SQL Server 2012 no longer has network connectivity!! Help!!
Our SQL Server network connectivity is broken! I can only get on it via a terminal from VMware.
Our server is set to a 192.168.0.x address, gateway 192.168.0.xxx. Ipconfig shows a 169.254.x.x address, I'm not sure why it is getting this.
Despite several re-boots I cannot ping it's IP address and several customer facing apps are failing. DNS looks OK, other servers with same settings are fine.
Can anyone help please!
Our server is set to a 192.168.0.x address, gateway 192.168.0.xxx. Ipconfig shows a 169.254.x.x address, I'm not sure why it is getting this.
Despite several re-boots I cannot ping it's IP address and several customer facing apps are failing. DNS looks OK, other servers with same settings are fine.
Can anyone help please!
masnrock
So this is a virtual? Are you having any issues with your virtual switch? Are there other VMs on the same system that have connectivity without incident?
ASKER
Yes its a VM. There are other servers running fine on the same virtual switch and have connectivity.
Can you set the static ip address? or already was static?
Hello, this should help sort you:
169.254.x.y is an APIPA address, it means that the adapter is set to DHCP.
Either:
A) You want to assign the server an IP through DHCP
In which case troubleshoot DHCP to figure out why it isn't getting an address, also follow step 1 in the next case as part of that.
Or more likely, B) You want to assign the server an IP statically
In which case the Server likely had a NIC removed and re-added in VMWare or re-detected the existing NIC as a new NIC for some reason, or someone maliciously or accidentally changed the NIC's settings.
To Resolve:
1) In vSphere verify that the VM is on the correct network, if not select the correct network.
2) Through VMWare console, open the NIC that should be on the 192.168.0.xxx network.
2a Change the settings of the NIC to have the correct static IP, default gateway, subnet mask, and DNS Servers in the NIC settings.
This should resolve your issue.
169.254.x.y is an APIPA address, it means that the adapter is set to DHCP.
Either:
A) You want to assign the server an IP through DHCP
In which case troubleshoot DHCP to figure out why it isn't getting an address, also follow step 1 in the next case as part of that.
Or more likely, B) You want to assign the server an IP statically
In which case the Server likely had a NIC removed and re-added in VMWare or re-detected the existing NIC as a new NIC for some reason, or someone maliciously or accidentally changed the NIC's settings.
To Resolve:
1) In vSphere verify that the VM is on the correct network, if not select the correct network.
2) Through VMWare console, open the NIC that should be on the 192.168.0.xxx network.
2a Change the settings of the NIC to have the correct static IP, default gateway, subnet mask, and DNS Servers in the NIC settings.
This should resolve your issue.
The 169.254.x.x address is an APIPA address. Thus the server could not initialize its IP correctly. Normally this mechanism is for dynamic IP and clients not being able to connect to the DHCP server.
Have you tried to disable autoconfiguration (command shell) in the guest:
Have you tried to disable autoconfiguration (command shell) in the guest:
netsh interface ipv4 set interface {nicId} dadtransmits=0 store=persistentSOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you can remove virtual switch, then add new virtual switch and take ip address from dhcp or add another free ip address manually
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You should keep your servers on a separate subnet from users and not run any dhcp in that address space.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Author found solution.