working now Re: [WISPA] strange connectivity issues

2007-05-29 Thread Marlon K. Schafer (509) 982-2181

I went back there today (the xp machine, not the vista one).

I put their ip addy in my laptop.  Things worked just fine.  They had 3 megs 
down 3.3 megs up.  (testing to the Seattle Speakeasy site)


Put their ip addy in their computer, 1 ping went, all the rest failed.  Put 
my test ip in their machine.  Got 3 pings then all failed.


Next I put in a router.  Programmed it (via their machine) to use their ip 
addy as it's static ip.  Customer is now working famously.  They bought the 
router and will just go with that for now.  We'll see how long till 
something else breaks.  grin


I've printed out that xp networking fix.  I'll give it a try next time 
something like this comes up.


laters,
Marlon
(509) 982-2181
(408) 907-6910 (Vonage)Consulting services
42846865 (icq)WISP Operator since 1999!
[EMAIL PROTECTED]
www.odessaoffice.com/wireless
www.odessaoffice.com/marlon/cam



- Original Message - 
From: John Scrivner [EMAIL PROTECTED]

To: WISPA General List wireless@wispa.org
Sent: Monday, May 28, 2007 8:09 AM
Subject: Re: [WISPA] strange connectivity issues


I think the common thread is a corrupted TCP/IP stack in most of your 
situations. From techrepublic.com:


There are times when a network snafu completely or partially corrupts your 
IP installation, which causes your TCP/IP network connection to fail or 
behave erratically. When this happens, the best solution is to rebuild the 
TCP/IP protocol stack.


In previous versions of Windows, rebuilding the TCP/IP protocol stack was 
a simple operation--you just removed and reinstalled TCP/IP. In Windows 
XP, you can't remove TCP/IP because it's considered an integral part of 
the operating system.


However, XP does come with a command-line utility--called NetShell--that 
allows you to reset all TCP/IP-related registry settings to their default 
values. The end result is essentially the same as installing a brand-new 
TCP/IP configuration.


To reset all TCP/IP-related registry settings, open a command prompt and 
type the following command:


/netsh int ip reset filename/

You must specify a log file in the filename placeholder for this command 
to work. Details about which registry keys were modified will appear in 
the log file.


I do not know if this same utility works in Vista as I am not running 
Vista and do not have access to it from my house. Please let us know what 
you find that finally fixes these issues.

Scriv


Marlon K. Schafer (509) 982-2181 wrote:


I've had some very strange things happen of late.

Wed. I hooked up a new customer.  Couldn't get their system to work but 
my laptop did.  I told them to call MacAfee and see if they could figure 
out what was blocking things.  They ended up taking the computer to a 
friend's house, hooking it up to a dsl connection via a router and it 
worked just fine.  Why would it not work via static ip but would via 
dhcp?


Yesterday I did a Vista setup.  It would connect to the wireless router 
just fine but would not get to the internet.  I finally went into IE 
options and set all of them back to the defaults.  What BS would have 
been in IE that would have told it to not use the established network 
connection?  There were no proxy's set up either.  Worked with the same 
router and wildblue sat. connection.  I changed the wireless network name 
and local ip addy. Nothing else changed.  It still says that the DNS 
suffix is wildblue.net.  I can't find that anywhere in the machine.  Oh 
yeah, the machine had both IE and firefox, neither worked.


Vista is a disaster.  Crappy interface.  Hides everything in strange 
places and in non intuitive fashion.


Today I get an email from a customer that can email but IE won't work. 
This one's dialup.


Anyone else seeing strange stuff like this?  Is there some bizarre 
windows update or virus program that's messing things up?


Marlon
(509) 982-2181
(408) 907-6910 (Vonage)Consulting services
42846865 (icq)WISP Operator since 
1999!

[EMAIL PROTECTED]
www.odessaoffice.com/wireless
www.odessaoffice.com/marlon/cam




--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/



--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/


Re: [WISPA] strange connectivity issues

2007-05-28 Thread John Scrivner
I think the common thread is a corrupted TCP/IP stack in most of your 
situations. From techrepublic.com:


There are times when a network snafu completely or partially corrupts 
your IP installation, which causes your TCP/IP network connection to 
fail or behave erratically. When this happens, the best solution is to 
rebuild the TCP/IP protocol stack.


