PDA

View Full Version : Default gateway is not available



Rainbow Dash
June 30th, 2012, 03:44 PM
I picked up a Lenovo x220t a few weeks ago, and so far it's working great, however I keep having this issue with wireless connections (apparently) randomly not working, and requiring a reset of the network adapter to get them working again.

Whenever I run the network troubleshooting utility I'm informed that the default gateway is not available. After the reset the connection will work fine anywhere from a few minutes to a few hours, there is no apparent pattern to why the issue occurs.

Other computers on the same network have no issues, both wired and wireless, and a wired connection to the tablet also functions without any issues.

From what I've been able to tell from googling, this is a windows 7 specific issue, but I have yet to find a fix. Any suggestions?

jcap
June 30th, 2012, 04:12 PM
First question I have is, are you using the normal Windows wireless manager, or are you using a third party application to manage the wireless card and connected networks?

Rainbow Dash
June 30th, 2012, 04:36 PM
I'm just doing it through the normal taskbar thing.

JackalStomper
June 30th, 2012, 05:19 PM
go into the IPv4 settings and check how the adapter is acquiring the gateway? Maybe sketchy drivers are messing with automatic detection, should try manual setting.

PopeAK49
June 30th, 2012, 05:38 PM
First question I have is, are you using the normal Windows wireless manager, or are you using a third party application to manage the wireless card and connected networks?

I would look at this. You either have windows managing your wireless connection or the 3rd party app that comes with the wireless nic.

Can you tell us if you are getting a private IP from your gateway or an APIPA? Go to command prompt and type ipconfig /all. Display the results for us.

Rainbow Dash
June 30th, 2012, 06:00 PM
go into the IPv4 settings and check how the adapter is acquiring the gateway? Maybe sketchy drivers are messing with automatic detection, should try manual setting.

Everything is set to be automatically obtained, and I'm pretty sure it's not the driver, every single other person with this issue that I found reported that it was limited to w7.


I would look at this. You either have windows managing your wireless connection or the 3rd party app that comes with the wireless nic.

Can you tell us if you are getting a private IP from your gateway or an APIPA? Go to command prompt and type ipconfig /all. Display the results for us.

I really have no idea that means, sorry.


Windows IP Configuration

Host Name . . . . . . . . . . . . : DS-THINK
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : phub.net.cable.rogers.com

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : phub.net.cable.rogers.com
Description . . . . . . . . . . . : 1x1 11b/g/n Wireless LAN PCI Express Half
Mini Card Adapter
Physical Address. . . . . . . . . : 7C-E9-D3-F3-9F-F2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::adfd:53a:f93e:c93(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.111(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : June-30-12 18:18:21
Lease Expires . . . . . . . . . . : July-01-12 18:18:21
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 343730643
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-66-A7-C5-3C-97-0E-01-DA-4E

DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connecti
on
Physical Address. . . . . . . . . : 3C-97-0E-01-DA-4E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.phub.net.cable.rogers.com:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : phub.net.cable.rogers.com
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:18dd:4ca:9c1f:4e5c(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::18dd:4ca:9c1f:4e5c(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

jcap
July 2nd, 2012, 11:57 AM
So, what happens if you configure a static address for it? Like, what if you actually set the adapter's properties to always use 192.168.0.111 for its IP, 192.168.0.1 for the DG, and 192.168.0.1 for its mask?

Also, next time it stops working, do another ipconfig /all and post here.

Also also, next time it stops working, ping your default gateway and post here: ping 192.168.0.1

Roostervier
July 2nd, 2012, 07:54 PM
money is to blame... fucking fat cats sitting in their mansions made your gateway unavailable because they've been reading your libelous assertions about them, it's all a conspiracy

Rainbow Dash
July 2nd, 2012, 09:34 PM
C:\Users\DS>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DS-THINK
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : phub.net.cable.rogers.com

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : phub.net.cable.rogers.com
Description . . . . . . . . . . . : 1x1 11b/g/n Wireless LAN PCI Express Half
Mini Card Adapter
Physical Address. . . . . . . . . : 7C-E9-D3-F3-9F-F2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::adfd:53a:f93e:c93%14(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.4.147(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : July-02-12 20:45:33
Lease Expires . . . . . . . . . . : July-03-12 20:45:33
Default Gateway . . . . . . . . . : 192.168.4.1
DHCP Server . . . . . . . . . . . : 192.168.4.1
DHCPv6 IAID . . . . . . . . . . . : 343730643
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-66-A7-C5-3C-97-0E-01-DA-4E

DNS Servers . . . . . . . . . . . : 192.168.4.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : phub.net.cable.rogers.com
Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connecti
on
Physical Address. . . . . . . . . : 3C-97-0E-01-DA-4E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.phub.net.cable.rogers.com:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : phub.net.cable.rogers.com
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:24a5:1d3:9c1f:4e5c(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::24a5:1d3:9c1f:4e5c%13(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\DS>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.4.147: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Users\DS>ping 192.168.4.1

Pinging 192.168.4.1 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 192.168.4.147: Destination host unreachable.
Reply from 192.168.4.147: Destination host unreachable.

Ping statistics for 192.168.4.1:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

Trying changing IPv4 settings now.

JackalStomper
July 3rd, 2012, 02:22 AM
working

IPv4 Address. . . . . . . . . . . : 192.168.0.111
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1

not working

IPv4 Address. . . . . . . . . . . : 192.168.4.147
Default Gateway . . . . . . . . . : 192.168.4.1
DHCP Server . . . . . . . . . . . : 192.168.4.1


should try manual setting


Also drivers are OS version specific, even if they have the same installer they can install different iterations of themselves depending on the environment. So yes it can be drivers even if its only on windows 7 that the problems are occurring.

Rainbow Dash
July 3rd, 2012, 07:40 PM
I updated the firmware on my router and the issue has not re-occured today after being used for about 8 hours, hopefully this is fixed, if not I'll be back.

thanks for helping!