Leigh Kalbli
asked on
no wan with static ip server 2012 esx
I have a multi host cluster using a Distributed Switch on esx. I have 50 ports and 29 available. Currently there are at least 6 vm's running server 2012 with static LAN addresses and have WAN connectivity. I just created 6 more vm's and assigned static addreses but cannot get WAN. I have verified subnet/gateway etc. I am able to ping the domain controllers and gateway when there is a static assignment. When set with a DHCP address, the servers have WAN. I have tried to remove the virtual NIC, reset tcp/ip stack. I cannot figure why i get no connection on a static address but do on DHCP. I have even tried to enter the DHCP settings manually, exactly the same. Any ideas?
What is the difference between DHCP assigned IP Addresses and the IP Addresses you have assigned STATICALLY ?
ASKER
Thanks for the response. Nothing is different. DHCP is handing out 192.168.0.0/24, 255.255.255.0 GW 192.168.0.1 DNS 192.168.0.60 and 61. ive aded our ISP's public DNS record to both the DHCP scope and Static and still same behaviors.
can you currently SWAP an IP Address which works, with an IP Address which doesn't as a test!
ASKER
Let me try it out and i will follow up. I can say that when i let the vm get a DHCP, i ping the address i wanted to statically assign to ensure it wasn't out on the network somewhere. I will have results shortly.
ASKER
Same behavior. I also added a second vmNIC and allowed it to pull from DHCP. I had WAN with it but then tried to assign the same address that was given out DHCP to the NIC with the same settings and then no WAN.
That's not what I meant.
Using an IP Address which is known to work, which is currently allocated to one of your working servers.... use this IP Address in a new VM, and new IP in the old server.
Using an IP Address which is known to work, which is currently allocated to one of your working servers.... use this IP Address in a new VM, and new IP in the old server.
ASKER
Sorry for misunderstanding. I took a working IP from a vm and applied it exactly to the new VM and everything worked. Putting the new IP in old server caused WAN connection to be lost.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Both VM's have the same windows firewall Group Policy applied. I will look in the firewall appliance and see if i can find anything as well.
upstream...
ASKER
Turns out someone pulled the up and assigned it to a device without updating IPAM. After removing it, the server operated correctly.