Home / server / Questions / 795642
In Process
Cam
Asked: 2016-08-09 14:07:00 +0800 CST

No Network Access with Static IP

  • 772

Have encountered this issue now on 3 servers, 2 were in pre-deployment stage, but this one happened after a crash.

Environment: VMWare ESXI 6.0u2 running on Dell Poweredge R510 Server with E1000E Adapter.

After a recovery from a crash server is working for four days, noticed today in troubleshooting a different issue, we were unable to ping the server or connect via RDP.

Logged into the server using the Vsphere Client, and Windows is not activated, and network access is in yellow.

Call MS Support, as Product Key is unable to be activated, and we get it going in about 15 minutes. Reboot the Server and Windows is now genuine, but am still seeing no network access.

Having seen this before on 2 other servers, I knew I could set the adapter to DCHP and it worked. I then created a new identical adapter in VSphere (E1000E) again, and gave it the static settings, but it would not connect.

Results of ipconfig /all

Ethernet adapter Ethernet 0:

Connection-specific DNS Suffix . :
Description. . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
Physical Address. . . . . . . . .: 00-0C-29-20-08-91
DHCP Enabled. . . . . . . . . . .: No
Autoconfiguration Enabled . . . .: Yes
IPv4 Address. . . . . . . . . . .: 192.168.15.26(Preferred)
Subnet Mask . . . . . . . . . . .: 255.255.255.0
Default Gateway . . . . . . . . .: 192.168.15.1
DNS Servers . . . . . . . . . . .: 192.168.0.26
                                   127.0.0.1
NetBIOS over Tcpip. . . . . . . .: Enabled

I have tried the registry DefaultGateway empty fix, it was empty but deleting it, and rebooting did not work, and editing it did not work.

Have attempted editing it multiple times in the GUI, and tried setting it manually via netsh as well.

Any help or insight would be greatly appreciated, Cam

EDIT:

PS C:\...> route print
Interface List
 24...00 0c 29 20 08 91 .....Intel(R) 82574l Gigabit Network Connection #3
   1......................................Sotware Loopback Interface 1
IPv4 Route Table
Active Routes:
Network Destination  Netmask        Gateway            Interface  Metric
0.0.0.0                0.0.0.0     192.168.15.1 192.168.15.26  266
127.0.0.0             255.0.0.0        On-link     127.0.0.1    306
127.0.0.1         255.255.255.255  On-link         127.0.0.1    306
127.255.255.255   255.255.255.255  On-link         127.0.0.1    306
192.168.15.0      255.255.255.0    On-link        192.168.15.26 266
192.168.15.26   255.255.255.255    On-link        192.168.15.26 266
192.168.15.255   255.255.255.255   On-link        192.168.15.26 266
224.0.0.0              240.0.0.0   On-link        127.0.0.1     306
224.0.0.0              240.0.0.0   On-link        192.168.15.26 266
255.255.255.255   255.255.255.255  On-link        127.0.0.1    306
255.255.255.255   255.255.255.255  On-link           192.168.15.26 266
Persistent Routes:
  Network Address                    Netmask    Gateway Address    Metric
                   0.0.0.0                       0.0.0.0          192.168.15.1     Default
                   0.0.0.0                       0.0.0.0          192.168.15.1     Default
IPv6 Route Table
Active Routes:
  If Metric    Network Destination                  Gateway
  1       306  ::1/128                                       On-Link 
  1       306  ff00::/8                                       On-Link 
Persistent Routes:
   None

I then followed what @mzhaase said to do and change from an E1000/E to a VMXNET driver, and added an additional adapter. The VMXNET does the same thing, and allows internet on a non .26 ip and on dhcp, but will not stick on .26

I also attempted creating a new install on a new vhd in vmware, and it also had the issue with .26 I reverted the vhd setup and put back in the original install.

At this point I think the issue is either in VMWare (6.0u2) or at our firewall PFSense. I'm going to work with my network engineer, to see if we can troubleshoot the firewall today.

networking vmware-esxi windows-server-2012-r2

2 Answers

  1. So the resolve was a known Ghost Adapter Issue in VMWare:

    Resolve was to log into the server,

    Run CMD

    Enter: set devmgr_show_nonpresent_devices=1

    Go into Control Panel -> Network & Internet -> Network Sharing Center and you should see atleast 2 adapters.

    One of them will have the held onto ip settings, change the adapter to dhcp, and then change the semi-working adapter to the static ip address and I was back in business.

    • 1

  2. I don't know if you will see this but I finally figured it out. There's a couple of things that were holding me back despite doing all the standard stuff.

    First, go onto your router 192.1.X.X and advanced and LAN IP there you'll see use this router as DHCP so lower the max value of that to something like 150.

    Second open Windows PowerShell as administrator and type Get-NetConnectionProfile

    This will show some details. If the network shows public this explains a lot of problems with static IP addresses. Type Set-NetConnectionProfile -InterfaceIndex <INDEX NUMBER SHOWN> -NetworkCategory Private

    Third go to network and sharing centre right click your adapter/details/internet protocol 4/details then set the IP address to 192.169.0.<any number above 150>

    To get the rest of the details you need open up cmd and type ipconfig

    Apply those settings then close it.
    Now add the services as standard.
    Then the inbound firewall rule to the IP address you set

    • 0