Windows 7 netbook can't see gateway

Microsoft Windows 7 home premium
June 1, 2010 at 13:04:10
Specs: Windows 7
My new Windows 7 netbook can only "see" the computers that are connected to the wireless access point. The wireless access point is connected to a Linksys broadband router which is the gateway. Because the netbook cannot see the gateway, it has local network access only. The curious thing is that the Linksys router is also the DHCP server and does provide a TCP/IP address to the netbook when requested. The netbook works just fine when connected to the network with an ethernet cable. I thought the problem might be a limitation of Windows 7 Starter, so I performed a clean install of Windows 7 Professional to no avail.

See More: Windows 7 netbook cant see gateway

Report •


#1
June 1, 2010 at 13:18:41
do a ipconfig and see if the netbook has a gateway entry.
if not your wireless AP dhcp server is incorrectly configured.

Report •

#2
June 1, 2010 at 14:21:57
Here is the basic network configuration:
Cable Modem
|
Linksys Router 192.168.1.1
| |
| +------- Linksys 16 port switch
|
Airlink 300N Wireless router configured as an AP 192.168.1.5
| |
| +~~~~ Netbook, Laptop and Desktops via Wi-Fi
|
Various desktops, printers and NAS devices (wired)

The netbook can "see" everything connected to the AP (wired and wireless), but cannot see anything that is upstream between the AP and the Modem.

The netbook is assigned an IP of 192.168.1.139 with a gateway of 192.168.1.1 by the DHCP server located on the Linksys router at 192.168.1.1.

This current problem is with an MSI netbook. We had the same problem with an Acer netbook that has since been returned. It was also running Windows 7 Starter. I have another Acer netbook that is running XP that has had no network problems.


Report •

#3
June 1, 2010 at 14:47:40
and the ipconfig /all?????

Report •

Related Solutions

#4
June 1, 2010 at 15:00:53
The result of the ipconfig/all was recapped in the following paragraph:

"The netbook is assigned an IP of 192.168.1.139 with a gateway of 192.168.1.1 by the DHCP server located on the Linksys router at 192.168.1.1."

The subnet mask was 255.255.255.0


Report •

#5
June 1, 2010 at 16:41:27
Please reread your "instructions" before you say that weren't followed.. You said: "do a ipconfig and see if the netbook has a gateway entry."

I ran the ipconfig (no /all was specified) as requested and responded that the DHCP server had assigned a gateway address of 192.168.1.1

