Feb 26, 2011 20:28
.. do unprovisioned cable modems hand out unrouted 192.168.100.xx IP's instead of just not answering DHCP like they used to? Is there any logical reason?
("Because people scream at us when their computers get self assigned IP addresses and this makes them think it's their platform so they'll call their platform support" is not a reason I consider
Leave a comment
Comments 13
Reply
This is very occasionally useful in that it lets the tech instruct the user over the phone to configure the modem via the internal web interface, but I agree it hardly makes up for all the rest of the false positives it inflicts during troubleshooting.
Reply
Reply
Reply
Reply
I'm shocked!
(Now if I could only find the real/equivalent model for my Dell Mono Laser MFP 1125 so I can find a driver that will work with a Mac...)
Reply
Reply
Reply
It's that there's a rash of cable modems out there that will give out a single public IP on DHCP to the device they're provisioned to, but *also* give out an IP to other devices, which breaks a lot of device-side detection that the connection is in fact down. Any frontline tech can tell if the platform isn't getting an IP from the router with minimal training. But if the customer is trying to use their own external router and the only error they get is double NAT, and they escalate up to my level because the "NAT" is an unrouted 192.168.100.xx .. that's just pure rectal pain. It'd be simpler if they just only gave DHCP to the device they've registered, and answered HTTP at 192.168.100.1 just for config. The false positives from the former are a serious training problem.
Reply
Reply
Leave a comment