In previous versions of Windows, rebuilding the TCP/IP protocol stack 
was a simple operation--you just removed and reinstalled TCP/IP. In 
Windows XP, you can't remove TCP/IP because it's considered an integral 
part of the operating system.


However, XP does come with a command-line utility--called NetShell--that 
allows you to reset all TCP/IP-related registry settings to their 
default values. The end result is essentially the same as installing a 
brand-new TCP/IP configuration.


To reset all TCP/IP-related registry settings, open a command prompt and 
type the following command:


/netsh int ip reset filename/

You must specify a log file in the filename placeholder for this 
command to work. Details about which registry keys were modified will 
appear in the log file.


I do not know if this same utility works in Vista as I am not running 
Vista and do not have access to it from my house. Please let us know 
what you find that finally fixes these issues.

Scriv


Marlon K. Schafer (509) 982-2181 wrote:


I've had some very strange things happen of late.

Wed. I hooked up a new customer.  Couldn't get their system to work 
but my laptop did.  I told them to call MacAfee and see if they could 
figure out what was blocking things.  They ended up taking the 
computer to a friend's house, hooking it up to a dsl connection via a 
router and it worked just fine.  Why would it not work via static ip 
but would via dhcp?


Yesterday I did a Vista setup.  It would connect to the wireless 
router just fine but would not get to the internet.  I finally went 
into IE options and set all of them back to the defaults.  What BS 
would have been in IE that would have told it to not use the 
established network connection?  There were no proxy's set up either.  
Worked with the same router and wildblue sat. connection.  I changed 
the wireless network name and local ip addy. Nothing else changed.  It 
still says that the DNS suffix is wildblue.net.  I can't find that 
anywhere in the machine.  Oh yeah, the machine had both IE and 
firefox, neither worked.


Vista is a disaster.  Crappy interface.  Hides everything in strange 
places and in non intuitive fashion.


Today I get an email from a customer that can email but IE won't 
work.  This one's dialup.


Anyone else seeing strange stuff like this?  Is there some bizarre 
windows update or virus program that's messing things up?


Marlon
(509) 982-2181
(408) 907-6910 (Vonage)Consulting services
42846865 (icq)WISP Operator since 
1999!

[EMAIL PROTECTED]
www.odessaoffice.com/wireless
www.odessaoffice.com/marlon/cam




--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/


[WISPA] strange connectivity issues

2007-05-25 Thread Marlon K. Schafer (509) 982-2181

I've had some very strange things happen of late.

Wed. I hooked up a new customer.  Couldn't get their system to work but my 
laptop did.  I told them to call MacAfee and see if they could figure out 
what was blocking things.  They ended up taking the computer to a friend's 
house, hooking it up to a dsl connection via a router and it worked just 
fine.  Why would it not work via static ip but would via dhcp?


Yesterday I did a Vista setup.  It would connect to the wireless router just 
fine but would not get to the internet.  I finally went into IE options and 
set all of them back to the defaults.  What BS would have been in IE that 
would have told it to not use the established network connection?  There 
were no proxy's set up either.  Worked with the same router and wildblue 
sat. connection.  I changed the wireless network name and local ip addy. 
Nothing else changed.  It still says that the DNS suffix is wildblue.net.  I 
can't find that anywhere in the machine.  Oh yeah, the machine had both IE 
and firefox, neither worked.


Vista is a disaster.  Crappy interface.  Hides everything in strange places 
and in non intuitive fashion.


Today I get an email from a customer that can email but IE won't work.  This 
one's dialup.


Anyone else seeing strange stuff like this?  Is there some bizarre windows 
update or virus program that's messing things up?


Marlon
(509) 982-2181
(408) 907-6910 (Vonage)Consulting services
42846865 (icq)WISP Operator since 1999!
[EMAIL PROTECTED]
www.odessaoffice.com/wireless
www.odessaoffice.com/marlon/cam



--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/


RE: [WISPA] strange connectivity issues

2007-05-25 Thread Jonathan Schmidt
Marlon, I fixed my brother's XP two weeks ago with the same strange
e-mail-but-no-IE condition.  

