Discussion Locked

IP addressing of DSL

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Scenerio: I have a DSL line installed and also a LinkSYS router. All is working fine internally with 10 workstations on a 192.x.x.x network. The problem I have is that the IP is being recieved dynamically and the IP that shows as my WAN connection is not one that I can ping from another computer outside the LAN. When I ping the DSL dynamic address it comes back with host unreachable. I need to get to that IP to run pcAnywhere on 1 workstation on that LAN. I have the ports forwarded and all thatbut the IP address cannot be pinged...and therefore pcANywhere will not work. HELP!

Thanks

4 replies

by ann777

I have exactly the same situation as you do. My DSL ISP only shows the 192.x.x.x ip address, not the real one. Windows only sees the internal, etc. There are two ways that work:

You can http: into your linksys router and look at the "status"(I am at work right now, not at home where my linksys router is... it might be a different tab label) tab, to see the current WAN ip address.

Or,

You can http://www.grc.com and click on the ShieldsUp! link and click on the scan ports. It willfirst return the ip address that it sees your computer on.

It's never been wrong, and both these methods work for me. I tend to use the later when I know the linksys router has been through a configuration change or a reboot due to a power failure... etc. Even though I shutdown my computer when not in use, I leave both the DSL modem and the linksys router powered on all the time; i've also configured the router to "Keep alive" the ip address. The ip address is kept alive, and does not change, unless I make a configuration change to the router or there's a power issue.

by ann777

A bit more info. Once you know the real ip address, you input that real ip address into your offsite browser. The linksys router shoud have forwards opened for 5631 to 5631 for UDP to the local ip addess of that server you wish to reach (192.x.x.x) amd there should be another forward opened for 5632 to 5632 for TCP to that same local port.

This discussion is closed to new replies.