Windows 10 systems can't seem to find internet when on the network
Windows 10 professional systems on a network with 2, Windows Server 2008 boxes.
I have 8 systems in the office at this time.
Sometimes I can have as many as 13 or 14.
Router: Netgear FVS336Gv3 Router in Dual WAN configuration. (Failover mode)
WAN1: TDS / Century Link T1 with Static IP
WAN2: Comcast Cable with Static IP
WAN 2 is primary connection
WAN 1 is failover link.
This had been working fine until this past week.
The Firewall is providing the DHCP
I have a block of addresses 192.168.1.180 - 192.168.1.250 being handed out.
The default gateway (Netgear Device) is 192.168.1.1
When I turn a Windows 10 machine on, or if I reboot it, I can't initially browse to the internet. I can see the servers on the LAN, however I cannot ping 192.168.1.1. It doesn't reply. I can ping the two servers IP's and they usually respond.
Now, interesting part! When I browse to the firewall IP: 192.168.1.1, sometimes I get "Page cannot be displayed". Sometimes I get to the firewall web interface.
When I am able to browse to the IP 192.168.1.1 using http I can then get out to the internet shortly after.
it's like the computer can't see the default gateway until I browse there.
Windows 10 and Windows 7 experiencing it.
Issue occurred this past week.
Thursday. So likely could have been from an update
Or this could be an ARP failure.
When the computer is rebooted, the arp table is cleared.
When the computer attempts to access the internet on reboot. It doesn't work.
Until I browse with the web browser to the 192.168.1.1
I ran fltmc from the command prompt. It shows two Webroot filters.
I am removing Webroot to troubleshoot.
Gathering diagnostic data.
Installed Netmon 3.4
I have 8 systems in the office at this time.
Sometimes I can have as many as 13 or 14.
Router: Netgear FVS336Gv3 Router in Dual WAN configuration. (Failover mode)
WAN1: TDS / Century Link T1 with Static IP
WAN2: Comcast Cable with Static IP
WAN 2 is primary connection
WAN 1 is failover link.
This had been working fine until this past week.
The Firewall is providing the DHCP
I have a block of addresses 192.168.1.180 - 192.168.1.250 being handed out.
The default gateway (Netgear Device) is 192.168.1.1
When I turn a Windows 10 machine on, or if I reboot it, I can't initially browse to the internet. I can see the servers on the LAN, however I cannot ping 192.168.1.1. It doesn't reply. I can ping the two servers IP's and they usually respond.
Now, interesting part! When I browse to the firewall IP: 192.168.1.1, sometimes I get "Page cannot be displayed". Sometimes I get to the firewall web interface.
When I am able to browse to the IP 192.168.1.1 using http I can then get out to the internet shortly after.
it's like the computer can't see the default gateway until I browse there.
Windows 10 and Windows 7 experiencing it.
Issue occurred this past week.
Thursday. So likely could have been from an update
Or this could be an ARP failure.
When the computer is rebooted, the arp table is cleared.
When the computer attempts to access the internet on reboot. It doesn't work.
Until I browse with the web browser to the 192.168.1.1
I ran fltmc from the command prompt. It shows two Webroot filters.
I am removing Webroot to troubleshoot.
Gathering diagnostic data.
Installed Netmon 3.4
ASKER
I verified that all of the computers are seeing the same thing.
If the computers can't obtain the correct ARP cached Mac Address for the firewall on boot, they get this false one.
Then in order to obtain the correct ARP cache entry I have to go to http://192.168.1.1
Has anyone seen this issue before with the Netgear Firewalls?
If the computers can't obtain the correct ARP cached Mac Address for the firewall on boot, they get this false one.
Then in order to obtain the correct ARP cache entry I have to go to http://192.168.1.1
Has anyone seen this issue before with the Netgear Firewalls?
it looks to me like some parts that are not windows 10 compatible
check also for firmware updates on the routers
check also for firmware updates on the routers
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think its an issue with the arp cache. I am waiting for their level 3 to respond in the morning.
Hi there,
Check the below links
i)
Try uninstalling any antivirus installed.
http://www.tenforums.com/network-sharing/11009-just-upgraded-windows-10-no-internet-connection-3.html
ii)
Check the below link
http://windowsreport.com/fix-netgear-wireless-adapter-problems-in-windows-10/
Check the below links
i)
Try uninstalling any antivirus installed.
http://www.tenforums.com/network-sharing/11009-just-upgraded-windows-10-no-internet-connection-3.html
ii)
Check the below link
http://windowsreport.com/fix-netgear-wireless-adapter-problems-in-windows-10/
I wonder if someone brought a router from home and plugged it into the office?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Glad to know the system is stable ...do update in case the issue crops up
ASKER
My resolution of replacing all of the network cables found an issue potentially with the cabling causing the issues with arp cache.
I replaced all cables going from the computers to the switch.
I moved the cables to ports lower in the port numbering.
I think there were multiple items which could have repaired the issue. It was a combination of many.
I replaced all cables going from the computers to the switch.
I moved the cables to ports lower in the port numbering.
I think there were multiple items which could have repaired the issue. It was a combination of many.
ASKER
- With webroot uninstalled, did the computer get to the internet right away?
Webroot has multiple connections to the internet. Multiple listeners so the conversation at this point is, is webroot causing a problem with TCP / IP communication after the upgrade to Windows 10 on the desktops?
Arp lookup shows a different Mac Address for the 192.168.1.1 gateway before I ping the gateway
00-DE-AD-10-75-00 (Kingtel Communication Corp) - Not sure what this device is.
Realtek PCIe GBE Family Controller is the network card
30-0E-D5-BA-7E-38 Mac Address of the local computer I am troubleshooting this issue on.
Later in the ping, the mac address comes back as 00-00-00-00-00-00
This happens just before I open the browser to http://192.168.1.1
The Arp cache then changes to the Mac Address of the Firewall WAN2 interface.
So it looks like the computers are possibly targeting some sort of interface when they are rebooted.
Then when we go to the http://192.168.1.1 they target the correct WAN interface or LAN interface on the firewall.
That is the exit point for the computers on the LAN>