I could ping by NAME or IP ADDRESS just fine.  The IE wouldn't work by NAME
or IP ADDRESS but e-mail would.  In fact, strangely, when entering a
server's numeric IP address in the address bar, it wouldn't find it and
re-wrote the address bar to http:///;, yes triple slashes and blank.  I've
seen that before but can't for the life of me recall what it was.  Maybe
that's benign.

I downloaded FIREFOX and it failed similarly.  I uninstalled IE7 and got
back to IE6 but still the same.  

I checked his XP SP2 firewall and it was disabled...I didn't leave it that
way.  HI checked the HOSTS file and it wasn't corrupted.

I tried rebooting with EVERYTHING turned off in MSCONFIG.  Still the same.

I brought up WORD and I tried entering www.cnn.com into the WORD OPEN
field and WORD managed to render it to a point, so the internal browsing
engine was working.

Then a window popped up Your Spyware Doctor requires an update, do you want
to do that now?...and I asked my brother where did you get this? and he
couldn't recall.  

That scared me.  I uninstalled it and everything I didn't know.  Of course,
I couldn't GOOGLE to see if it was OK...it could have been a legitimate
program or a fake.

Then I used the XP CD to do a system recovery and, after 1/2 hour, it was
back with applications still installed and the desktop as it was...and, no
problems.  

I turned on the XP firewall, downloaded DEFENDER (again) and installed it.

So far, so good and my brother insists it's 10X faster than before it broke.
What was it?  I don't know.  It was on a fast, new HP w/XP Media Center only
a few months old.

. . . j o n a t h a n

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Marlon K. Schafer (509) 982-2181
Sent: Friday, May 25, 2007 1:35 PM
To: wireless@wispa.org
Cc: [EMAIL PROTECTED]
Subject: [WISPA] strange connectivity issues

I've had some very strange things happen of late.

Wed. I hooked up a new customer.  Couldn't get their system to work but my 
laptop did.  I told them to call MacAfee and see if they could figure out 
what was blocking things.  They ended up taking the computer to a friend's 
house, hooking it up to a dsl connection via a router and it worked just 
fine.  Why would it not work via static ip but would via dhcp?

Yesterday I did a Vista setup.  It would connect to the wireless router just

fine but would not get to the internet.  I finally went into IE options and 
set all of them back to the defaults.  What BS would have been in IE that 
would have told it to not use the established network connection?  There 
were no proxy's set up either.  Worked with the same router and wildblue 
sat. connection.  I changed the wireless network name and local ip addy. 
Nothing else changed.  It still says that the DNS suffix is wildblue.net.  I

can't find that anywhere in the machine.  Oh yeah, the machine had both IE 
and firefox, neither worked.

Vista is a disaster.  Crappy interface.  Hides everything in strange places 
and in non intuitive fashion.

Today I get an email from a customer that can email but IE won't work.  This

one's dialup.

Anyone else seeing strange stuff like this?  Is there some bizarre windows 
update or virus program that's messing things up?

Marlon
(509) 982-2181
(408) 907-6910 (Vonage)Consulting services
42846865 (icq)WISP Operator since 1999!
[EMAIL PROTECTED]
www.odessaoffice.com/wireless
www.odessaoffice.com/marlon/cam



-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/


Re: [WISPA] strange connectivity issues

2007-05-25 Thread David E. Smith
Marlon K. Schafer (509) 982-2181 wrote:

 Anyone else seeing strange stuff like this?  Is there some bizarre
 windows update or virus program that's messing things up?

Yeah, it's called Microsoft Windows.

Serious answer: If there were anything that big going on, it'd probably
be on CNN and people would be crying about the end of the world or
something. Honestly, sounds like just a rash of several unrelated issues.

