Name: problemsolver Date: October 26, 2007 at 04:25:40 Pacific Subject: DSL Network Conflict OS: WindowsXP CPU/Ram: 2.4ghz/512 Model/Manufacturer: Intel Pentium IV
Comment:
I have a Wireless Router which has the html-admin page. My DSL modem has the same page. Router's page opens from 192.168.1.1 and DSL modem's page opens from 192.168.1.2:2800. I also have two lan cards on my server pc and I have shared the connection. Yesterday the net was working fine on the other pc as was the lan (pings, fileshares). Then the DSL disconnected for a minute and then when it reconnected it didn't work on any of the PCs. I disabled the lan and the DSL started working on the server. When i enabled it, it stopped working. On the client pc, it just stopped working altogether.
When i ping the client pc, it doesn't work. When i write \\clientpc in run, it does go to the shared files.
When i plug in the DSL modem into the Wireless Router's WAN node, the internet doesn't work. The lan however works then. When the dsl is plugged into the router, the router admin page opens but not the dsls. Now when i plug the DSL in the PC's 2nd lan slot, and disable the lan, the DSL router page opens (of course), but when i enable it, the router's page opens and the DSL stops working
Your router can't route if the lan and modem are in the same subnet. I have no idea why you would be sharing your servers nic [to other pcs?] when you have a router.
Here is what your config is supposed to look like:
modem 192.168.1.2 should be giving the WAN port on the router an address like 192.168.1.1. On the routers LAN side you should set the gateway to 192.168.0.1 and dhcp server to a scope of 192.168.0.2-x x=how many pcs you have connecting. PCs/server would all be cabled/wireless to the router.
Are you ready for where Microsoft wants you to go today?
The only other choice might be to change the modem to be a passthrough device so that the wan ip ends up on the router's wan port. I prefer that way so that the modem isn't an ip device anymore.
I read it wrong and answer it wrong too. So get off my case you peanut.
See the problem is the internet did work on the client pc but it suddenly stopped. Stress on "suddenly".
And it shows on the client pc that the internet is connected on the server PC, but it doesn't browse. Firewall is off on both PCs, so thats not the reason.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE