• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

WEIRD problem: Can't access any sites with the IP 12.*.*.*

Balt

Lifer
My apartment complex has some sort of proxy server set up I think (each apartment has a net connection provided). Also I've noticed MY ip starts with 12. Is it possible they configured their proxy incorrectly? It's annoying as hell.


I wouldn't put it past them. 😛
 
They probably configured either the subnet mask wrong (Run Winipcfg and see if you have a 255.0.0.0 subnet mask) or didn't configure their router right..

- G
 
Garion,

You are partially correct. It does list the subnet mask as 255.255.0.0

What a pain in the arse :|


Thanks for the info
 
The x.x part is what your computer considers to be on your local LAN - If any other 12. addresses are in that part, you won't be able to see them. Your network admin might have also messed up the router config, too. If that's the case, nothing you will do will make it work. It's definitely messed up, however, so call your admin (or whomever does it) and get them to fix it.

- G
 
One specific thing to ask your admin.. If he's got a Cisco router, make sure he's got the global command ip classless on the router. 12.x.x.x is a "Class A" network - That is, it was originally meant to have the ENTIRE 12.x.x.x address range assigned to one company as one big network, not split up and used on the Internet. Some routers will see that it's a class A and automatically infer a subnet mask of 255.0.0.0. Of course, it thinks the 12.x.x.x network is local and will never forward to the Internet where it should go.

- G
 
I've seen an idiotic corp that I used to work for set their internal addresses to a set of real world IP's. Don't know why they did it but they did. One of their network guys (if you can call morons that) said it worked fine but the users couldn't go to any addresses that were on the 170.x.x.x range.

You might have the same type of thing, but there can't be that many losers in the world....
 


<< You might have the same type of thing, but there can't be that many losers in the world.... >>



you'd be very surprised.
 
Yeah, they have some serious goons running the network here. I won't bore with the other tales of woe I've experienced during my short time here. 😉

Thanks for all the help, guys. I'll see if I can get them to fix it, though I don't have much confidence they will. 😉
 
Back
Top