network connectivity lost

  • Thread starter Thread starter John Gregory
  • Start date Start date
J

John Gregory

I am having trouble connecting to my router. Both wireless and cable
connections are no longer working after a road trip.
The computer is a IBM T-30 laptop that worked fine while on the road over
christmas, but does not work at our home network upon return.

Both the wireless and the cable connections show connectivity, but there is
no IP address. I can use another laptop to verify the router is working
properly. The router does not showw an IP address for the T-30 laptop.

I have done multiple resets, unsinstalled and re-installed both the cable
and wireless NIC drivers, and run the windows network diagnostic tool, all
with no luck.

Any ideas on how to diagnos this problem?
 
John said:
I am having trouble connecting to my router. Both wireless and cable
connections are no longer working after a road trip.
The computer is a IBM T-30 laptop that worked fine while on the road over
christmas, but does not work at our home network upon return.

Both the wireless and the cable connections show connectivity, but there is
no IP address. I can use another laptop to verify the router is working
properly. The router does not showw an IP address for the T-30 laptop.

I have done multiple resets, unsinstalled and re-installed both the cable
and wireless NIC drivers, and run the windows network diagnostic tool, all
with no luck.

Any ideas on how to diagnos this problem?

From a command prompt window, run ipconfig /all and post the results.

Do the same from any other computer on your home network that is working.

Verify that the Ethernet cable you're using is OK by connecting that
"other" laptop to your router with it.

--
Lem -- MS-MVP - Networking

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm
 
The network cable works fine on the working computer. I have also tried
multiple ports and another cable, all with the same results.

ipconfig /all for both computers is as follows:
---------------------

From the computer that is not working:


Windows IP Configuration



An internal error occurred: The request is not supported.



Please contact Microsoft Product Support Services for further help.



Additional information: Unable to query host name.

---------------------


From the computer that is working properly:

Windows IP Configuration



Host Name . . . . . . . . . . . . : LENOVO-12CF6849

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : hsd1.ma.comcast.net.



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . : hsd1.ma.comcast.net.

Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG
Network Connection

Physical Address. . . . . . . . . : 00-19-D2-34-94-5D

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.109

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IP Address. . . . . . . . . . . . : fe80::219:d2ff:fe34:945d%4

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 68.87.71.226

68.87.73.242

fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

Lease Obtained. . . . . . . . . . : Sunday, January 06, 2008 8:12:39
AM

Lease Expires . . . . . . . . . . : Monday, January 07, 2008 8:12:39
AM



Tunnel adapter Teredo Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 80-00-28-3A-E7-DD-3B-C3

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . :
2001:0:4136:e38c:8000:283a:e7dd:3bc3

IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5

Default Gateway . . . . . . . . . : ::

NetBIOS over Tcpip. . . . . . . . : Disabled



Tunnel adapter Automatic Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . : hsd1.ma.comcast.net.

Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-01-6D

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.109%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled
 
Do you have a grinch at home that got into your router while you were away?
Perhaps someone block your errant computer, by it MAC address!
I know that sounds ridiculous, but you do have a tough problem.
It sounds like hardware died...but when you say that both cable and wireless
resources failed simultaneously, that tends to dispel that theory.

Can you set your wired LAN card's TCP/IP properties statically, and see what
happens? Please post your ipconfig /all here, accordingly.

I suggest ip address of 192.168.1.51
mask 255.255.255.0
default gateway 192.168.1.1
dns Use the same as you have on the working computer
 
John said:
The network cable works fine on the working computer. I have also tried
multiple ports and another cable, all with the same results.

ipconfig /all for both computers is as follows:
---------------------

From the computer that is not working:


Windows IP Configuration



An internal error occurred: The request is not supported.



Please contact Microsoft Product Support Services for further help.



Additional information: Unable to query host name.

---------------------


From the computer that is working properly:

Windows IP Configuration



Host Name . . . . . . . . . . . . : LENOVO-12CF6849

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : hsd1.ma.comcast.net.



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . : hsd1.ma.comcast.net.

Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG
Network Connection

Physical Address. . . . . . . . . : 00-19-D2-34-94-5D

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.109

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IP Address. . . . . . . . . . . . : fe80::219:d2ff:fe34:945d%4

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 68.87.71.226

68.87.73.242

fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

Lease Obtained. . . . . . . . . . : Sunday, January 06, 2008 8:12:39
AM

Lease Expires . . . . . . . . . . : Monday, January 07, 2008 8:12:39
AM



Tunnel adapter Teredo Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 80-00-28-3A-E7-DD-3B-C3

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . :
2001:0:4136:e38c:8000:283a:e7dd:3bc3

IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5

Default Gateway . . . . . . . . . : ::

NetBIOS over Tcpip. . . . . . . . : Disabled



Tunnel adapter Automatic Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . : hsd1.ma.comcast.net.

Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-01-6D

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.109%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled

See if this helps: http://support.microsoft.com/kb/918557/en-us

--
Lem -- MS-MVP - Networking

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm
 
I tried both of the suggestions, but still no success. Ipgonfig still does
not work, and still no connection (ip address) althogh both still show a good
connection to the router.

Any other ideas?
 
John said:
I tried both of the suggestions, but still no success. Ipgonfig still does
not work, and still no connection (ip address) althogh both still show a good
connection to the router.

Any other ideas?

Assuming that you don't recall anything that you did between the time
things work and the time they didn't, only general suggestions. But
first, go to Network Connections, right click on with the Local Area
Connection or the Wireless Connection, and select Properties. What is
listed under "This connection uses the following items"?

(You should see *only* Client for Microsoft Networks, File and Printer
Sharing, Internet Protocol (TCP/IP), and possibly also QoS Packet
Scheduler.)

The following 2 sites have similar suggestions:

Try MVP Hans-Georg Michna's network troubleshooter:
http://winhlp.com/wxnet.htm (see the section "TCP/IP not working")

Or try the suggestions at: http://nitecruzr.blogspot.com/search?q=lspfix
(If you have WinXP sp2, I'd start with #9 and then #7)

--
Lem -- MS-MVP - Networking

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm
 
Thank you for your responses, however I decided to reload Windows since I
could not determine why the problem occured. Everything seemed to be set
correctly, it simply did not work.

I did a repair installation and the computer is now working normally -
downloading updates from the windows site.

I still have no idea why the change.
 
John said:
Thank you for your responses, however I decided to reload Windows since I
could not determine why the problem occured. Everything seemed to be set
correctly, it simply did not work.

I did a repair installation and the computer is now working normally -
downloading updates from the windows site.

I still have no idea why the change.

Although figuring out and fixing only what has gone wrong is satisfying,
sometimes a repair install is the fastest way to a resolution. I'm glad
you got things back to working.
--
Lem -- MS-MVP - Networking

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm
 
Back
Top