:huh:
To recap from my other thread, I got Ultimate speeds after I did a factory reset on my Cisco/Linksys EA2700 POS. DHCP is enabled for LAN, starting at 192.168.1.100, router is 192.168.1.1. For some inexplicable reason, devices are now not pulling a 192.168 IP, but are pulling 10.134.116.* addresses, with the Gateway and DNS being the same at 10.134.116.183, IP lookup says it's a Cox address out of Wichita. Now those devices can get to the internet as a normal 192.168 address would, but obviously they can't see my internal servers that have 192.168 numbers.
If I do a release/renew on any of those devices, it still pulls a 10.134 numbers. If I try to manually set the IP to the correct 192.168 info, it won't do anything. No internet, no server, nothing.
I am so ready to take a big fking hammer to all of it. The really weird thing is that the PC I'm posting this from, is on DHCP and is pulling a correct 192.168 number.
I just tested a really strange theory, that the results make no sense. I have an 8 port TrendNet Gig switch. I have a streaming media box for TV. It was pulling a 10.134 address no matter how many times I told it to renew. Just for fun, I pulled it off the switch and plugged it into the EA2700. It now pulled a correct 192.168 address is is working perfectly fine. Now remember, the PC I'm on is on DHCP with a 192.168, it's plugged into that same switch the streamer was on.
This really shouldn't be difficult, I don't understand where those 10.134 are coming from and how I am getting them on an internal network.
:huh: :huh: :huh:
Correction: IP Lookup says that it doesn't know who that 10.134 belongs to. If you do a tracert on it, it goes out to a 70.169.88.92 which is a Cox address from Wichita, then comes BACK into my network and finalizes at the offending device.
↧
