Saturday, March 23, 2013

Network from hell

This post might be a bit technical, so if you're boring, don't bother reading it.


So I was at work (I'm an IT library admin type person thing).

We had this problem pop up on Wednesday, where 4 computers couldn't connect to the internet.

Initially, I was told one computer couldn't get email, two couldn't connect to symphony, my own couldn't connect to Google.

People don't always tell me what's actually wrong. None of them had any internet connections at all.

I the ping the domain server, which is a 90.0.0.x address. Works fine. I can even access files on the domain network.

Change my DNS servers. Still can't get out. Hmm, must be vile monkeys.

I check IP config on each computer. 90.0.0.41.... 90.0.0.35...192.168.1.4... WHAT THE HELL

Where did you come from, random IP? I trouble shoot best I can, reset TCPIP stacks, winsocks, triflux capacitors, etc. WATER YOU DOING COMPUTERS!?!? After an enormous amount of walking around, I find out the second DHCP signal was coming through the wan port on a specific wifi router. This does *not* supposed to ever happen.

Disconnect all the wifi routers, and check DHCP. Opp, everything is back to 90.0.0.x like a good IP address should be.

I'm really getting sick of ipconfig /release and ipconfig /renew at this point (done atleast 50 times after making changes)

Computers still won't connect to the internet... what the hell man, what the hell

I decided to set IP addresses static... doesn't work. Just an idea, lets set them above the DHCP range. Set it to 130. Oh my gosh, it works!

So, I try 131. Doesn't work. 132, works, 133 doesn't work, 134 works... I don't believe there is anything about IP addresses being even making them work, but somehow, it magically worked that way all the way up to a tested 150.

None of this makes any sense to me at all.

So all in all, we got it working, but it still is broken... blegh

4 comments:

  1. May wish to consider the possibility that someone's got some interesting wifi hookups leaching off your network infrastructure. Could also potentially be an ARP Poisoning attack.

    ReplyDelete
  2. I was still having issues with every wifi router off.

    ReplyDelete
  3. Hmm, that's very strange. = There's a whole slew of things that could be potentially wrong with those systems.

    ReplyDelete
  4. Everything is broken FOREVER

    We're looking at upgrading and replacing our eth and switches/routers anyways

    ReplyDelete