asked on
after power failure no one can access internet or servers. everyone gets 169 address
after a power failure one of my switches was fried. I replaced the switch, however, everyone still cannot access internet or servers.
I cannot ping or telnet into my router or any server
everyone gets a 169 ip address, If i try entering manual information it does not work either
I have called our Isp and they can ping and see the router but say my issue is the first hop (which is connected to the new switch---if I move it to a different one its the same thing)
also wireless does not work
any thoughts??
I cannot ping or telnet into my router or any server
everyone gets a 169 ip address, If i try entering manual information it does not work either
I have called our Isp and they can ping and see the router but say my issue is the first hop (which is connected to the new switch---if I move it to a different one its the same thing)
also wireless does not work
any thoughts??
DHCPRoutersNetworking
Last Comment
itsup23
ASKER
Yes I did consider that (I didn't set the network up)
However I have no access to any server or the internet only local on my machine
However I have no access to any server or the internet only local on my machine
Are you onsite? You will need to log into the console of the server to setup DHCP.
Alternately, you can do it on the switch - what make/model?
Alternately, you can do it on the switch - what make/model?
ASKER
i will try on the server now through the console.
it was a dell powerconnect 2716 and I replaced it with a Dlink DGS-1024D
it was a dell powerconnect 2716 and I replaced it with a Dlink DGS-1024D
ASKER
servers are all vm machines and plugging in directly to the physical server doesn't allow me to enable one of them as dhcp server
Neither switch supports dhcp server functionality. So your addresses must have come from the router or the server.
Do you know the network range you use there?
As for the VMs, what are you running as the Host OS? Is it VMware or Hyper-V?
Do you know the network range you use there?
As for the VMs, what are you running as the Host OS? Is it VMware or Hyper-V?
You went from a managed switch to an unmanaged switch, perhaps you have VLANs setup before?
How many DHCP scopes do you have setup in your server?
On your servers, are they on different subnets? If so, perhaps you were sending tagged and untagged traffic to the ESX host and now you're unable to.
What device is doing the routing in your environment? How many IP enabled interfaces are enabled? Are they physical, sub-interface? If sub-interface, what is the dot1q tag associated with them?
How many DHCP scopes do you have setup in your server?
On your servers, are they on different subnets? If so, perhaps you were sending tagged and untagged traffic to the ESX host and now you're unable to.
What device is doing the routing in your environment? How many IP enabled interfaces are enabled? Are they physical, sub-interface? If sub-interface, what is the dot1q tag associated with them?
Try a static IP (i.e. 192.168.1.123 or whatever your subnet is supposed to be) and see if you can't get access to the LAN. Hardwire the router/gateway number.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
ISP was causing issue
Either reconfigure the switch to be your DHCP server or set it up on your server.