I won't dispute that Vista is weird and counter-intuitive, but thus far
the networking stack doesn't seem to be any more broken than XP's ever
was. (I'm still a bit cranky about the loss of gaming performance and
such, but that's not a WISPA issue really.)

David Smith
MVN.net
-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/


Re: [WISPA] strange connectivity issues

2007-05-25 Thread George Rogato

Marlon K. Schafer (509) 982-2181 wrote:

Vista is a disaster.  Crappy interface.  Hides everything in strange 
places and in non intuitive fashion.





I seen Vista for the first time a couple weeks ago. I felt stupid not 
being able to navigate so easily in front of the customer.


Now I need to upgrade to Vista on my personal machines so that I can 
acquainted.


George
--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/


Re: [WISPA] strange connectivity issues

2007-05-25 Thread Dennis Burgess

In several of my consulting customers, we use several differant types of
anti-virus/anti-spyware proxy servers etc.  Trend Micro is the most common,
but their hardware box and their software proxy server.   one company, a
just bit under 200 users, after putting in Trend Micro's Interscan Web
Security Suite and forcing everyone to run though the proxy server, we have
had 0 issues of this!

Slow browsing, unkonwn applications, things like that, SPYWARE, etc its
all a pain in the ass!   Weird stuff like, I can't browse, but can e-mail,
etc, all can be attribuited to spyware apps, etc.  ..

lol

Enjoy!

Dennis

On 5/25/07, Jonathan Schmidt [EMAIL PROTECTED] wrote:


Marlon, I fixed my brother's XP two weeks ago with the same strange
e-mail-but-no-IE condition.

I could ping by NAME or IP ADDRESS just fine.  The IE wouldn't work by
NAME
or IP ADDRESS but e-mail would.  In fact, strangely, when entering a
server's numeric IP address in the address bar, it wouldn't find it and
re-wrote the address bar to http:///;, yes triple slashes and
blank.  I've
seen that before but can't for the life of me recall what it was.  Maybe
that's benign.

I downloaded FIREFOX and it failed similarly.  I uninstalled IE7 and got
back to IE6 but still the same.

I checked his XP SP2 firewall and it was disabled...I didn't leave it that
way.  HI checked the HOSTS file and it wasn't corrupted.

I tried rebooting with EVERYTHING turned off in MSCONFIG.  Still the same.

I brought up WORD and I tried entering www.cnn.com into the WORD OPEN
field and WORD managed to render it to a point, so the internal browsing
engine was working.

Then a window popped up Your Spyware Doctor requires an update, do you
want
to do that now?...and I asked my brother where did you get this? and he
couldn't recall.

That scared me.  I uninstalled it and everything I didn't know.  Of
course,
I couldn't GOOGLE to see if it was OK...it could have been a legitimate
program or a fake.

Then I used the XP CD to do a system recovery and, after 1/2 hour, it was
back with applications still installed and the desktop as it was...and, no
problems.

I turned on the XP firewall, downloaded DEFENDER (again) and installed it.

So far, so good and my brother insists it's 10X faster than before it
broke.
What was it?  I don't know.  It was on a fast, new HP w/XP Media Center
only
a few months old.

. . . j o n a t h a n

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Marlon K. Schafer (509) 982-2181
Sent: Friday, May 25, 2007 1:35 PM
To: wireless@wispa.org
Cc: [EMAIL PROTECTED]
Subject: [WISPA] strange connectivity issues

I've had some very strange things happen of late.

Wed. I hooked up a new customer.  Couldn't get their system to work but my
laptop did.  I told them to call MacAfee and see if they could figure out
what was blocking things.  They ended up taking the computer to a friend's
house, hooking it up to a dsl connection via a router and it worked just
fine.  Why would it not work via static ip but would via dhcp?

Yesterday I did a Vista setup.  It would connect to the wireless router
just

fine but would not get to the internet.  I finally went into IE options
and
set all of them back to the defaults.  What BS would have been in IE that
would have told it to not use the established network connection?  There
were no proxy's set up either.  Worked with the same router and wildblue
sat. connection.  I changed the wireless network name and local ip addy.
Nothing else changed.  It still says that the DNS suffix is wildblue.net
.  I

can't find that anywhere in the machine.  Oh yeah, the machine had both IE
and firefox, neither worked.

Vista is a disaster.  Crappy interface.  Hides everything in strange
places
and in non intuitive fashion.

Today I get an email from a customer that can email but IE won't
work.  This

one's dialup.

Anyone else seeing strange stuff like this?  Is there some bizarre windows
update or virus program that's messing things up?

Marlon
(509) 982-2181
(408) 907-6910 (Vonage)Consulting services
42846865 (icq)WISP Operator since
1999!
[EMAIL PROTECTED]
www.odessaoffice.com/wireless
www.odessaoffice.com/marlon/cam



--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/





--
Dennis Burgess, MCP, CCNA, A+, N+, Mikrotik Certified Consultant
www.mikrotikconsulting.com
[EMAIL PROTECTED]
--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/


RE: [WISPA] strange connectivity issues

2007-05-25 Thread Jonathan Schmidt
Yes, I agree.  And, I have had very good luck with Trend Micro's on-line,
free virus removal tool...as long as the browser works at all.

I have fixed probably 20 PCs with this:
http://housecall.trendmicro.com
and use the free, on-line virus removal.  It is the real thing except it
loads via ActiveX but uses their up-to-date virus list.  Once you've cleaned
with that you can install and run the permanent anti-virus and anti-spyware
of your choice.  Their installed anti-virus product darned good.  So is Free
AGV:
http://free.grisoft.com

. . . j o n a t h a n

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Dennis Burgess
Sent: Friday, May 25, 2007 2:31 PM
To: WISPA General List
Subject: Re: [WISPA] strange connectivity issues

In several of my consulting customers, we use several differant types of
anti-virus/anti-spyware proxy servers etc.  Trend Micro is the most common,
but their hardware box and their software proxy server.   one company, a
just bit under 200 users, after putting in Trend Micro's Interscan Web
Security Suite and forcing everyone to run though the proxy server, we have
had 0 issues of this!

Slow browsing, unkonwn applications, things like that, SPYWARE, etc its
all a pain in the ass!   Weird stuff like, I can't browse, but can e-mail,
etc, all can be attribuited to spyware apps, etc.  ..

lol

Enjoy!

Dennis

On 5/25/07, Jonathan Schmidt [EMAIL PROTECTED] wrote:

 Marlon, I fixed my brother's XP two weeks ago with the same strange
 e-mail-but-no-IE condition.

 I could ping by NAME or IP ADDRESS just fine.  The IE wouldn't work by
 NAME
 or IP ADDRESS but e-mail would.  In fact, strangely, when entering a
 server's numeric IP address in the address bar, it wouldn't find it and
 re-wrote the address bar to http:///;, yes triple slashes and
 blank.  I've
 seen that before but can't for the life of me recall what it was.  Maybe
 that's benign.

 I downloaded FIREFOX and it failed similarly.  I uninstalled IE7 and got
 back to IE6 but still the same.

 I checked his XP SP2 firewall and it was disabled...I didn't leave it that
 way.  HI checked the HOSTS file and it wasn't corrupted.

 I tried rebooting with EVERYTHING turned off in MSCONFIG.  Still the same.

 I brought up WORD and I tried entering www.cnn.com into the WORD OPEN
 field and WORD managed to render it to a point, so the internal browsing
 engine was working.

 Then a window popped up Your Spyware Doctor requires an update, do you
 want
 to do that now?...and I asked my brother where did you get this? and he
 couldn't recall.

 That scared me.  I uninstalled it and everything I didn't know.  Of
 course,
 I couldn't GOOGLE to see if it was OK...it could have been a legitimate
 program or a fake.

 Then I used the XP CD to do a system recovery and, after 1/2 hour, it was
 back with applications still installed and the desktop as it was...and, no
 problems.

 I turned on the XP firewall, downloaded DEFENDER (again) and installed it.

 So far, so good and my brother insists it's 10X faster than before it
 broke.
 What was it?  I don't know.  It was on a fast, new HP w/XP Media Center
 only
 a few months old.

 . . . j o n a t h a n

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Marlon K. Schafer (509) 982-2181
 Sent: Friday, May 25, 2007 1:35 PM
 To: wireless@wispa.org
 Cc: [EMAIL PROTECTED]
 Subject: [WISPA] strange connectivity issues

 I've had some very strange things happen of late.

 Wed. I hooked up a new customer.  Couldn't get their system to work but my
 laptop did.  I told them to call MacAfee and see if they could figure out
 what was blocking things.  They ended up taking the computer to a friend's
 house, hooking it up to a dsl connection via a router and it worked just
 fine.  Why would it not work via static ip but would via dhcp?

 Yesterday I did a Vista setup.  It would connect to the wireless router
 just

 fine but would not get to the internet.  I finally went into IE options
 and
 set all of them back to the defaults.  What BS would have been in IE that
 would have told it to not use the established network connection?  There
 were no proxy's set up either.  Worked with the same router and wildblue
 sat. connection.  I changed the wireless network name and local ip addy.
 Nothing else changed.  It still says that the DNS suffix is wildblue.net
 .  I

 can't find that anywhere in the machine.  Oh yeah, the machine had both IE
 and firefox, neither worked.

 Vista is a disaster.  Crappy interface.  Hides everything in strange
 places
 and in non intuitive fashion.

 Today I get an email from a customer that can email but IE won't
 work.  This

 one's dialup.

 Anyone else seeing strange stuff like this?  Is there some bizarre windows
 update or virus program that's messing things up?

 Marlon
 (509) 982-2181
 (408) 907-6910 (Vonage)Consulting services
 42846865 (icq

RE: [WISPA] strange connectivity issues

2007-05-25 Thread Chadd Thompson
Marlon,

Sound like you covered all your bases here but here is my .02 worth.

I have had issues like this in the past and it has always been related to
one of three things.

1. If it is a new hookup from dialup or SAT usually it is some sort of a
proxy issue, either proxy is enabled in internet explorer settings or there
is a third party app installed for the dialup/sat. I had to reformat a PC
one time because I couldn't get a clean uninstall of Directway's proxy
software.

2. Mcaffee or Norton Virus/internet security is installed tyring to make
sure that it stays installed on the PC and kept up to date. I have seen both
programs totally hose a PC with the same issues you are describing. One of
the first things I do on a PC with either of these to programs is uninstall
it if it will let you and install AVG Antivirus and AVG anitspyware or MS
defender.

3. There is a virus and or spyware on the PC.

Thanks,
Chadd

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Behalf Of Marlon K. Schafer (509) 982-2181
 Sent: Friday, May 25, 2007 1:35 PM
 To: wireless@wispa.org
 Cc: [EMAIL PROTECTED]
 Subject: [WISPA] strange connectivity issues


 I've had some very strange things happen of late.

 Wed. I hooked up a new customer.  Couldn't get their system to
 work but my
 laptop did.  I told them to call MacAfee and see if they could figure out
 what was blocking things.  They ended up taking the computer to a
 friend's
 house, hooking it up to a dsl connection via a router and it worked just
 fine.  Why would it not work via static ip but would via dhcp?

 Yesterday I did a Vista setup.  It would connect to the wireless
 router just
 fine but would not get to the internet.  I finally went into IE
 options and
 set all of them back to the defaults.  What BS would have been in IE that
 would have told it to not use the established network connection?  There
 were no proxy's set up either.  Worked with the same router and wildblue
 sat. connection.  I changed the wireless network name and local ip addy.
 Nothing else changed.  It still says that the DNS suffix is
 wildblue.net.  I
 can't find that anywhere in the machine.  Oh yeah, the machine
 had both IE
 and firefox, neither worked.

 Vista is a disaster.  Crappy interface.  Hides everything in
 strange places
 and in non intuitive fashion.

 Today I get an email from a customer that can email but IE won't
 work.  This
 one's dialup.

 Anyone else seeing strange stuff like this?  Is there some
 bizarre windows
 update or virus program that's messing things up?

 Marlon
 (509) 982-2181
 (408) 907-6910 (Vonage)Consulting services
 42846865 (icq)WISP Operator
 since 1999!
 [EMAIL PROTECTED]
 www.odessaoffice.com/wireless
 www.odessaoffice.com/marlon/cam



 --
 WISPA Wireless List: wireless@wispa.org

 Subscribe/Unsubscribe:
 http://lists.wispa.org/mailman/listinfo/wireless

 Archives: http://lists.wispa.org/pipermail/wireless/

 No virus found in this incoming message.
 Checked by AVG Free Edition.
 Version: 7.5.467 / Virus Database: 269.8.0/817 - Release Date:
 5/24/2007 4:01 PM


-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/


Re: [WISPA] strange connectivity issues

2007-05-25 Thread Clint Ricker

Often, when you have issues like this, a good practice is to reset TCP/IP
and Winsock.  This can especially be true on machines that have been mucked
up with Norton Internet (in)Security, which has an annoying habit of leaving
its firewall settings intact after uninstallation on at least some
versions.  This fixes a lot of things at once and so is often a good quick
fix.

The instructions below walk through the process...

Also, check out netstat (open command prompt, do netstat -ano (the n
disables DNS and the o shows the PID).  This can give you an idea as to what
sort of connections the computer is making and attempting to make.  It also
often reveals viruses, as anything that is trying to spam out or spread
itself out through the network will (generally) show up in here (although,
viruses sometimes do hide themselves).

-Clint Ricker
Kentnis Technologies.





TCP/IP and Winsock Reset

Reset the Winsock and TCP/IP stack...  Reset TCP/IP

Command usage netsh int ip reset [log_file_name]

To run the command successfully, you must specify a file name for the log
where actions that are taken by netsh will be recorded. For example, at a
command prompt, type either of the samples that are listed in the Command
samples section. The TCP/IP stack will then be reset on a system, and the
actions that were taken will be recorded in the log file, Resetlog.txt. The
first sample creates the log file in the current directory, while the second
sample creates a path where the log will reside. In either case, where the
specified log file already exists, the new log will be appended to the end
of the existing file.

Command samples netsh int ip reset resetlog.txt netsh int ip reset
c:\resetlog.txt

Reset Winsock


  1. Click Start, and then click Run.
  2. In the Open box, type regedit, and then click OK.
  3. Locate the following registry subkeys:
  HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
  HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
  4. Right-click each key, and then click Delete.
  5. Click Yes to confirm the deletion.

Note Restart the computer after you delete the Winsock keys. This action
creates new shell entries for those two registry subkeys. If you do not
restart the computer after you delete the Winsock keys, the next step does
not work correctly. When you restart the computer, you may see dialog boxes
that mention TCP/IP problems and various event log messages that relate to
services that you have installed. Ignore these messages. To reinstall
TCP/IP, follow these steps:

  1. Right-click the network connection, and then click Properties.
  2. Click Install, click Protocol, and then click Add.
  3. Click Have Disk
  4. Type C:\Windows\inf, and then click OK.
  5. In the list of available protocols, click Internet Protocol
  (TCP/IP), and then click OK.
  6. Restart the computer.


-



On 5/25/07, Chadd Thompson [EMAIL PROTECTED] wrote:


Marlon,

Sound like you covered all your bases here but here is my .02
worth.

I have had issues like this in the past and it has always been related to
one of three things.

1. If it is a new hookup from dialup or SAT usually it is some sort of a
proxy issue, either proxy is enabled in internet explorer settings or
there
is a third party app installed for the dialup/sat. I had to reformat a PC
one time because I couldn't get a clean uninstall of Directway's proxy
software.

2. Mcaffee or Norton Virus/internet security is installed tyring to make
sure that it stays installed on the PC and kept up to date. I have seen
both
programs totally hose a PC with the same issues you are describing. One of
the first things I do on a PC with either of these to programs is
uninstall
it if it will let you and install AVG Antivirus and AVG anitspyware or
MS
defender.

3. There is a virus and or spyware on the PC.

Thanks,
Chadd

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Behalf Of Marlon K. Schafer (509) 982-2181
 Sent: Friday, May 25, 2007 1:35 PM
 To: wireless@wispa.org
 Cc: [EMAIL PROTECTED]
 Subject: [WISPA] strange connectivity issues


 I've had some very strange things happen of late.

 Wed. I hooked up a new customer.  Couldn't get their system to
 work but my
 laptop did.  I told them to call MacAfee and see if they could figure
out
 what was blocking things.  They ended up taking the computer to a
 friend's
 house, hooking it up to a dsl connection via a router and it worked just
 fine.  Why would it not work via static ip but would via dhcp?

 Yesterday I did a Vista setup.  It would connect to the wireless
 router just
 fine but would not get to the internet.  I finally went into IE
 options and
 set all of them back to the defaults.  What BS would have been in IE
that
 would have told it to not use the established network connection?  There
 were no proxy's set up either.  Worked with the same router and wildblue
 sat. connection.  I changed the wireless network name and local