Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, August 29, 2019 3:00 PM | 1 vote
I have issues connecting to the network when I statically assign an IP address to certain WIN10 Machines. (HPZ8)
Adapter Config:
IP: 10.0.50.41
Subnet Mask: 255.255.0.0
Default Gateway:10.0.0.1
DNS: 8.8.8.8 8.8.4.4
The original issue was detected when the NICs were "Losing" their IP configuration after reboot.
- After deleting old registry entries ... the NIC now "Remembers" It's IP configuration after reboot.
Tests Performed:
Step 1: Enable DHCP on the Adapter: No network access after reboot.
Step 2: Unplug the physical cable and re-insert (Using DHCP) : Network access is available.
Step 3: Set a STATIC IP (As desired) on the Adapter, It then connects to the network and correctly remembers ipv4 configuration.
Step 4: Reboot the machine. IPv4 configuration remains: NO network access.
Step 5: Renable DHCP. NO Network access.
Step 6: Restore Static configuration
Step 7: Reboot without ethernet cable (configuration is remembered)
Step 8: Re-insert ethernet cable with static configuration. Network Is available,
Further Information:
- Drivers are up to date and current
- Windows is up to date and current
- Devices have been reinstalled (devmgmt) multiple times with out success. Behaviour persists.
All replies (12)
Thursday, August 29, 2019 6:45 PM
Hi,
Thanks for posting in Technet.
It may not have anything to do with your static IP. When you experience the problem, are you able to ping the router and websites, and can you access the router's GUI? Did you check ipconfig to see if your static IP address is still correct? Did you try a different static IP address?
You need to make sure the address you use is not in the DHCP range of your router. Otherwise, that address might be automatically assigned by the router to another device on your network, which will cause connectivity issues.
Best Regards,
Eric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, August 30, 2019 7:44 AM
Also... I have now completely reloaded windows and the issue persists :)
Except this time.... the Ethernet Adapters have new names! and are numbered from 5 to 8...........??!!
Friday, August 30, 2019 9:17 AM
Hi Eric,
To summarise...
If I reboot the machine WITHOUT the network cable plugged in. Then plug it in... the configuration works successfully.
If I reboot the machine after this, leaving the cable in... on boot it does not connect until I repeat the above process?
(Yes, I checked all your steps)
Friday, August 30, 2019 11:41 AM
A further point of note, is that I can see the adapter in the device management but not in netsh?
Monday, September 2, 2019 8:18 PM
Hi,
Thanks for your reply.
Please make sure that you are using an elevated command-prompt, otherwise it won’t have access to everything.
Please check your firewall. You can try to close firewall for a while and check whether the issue still exist.
Best Regards,
Eric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, September 3, 2019 8:38 AM
Hi Eric,
There is no firewall. Windows, or otherwise and yes, I have been using elevated command prompt.
And yes the issue persists :)
Thanks for your continued support.
Kind Regards
Thursday, September 5, 2019 1:10 PM
Hi,
Thanks for your reply.
Do you means you can connect to internet via DHCP but fail to connect tro internet when set static ip address?
Maybe there is something wrong in your setting, I suggest you to record the ip address, subnet mask,default gateway and DNS when use DHCP.
Then set these data as static and check whether the issue still exist.
Best Regards,
Eric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, September 5, 2019 2:16 PM | 1 vote
Hi Eric,
There is no issue with the network settings, the behaviour is the same whether static or DHCP.
Scenario 1:
1. Restart the machine without ethernet cable attached
2. Insert cable
3. Connectivity (yay!)
====================
Scenario 2:
1. Restart the machine WITH ethernet cable
2. No connectivity (boo :( )
3. Unplug and replug ethernet cable in (boo!)
It isn't practical to take out and reinsert the ethernet cable every time a reboot is required. We literally have HUNDREDs of these machines.
Monday, November 11, 2019 10:58 PM
Have you made any headway since early September? I'm curious as I have exactly the same issue.
Saturday, November 23, 2019 4:12 PM
WOW I WONDERED THIS TRICK ALSO WORKED ME
THANKS YAY
Tuesday, January 14, 2020 2:36 PM
Did you ever find a reason this was happening or a way to fix it?
Wednesday, January 15, 2020 2:14 PM
Likewise, I'm still looking for a reason or long term fix... We see this, periodically, on many of our VMware windows servers. Seemingly always after an automatic windows update scheduled reboot - but not every time windows reboots because of an update.
When I login to the console, I see the network adapter, connected, with my static IP info there, but with "no internet connection".
Universally, all I've had to do is right click on the network adapter, disable it, and reenable it. Immediately it comes back connected appropriately.
This happens across multiple versions of windows, with multiple NIC types applied to the vms. For us, right now, I'm just trying to rely on our system monitoring/paging software and hoping I can catch that the server is down quickly enough in the morning before end users experience issues...