Recommended Posts

Here's my setup:

I have a Motorola SB5100 connected to my telephone adapter for VoIP. The telephone adapter then connects to my wireless router (Linksys WRT54G). I have one desktop computer wired to the router and two laptops that connect wirelessly.

I am going on a trip next week and need to be able to connect to the desktop computer that is wired to the router.

I can use Remote Desktop Connection (RDC) within my home wireless network to connect to each computer remotely (by simply typing in the name of each computer in the RDC client).

But I need to be able to connect to just my desktop computer from outside of my own network (using another Internet connection). All of my computers, when connected to my wireless network, have the same IP address issued by Comcast. When I type that IP address into the RDC client on my neighbor's computer, it does not connect.

When I go to the command prompt and use ipconfig, the IP of my desktop computer is: 192.168.1.102

I tried following the instructions on this site : ?www.dslwebserver.com/main/fr_ind???ort.html

but that did not seem to work and I have set the ports back to the default.

On my router configuration page, I have Port Range forwarding set up as shown in the attached screenshot.

I also have ZoneAlarm, but even with ZoneAlarm shut down, I cannot connect.

Please help! I've tried to provide as much information as possible; let me know if I can provide anything else.

post-7801-1143157149_thumb.jpg

make sure that the local ip didnt change (192.). If you have a different computer on your local network try connecting from it to see if you are able. Make sure you allow RDC on all firewalls - incoming and outgoing. Or better - shut them down for testing purposes. Make sure that Terminal Services service is running on the machine you are trying to control. Then if you are able to connect locally go to www.dnsstuff.com (right top corner), www.myipaddress.com and get a public IP. If you have dynamic ip try service like www.<< spam >>. you'll install a small app that will monitor your ip and get a name mycomputer.no-ip.info.

I'm pretty sure you cannot use your WAN IP address to connect if you are inside your network. If you try connecting using a PC that is outside of your network it should work.

EDIT: Sorry, misread your post that said you were already trying it from your neighbor's PC.

What VoIP box do you have? Most of these boxes handle NAT and you would also have to forward the port on the VoIP box to the IP address you are using for the WAN connection on the WRT54G.

The easiest way to tell if the VoIP box is what is causing the issue is take it out while your testing. If the RDP connection works without the box then that is your problem. If it doesn't then it looks like you have another problem.

  Frank said:

What VoIP box do you have? Most of these boxes handle NAT and you would also have to forward the port on the VoIP box to the IP address you are using for the WAN connection on the WRT54G.

The easiest way to tell if the VoIP box is what is causing the issue is take it out while your testing. If the RDP connection works without the box then that is your problem. If it doesn't then it looks like you have another problem.

It is a D-Link VoIP box provided by AT&T CallVantage. I'm currently out of town, so I can't give you the exact model. But I do recall that there are some settings within the box's configuration page that have to deal with firewall settings, etc.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.