TCP/IP won't connect Ethernet (SP2?)

[Guest]

About a week after installing SP2, the Ethernet connection on my Thinkpad A21
became unable to connect to any network from XP, although if I boot to
Win2000, the hardware works perfectly as usual.

Everything looks normal in Device Manager, and the properties show nothing
amiss, but when I plug into the network I just get the dreaded Limited or No
Connectivity notice, DHCP fails, and even if I assign a valid IP
address/mask/gateway I am still unable to ping anything.

Trying 'netsh int ip reset' made no difference. I don't know where to turn
next.

 

[Guest]

i've posted a similar situation under the windows configuration mgmt
heading, windows xp config and mgmt sub heading . take a look there as to
any helpful thoughts that might come down.

 

[Ken Wickes [MSFT]]

Any 3rd party firewalls installed?

 

[Guest]

Sorry about my delay reading your reply. Yes, I have ZA, but it's configured
to allow me to connect to the 10.1.1.1 domain at my work, and no change had
been made to it.
However, before I got your reply, in desperation I tried 'netsh winsock
reset'. To my great surprise this did the trick - I was not expecting it to
work because I assumed that my previously unsuccessful invocation of 'netsh
int ip reset' was more comprehensive and would have reset the winsock as part
of its function.

But thanks very much for your attention.

Any 3rd party firewalls installed?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

i've posted a similar situation under the windows configuration mgmt
heading, windows xp config and mgmt sub heading . take a look there as to
any helpful thoughts that might come down.

 

[Guest]

Ken: yes I have ZA, but it is configured to allow access to the 10.1.1.1
domain at work, and to the 192.168.1.1 router at home, and had not been
changed.

However, before I found your post, in desperation I tried 'netsh winsock
reset' which fixed the problem, much to my surprise, as I assumed that my
unsuccessful invocation of 'netsh int ip reset' would have included resetting
winsock as part of its function.

But thanks very much for replying to my problem, and I hope my accidental
hit-and-miss solution to it might help someone else...

Any 3rd party firewalls installed?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

i've posted a similar situation under the windows configuration mgmt
heading, windows xp config and mgmt sub heading . take a look there as to
any helpful thoughts that might come down.

 

[Guest]

Ken: yes I have ZA, but it is configured to allow access to the 10.1.1.1
domain at work, and to the 192.168.1.1 router at home, and had not been
changed.

However, before I found your post, in desperation I tried 'netsh winsock
reset' which fixed the problem, much to my surprise, as I assumed that my
unsuccessful invocation of 'netsh int ip reset' would have included resetting
winsock as part of its function.

But thanks very much for replying to my problem, and I hope my accidental
hit-and-miss solution to it might help someone else...

Any 3rd party firewalls installed?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

i've posted a similar situation under the windows configuration mgmt
heading, windows xp config and mgmt sub heading . take a look there as to
any helpful thoughts that might come down.

 

[Guest]

Sorry, I didn't mean to send the same reply 3 times - any idea why the system
always tells me it can't send the message whenever I tick 'Notify me of
replies' - and then - just sometimes - sneakily sends the damn thing
anyway...?

 

[Ken Wickes [MSFT]]

I'm actually surprised that worked. I didn't think ping went through the
winsock providers.

Regardless I'm glad you have it working.

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Ken: yes I have ZA, but it is configured to allow access to the 10.1.1.1
domain at work, and to the 192.168.1.1 router at home, and had not been
changed.

However, before I found your post, in desperation I tried 'netsh winsock
reset' which fixed the problem, much to my surprise, as I assumed that my
unsuccessful invocation of 'netsh int ip reset' would have included
resetting
winsock as part of its function.

But thanks very much for replying to my problem, and I hope my accidental
hit-and-miss solution to it might help someone else...

Any 3rd party firewalls installed?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no
rights.

i've posted a similar situation under the windows configuration mgmt
heading, windows xp config and mgmt sub heading . take a look there as
to
any helpful thoughts that might come down.

:

About a week after installing SP2, the Ethernet connection on my
Thinkpad
A21
became unable to connect to any network from XP, although if I boot to
Win2000, the hardware works perfectly as usual.

Everything looks normal in Device Manager, and the properties show
nothing
amiss, but when I plug into the network I just get the dreaded Limited
or
No
Connectivity notice, DHCP fails, and even if I assign a valid IP
address/mask/gateway I am still unable to ping anything.

Trying 'netsh int ip reset' made no difference. I don't know where to
turn
next.