DHCP is not handing out IP/Computer can't reach the Router?

SDPotter

Reputable
Dec 2, 2016
3
0
4,510
Hi! I help run the network for a Non-profit. One of the employee's moved to a new office. Originally there was no CAT5 connection in the office so one was set up, leading to, I believe, the main router. It connected perfectly and then suddenly a couple days ago stopped working.

So when we go to the Network Connections in Control Panel we have this:
loiEFfK.png

Properties of every computer in the building looks like this:
pKwzsKv.png



3CSwh1r.png

Turning the DNS to automatic simply switches the text on the Ethernet icon on Network Connections to "Unidentified Network"

Here is the ipconfig/all
C7QhjNP.png



So an additional list of things I've tried:

  • - Disabled and Enabled the Ethernet connection
    - Updated the Drivers on the Ethernet connection
    - Uninstalled the Hardware via Device Manager and Scanned for New Hardware
    - Unplugged the CAT5 and plugged it back in
    - Restarted the Computer
    - ipconfig /release (usually met with an error of "no valid IP address has been configured"
    - ipconfig /renew (met with Windows IP Configuration hanging)
    - Ran Windows' Network Diagnostic which resulted in error about not being able to reset the Ethernet connection (I believe so anyways, this happened yesterday so I'm not remembering all details)
    - Tried to set a static IP

The one single thing I haven't done is power down the router itself. I looked for other issues where people's networking was being set to 169.x.x.x but none of the previous questions & answers solved anything.

Computer is an older Inspiron in a slim case if that helps anyone. I've tried to provide as much detail as I can. I tried transferring more pictures via Bluetooth to my phone but the transfer connection was spotty and I didn't think to just take pictures with my phone.

Any help would be much appreciated!
 
Solution
The 169..... etc. IP address shown in the ipconfig /all results is one of the IPs that Windows assigns itself when an IP address cannot otherwise be obtained.

The following sentence from your post caught my eye:

"Originally there was no CAT5 connection in the office so one was set up, leading to, I believe, the main router. It connected perfectly and then suddenly a couple days ago stopped working.Try another known working ethernet cable."

How was the connection set up: direct router LAN port to Inspiron LAN port? Wall jacks/patch panels? Hubs/switches?

Can you try another known working ethernet cable?

In any case trace the wiring path and look for some cable damage or connection problem.





Ralston18

Titan
Moderator
The 169..... etc. IP address shown in the ipconfig /all results is one of the IPs that Windows assigns itself when an IP address cannot otherwise be obtained.

The following sentence from your post caught my eye:

"Originally there was no CAT5 connection in the office so one was set up, leading to, I believe, the main router. It connected perfectly and then suddenly a couple days ago stopped working.Try another known working ethernet cable."

How was the connection set up: direct router LAN port to Inspiron LAN port? Wall jacks/patch panels? Hubs/switches?

Can you try another known working ethernet cable?

In any case trace the wiring path and look for some cable damage or connection problem.





 
Solution

SDPotter

Reputable
Dec 2, 2016
3
0
4,510


Turns out that the cable was plugged into a secondary switch outside the main office causing all the problems. We plugged it back into the main switch and poof everything fixed. I think someone may have fiddled with the cables down there.
 

Ralston18

Titan
Moderator
Glad to hear things are back to normal.

Probably should look into locking or otherwise securing the area.

Physical access could easily lead to some damaging hack or data theft. Or any number of costly results if communications and internet are lost.

Could be someone (co-worker, former co-worker) with a grudge being malicious. Or someone who believes that "network" problems will get them off the hook for a missed deadline or botched project. Some slacker hoping to maybe get sent home early.....

Or an untrained technician (any field) who sees no differences in ports and cables. Seen all of those sort of things happen - similar stories abound and are well known to many IT folks I am sure. E.g., the painter who was explicity told not to paint the cables. He didn't: just unplugged them all and dutifully painted the switches along with the walls.