• 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.

should i be able to access 192.168.0.1 ?

gryfon

Member
i'm sorry if this is a noob question, but shouldn't i be able to access my router default config console (default router ip is 192.168.1.1) when i statically defined my ip as 192.168.0.1 ? Or is it not ? By access, i mean http 80 port.

What about file sharing ? if i have a computer on 192.168.1.2, can my computer on 192.168.0.1 access it too ? i'm aware that windows network neighboorhood doesn't access across different subnet masks, but can i type \\192.168.1.2 on explorer ? ATM i cannot, but i'm curios whether it actually *can*.

BTW, why counter strike didn't list server on 192.168.1.x (the client that try to connects is on 192.168.1.x also), but when i try to connect manually using console command 'connect 192.168.1.xx' it worked. Does lan games necessarily be put on 192.168.0.x to see each other ?

thanks,
gryfon
 
If your on a different subnet you will not see each other. If your using a standard class c subnet mask, 192.168.0.1 & 192.168.1.1 will not see each other.
 
If you are talking about consumer routers then you are on a network with a Linksys router. And you are attemption to contact the location where a Netgear router usually resides.

If you want to access your Linksys router go to 192.168.1.1.
 
You need to understand subnetting. If your subnet mask is 255.255.255.0, then no you will not. However, if your subnet mask is 255.255.0.0, then should should be able to.
 
When you statically define your ip adress, you have to make sure that the subnet mask is the same as that of your routers. Your routers subnet mask is probably 255.255.255.0 so when defining your ip adress, make sure that the extra 255 is on the end so it would be 255.255.255.0 and not 255.255.0.0.
 
Back
Top