In any case, here are the results of the ipconfig/all:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Netbook
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.wa.comcast.net.

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : hsd1.wa.comcast.net.
Description . . . . . . . . . . . : 802.11bgn 1T1R Mini Card Wireless Adapter
Physical Address. . . . . . . . . : 40-61-86-3C-24-EE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.132(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, June 01, 2010 4:19:47 PM
Lease Expires . . . . . . . . . . : Wednesday, June 02, 2010 4:19:46 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 4.2.2.1
4.2.2.2
68.87.69.150
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : hsd1.wa.comcast.net.
Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
Physical Address. . . . . . . . . : 40-61-86-1B-22-ED
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.hsd1.wa.comcast.net.:

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

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
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

Trying to ping the gateway at 192.168.1.1 yields either a timeout (occasional) or the message "Destination host unreachable" (more frequent).


Report •

#6
June 2, 2010 at 07:51:38
Thanks for the ipconfig /all

You should not be using the verizon dns servers but the comcast ones.

Though 68.87.69.150 pings successfully it is not listed as a comcast dns server. Nor could I find it listed as a dns server on the web.

The listed national comcast dns servers are
68.87.66.196 Comcast (national) Primary DNS Server.
68.87.64.196 Comcast Secondary DNS Server.

It also appears you are manually inputting the
Connection-specific DNS Suffix . : hsd1.wa.comcast.net.
since this shows up on the wired card which should have nothing showing. Don't do this. Leave it to dhcp/blank.

Having a timeout when pinging the gateway indicates a communication issue. Do you have access to another wireless laptop/friends notebook you could test with?.

We need to determine if its the notebook or the AP

I would also suggest you disable the wired connection and try your ping test again. Windows sometimes gets confused as to which interface its talking on


Report •

#7
June 2, 2010 at 11:13:35
That's interesting regarding the Verizon DNS entries. Verizon does not service my neighborhood with DSL. The DNS addresses must have been hand entered into the router by a previous owner of the "new" router I purchased from Fry's...

As for the DNS suffix on the wired connection, that is present on all of my computers. I assumed that it was set by Comcast as I see no way to change or enter this on the router.

I have eliminated the Verizon DNS entries from the router configuration and now receive the following DNS addresses:
68.87.69.150
68.87.85.102

The updated DNS addresses (minus the Verizon addresses) now show up on the Netbook with ipconfig/all, but the Netbook still cannot ping any other address that is not "attached" to the AP - still can't ping the gateway at 192.168.1.1.

I just installed a frys.com Wireless N USB adapter on the Netbook and am able to use AngryIP to see my entire network with the new NIC. This is still not a solution to why the integrated wireless NIC is not working. It appears to me that the problem might be with the wireless module and drivers for Win 7 that is being used in some of the newer Netbooks. As I mentioned before, I have an older Acer (1 year old) that works fine on my home network.


Report •

#8
June 2, 2010 at 11:31:03
Can you see the entire network without angryip on the new nic?
You see the entire network just fine with the acer?

firewall software disabled?
can you ping the ip of the AP you are attached to?


Report •

#9
June 2, 2010 at 12:12:53
Yes, I can individually ping the other computers on the network with the new NIC. The older Acer has never had a network problem, wired or wireless. The Acer Netbook that was returned because of a wireless network problem (probably the same issue) was a newer Acer unit, and the Netbook that I am currently working with is an newer MSI.

Same results with the firewall enabled and disabled on the MSI.

On the MSI and just the integrated wireless NIC, I can only ping the AP and any other computer or device attached to that AP with the exception of the Linksys Router at 192.168.1.1. With the frys.com NIC installed I have access to my entire network as well as the internet.

The obvious solution is simple - use a secondary wireless NIC. It's just that I dislike working around problems that have no apparent explanation or solution.

So, to recap, from the MSI Netbook utilizing the integrated wireless NIC, I can ping only those units plugged into or connected to my wireless AP at 192.168.1.5. Even though there is a direct CAT-6 cable run to the Linksys router at 192.168.1.1, I can't ping the router. Even though I cannot ping the router, the router's DHCP server still assigns an address to the MSI (TCP vs UDP?).


Report •

#10
June 2, 2010 at 12:28:23
is network discovery enabled? I am not near a windows7 box to tell you where to look. On vista its in the network and sharing gui.

Can you ping any of the pcs attached to the router?


Report •

#11
June 2, 2010 at 13:04:53
Good question regarding network discovery. It's a little more convoluted to get to than it is in Vista. Because Win 7 couldn't verify the gateway/router, it identifies the network as a Public Network with discovery turned off by default. If I go to My Computer and select Network, the "gold bar" indicates that discovery is turned off. At that point I am able to change the network from Public to Private with discovery turned on.

Same failure in pinging the gateway at 192.168.1.1.

No, I am unable to ping or access anything that is plugged into the Linksys 16 port switch. This switch is plugged directly into the Linksys router.


Report •

#12
June 2, 2010 at 13:14:38
That is just too weird. I would contact the netbooks support [its under warranty] and get their take on it. Perhaps a replacement driver or patch is available.

If all of this works for the acer it has to be the netbook is the source of the problem.


Report •

#13
June 2, 2010 at 13:28:41
Yes, weird it is. I encountered a situation similar to this when we were daisy-chaining switches at a private school. We found that some of the shared printers off of one switch could not be reached by some computers that were connected to a different switch. We finally solved that by restructuring the network.

I'll post a response here if and when I get this resolved...

Thanks for your assistance.


Report •

#14
June 6, 2010 at 20:31:41
Replaced the Linksys router (it was 5-6 years old) with the Airlink 300N AP now configured as a wireless broadband router. Everyone seems to be happy, the Win 7 netbook now connects to the internet via the wireless connection. Because the broadband connection is at one end of the basement, the wireless connection at the opposite upstairs end has degraded a bit (the wireless AP used to be in the center of the basement).

Okay.

Then I figured that I would fire up my backup Airlink 300N router as a wireless AP in the center of the basement for better coverage. Changed the SSID in the "new" AP so as not to conflict with the main wireless router's SSID. Surprise, surprise, when the Netbook connects with the new AP and new SSID, it has exactly the same problem conncting to the internet (seeing the gateway) as it had before. I think it is a Windows 7/wireless NIC driver problem, but I guess it could be a problem with the Airlink equipment...

I left well enough alone and took the new AP out of the equation and will live with the wireless router at one end of the house.

@wanderer, thanks for your help and feedback last week.


Report •

#15
September 19, 2010 at 09:20:57
I got the exact same problem.

My laptop is older (Compaq presario R4000) so i'm not surprised the driver may be not supported perfectly.

For me it was working perfectly the first week I installed Windows 7. But suddently, it stop working. I'm connected to a wireless router witch is connected to another Wireless router (gateway) in the LAN port. I'm only able to see my NAS and another PC connected to the first wireless routeur and can't ping the other routeur (gateway). Seems to be exactly like you...

I did the same thing as you, trying with another network adapter and it's working.

So if somebody also is having the problem and solved it, i'll be glad to ear an answer !


Report •


Ask Question