I'm having a problem with my wireless router as I switch from cablemodem to DSL. Can someone help me straighten this out?
One thing I've noticed is that AT&T's DSL modem gives itself the LAN IP 192.168.1.254. However, my wireless router calls itself 192.168.2.1 (and the computers on my network have 192.168.2.* IPs). I note that I can't access the DSL modem from a web browser when I connect it through the router, but I can access the wireless router.
When I try to access webpages, they load very slowly. As in, I can get the occasional graphic or title, but almost nothing else. It says "Waiting for " at the bottom of the browser window, and I frequently get the "An Internet cable is unplugged" pop-up. I get the same behavior when I try to access the DSL modem via its own IP.
This router worked flawlessly with my cablemodem, and I hadn't changed any of the settings. The DSL modem works fine when I connect it directly to my computer.
Here are some shots and copy/pastes of the router's status screen I took in the process of trouble-shooting.
http://dl.dropbox.com/u/338749/screenshots.doc
http://dl.dropbox.com/u/338749/status2.txt
http://dl.dropbox.com/u/338749/tracert.txt
When I go into my modem's configuration, I see it's using PPPoE to log in, But when I change my wireless router to use PPPoE and enter the userID and password I set up, it just never connects, all it says is "Dial On Demand (PPPoE)." and I don't get DNS.
You can leave an optional "tip" with Mahalo's virtual currency, Mahalo Dollars. If you are asking a difficult question that might require some research, or if you'd like a wide variety of feedback, a higher tip often leads to more answers to your question.
M$3 Answers
your DSL modem gets assigned a IP WAN side taht is routable on the internet.
You Router does the same thing on the WAN port.
Both act as DHCP servers an assign 192.*.*.* addresses insdie on the internal ports.
These IPs are non-routable hence behind the Router you'd never be able to connected to the 192. IP of the modem.
So here's a diagram.
DSL Wan Port- IP 68.68.*.*
Internal Port(s)- IP 192.*.*
Router WAN Port- IP - 192.*.*.* (because this is leased from the DSL Modem
Internal Port- IP 192.*.*.* (range)
Computer IP- 192.*.* (leased from Router)
(All data flows down or up through this exact sequence)
If you plugged either of these in the wrong ports on the DSL/Router you could get a conflict. For example if you tried to plug the DSL into the Internal Ports on the Router they'd both try to assign IPs to the same Subnet and you'd get nothing.
Also under certain circumstances you can get conflicts from a MS Win system running internet sharing. Since ICS acts like a server and uses an IP of 192.*.*.* which sometimes conflicts with the router's IP.
I'd also try hard-reseting you router. Make sure its obtaining its IPs via the WAN via standard DHCP and not some weird PPoE or DSL setting which some routers have.
Make sure the Router says its getting assigned an IP. And it looks like an IP that your modem would usually lease to your computer. Keep in mind this is the IP it uses WAN side while internally it uses a 192.1.*.* IP address as the host gateway from the subnet.
I'm in a rush hope that helps. :)
You can leave an optional "tip" with Mahalo's virtual currency, Mahalo Dollars. If you are asking a difficult question that might require some research, or if you'd like a wide variety of feedback, a higher tip often leads to more answers to your question.
M$
Since you can connect to the internet, that tells me there is a problem with the quality of the connection and a possible conflict. Since the data is getting there, just extremely slow, there may be an issue with the IP addresses. Think of the IP addresses like a street address. The data is using the IP address to know where to go. If there is a conflict or inconsistency with the addresses, it is difficult and sometimes impossible to get to the correct location. Here are some of the things I would try:
1. Reset the router to factory defaults and follow the installation instructions.
http://www.smc.com/files/AL/MN_SMC2804WBR_MN_E.pdf
OR
2. Turn off the DSL Modem and router. Turn on the modem and wait for complete connection. Turn on the router.
OR
3. Change the IP of the address of the router to 192.168.1.2
You can leave an optional "tip" with Mahalo's virtual currency, Mahalo Dollars. If you are asking a difficult question that might require some research, or if you'd like a wide variety of feedback, a higher tip often leads to more answers to your question.
M$
good points about WiFi. And changing the IP could help avoid conflicts as I outlined.
It's starting to look more and more like something's screwy about the way the router is routing. (See my comment to the other answer, above.) I haven't tried restoring the router to factory defaults yet, given that I really don't want to lose all the port forwards I have set up and there really aren't all that many settings to change to begin with. But I took a screenshot of them so I can add them back if necessary, I guess.
We had to switch the router and hardware to 10.0.0.1 local numbers and then arbitrarily assign a high number to the credit card machine, like 10.0.0.6, and the computers had to just pick up their IPs when they were turned on. The printer was the fax machine so it always stayed on. We were able to hard-assign the credit card term right on its screen. Not competing for space with printer or anything else...problem solved.
You can leave an optional "tip" with Mahalo's virtual currency, Mahalo Dollars. If you are asking a difficult question that might require some research, or if you'd like a wide variety of feedback, a higher tip often leads to more answers to your question.
M$
At the moment, the DSL modem is assigning the router the IP 192.168.1.64. This means when I try to change the router's IP to 192.168.1.1, it complains that it's on the same network.
Looking at the tech readout on the modem, it appears the modem's DHCP has a range of exactly one IP address: 192.168.1.64.
I found a way to put the modem into "bridging" mode, with the PPPoE handled through the wireless router or computer. I tested this mode with my laptop on PPPoE and was able to connect that way, but when I put my PPPoE details in the router, it seemed to get a connection, but didn't pass that connection through to any of my computers connected to it.
ok. Maybe I didn't explain that well.
The router if setup correctly should have two IPs. One is used internally and one externally. They cannot conflict because they're on seperate IP subnets and 192. addresses are non-routeable.
So it could have WAN side: 192.168.1.64 (assighned via DSL Modem)
the have a Internal IP: of 192.168.1.1 (this would not conflict with the DSL Modem using the same IP because the IP is non-routeable and there different subnets; with NAT trafersal the router has to change the IPs on the internal and to another IP on the WAN side)
The Modem also has two IPs.
On the WAN side: it might have something like; IP 68.68.68.68
On the internal side: it would use something like IP 192.168.1.1
So here how you packet routes:
Start at Computer 192.168.1.100
sent to router 192.168.1.1 (most likely not 64; labeled Gateway in Windows TCP/IP protocol)
the packet's headers are changed to the routers WAN side IP 192.168.1.64 (i'd bet) (leased from modem)
now it travels to the modems IP (which is the router gateway & DHCP) IP 192.168.1.1
the packet's headers are changed to the routers WAN side (routeable Internet IP) IP like 68.68.68.68
The router and modem respectively keep a map of each address to each address. So it knows one IP maps to another.
The trick are your cables plugged in right.
If you plug the DSL ethernet cable into the internal ports on the Router YOU will get conflicts.. Because you'll have two DHCP servers (Modem & Router) trying to issue IPs. and more than likely they'd use the same IP as gateway. Even if they didn't and say you PC got an IP from the router it has nothing plugged into the WAN port so you data goes know where. Hence no net connectivity.
Second if you had DMZ turned on on the router this could possiblity happen.
So make sure you cables are correct. If you can get the router to act as the PPOe that's great but if not that's ok too; not necessary though.
DSL -----cable---> WAN Port (rotuer)-----LAN Port off Router cable runs too ---->Computer
the back of the router will have ports
LAN LAN LAN LAN WAN
] ]
http://www.comptechdoc.org/os/linux/manual1/router.html