Remote connection

chrisx03 · Post by **chrisx03** » Tue Oct 07, 2008 9:46 pm

i am having a problem connecting through a remote connection. i have set up accordingly to instructions and my own knowledge. but of course my knowledge is very limited in remote connections. i have bellsouth dsl the modem is a Motorola and it is connected to a linksys router, i do not have the model number at hand but anyways i forwarded port 3389 on the router and also on the modem. i also set up my pc of course with the remote desktop by turning all of the services on. I went to http://www.canyouseeme.org and everything and all ports were detectable. So i also setup remote access and port forwarding on my motorola modem with the bellsouth dsl service. so the result of all of this is i can access my modem form a remote location having access to my modem settings ...etc through a browser of course. i cannot ping the ip at all, when i try to connect to the remote pc this error pops up

i tried going through the list and seeing if any of these errors were the culprit. i must be missing something, any help please?thank you

....

Post by **YeOldeStonecat** » Wed Oct 08, 2008 5:06 am

chrisx03 wrote:ii have bellsouth dsl the modem is a Motorola and it is connected to a linksys router, i do not have the model number at hand but anyways i forwarded port 3389 on the router and also on the modem.

It sounds like you have a double NAT situation here...as the Motorola modem is actually a combo modem and router. Have you reconfigured it to run as a pure modem, in bridged mode? So that your Linksys is doing the PPPoE and obtaining the public IP address?

chrisx03 · Post by **chrisx03** » Wed Oct 08, 2008 6:02 pm

Have you reconfigured it to run as a pure modem, in bridged mode?

How do i come about in doing this? i will make sure that my router is doing PPPoE and getting the public IP adress in the mean time.

chrisx03 · Post by **chrisx03** » Wed Oct 08, 2008 7:08 pm

i have set up the modem to brige in the setup and set up my router to PPPoE and now my internet is working again but im still having the same problem with the same error. and now i cannot access the modem setup through my browser.

Post by **YeOldeStonecat** » Wed Oct 08, 2008 7:35 pm

OK so your router obtains the public IP address on its WAN interface now?
Don't need to hit the web admin of the modem anymore..nothing to configure. If you ever have to down the road, set a static IP on your PC temporarily, say the modem has an internal IP of 192.168.0.1, set your PC to 192.168.0.10/255.255.255.0, you can leave the gateway and DNS blank, log into your modem to do whatever, when done, turn your PCs TCP/IP back to obtain auto again.

Ensure remote desktop is enabled on your host PC
Ensure remote desktop traffic (tcp port 3389) is allowed through any software firewall on it
Try testing it internally on the network first if you have a second PC available, using the LAN IP address of the host PC.
Ensure the host PC has a static LAN IP address, and port tcp 3389 is forwarded on your router to this static LAN IP address.

If still no go, try updating your video drivers.

chrisx03 · Post by **chrisx03** » Wed Oct 08, 2008 7:52 pm

my video drivers?? that sounds odd, but anyway everythgin seems to be in a+ condition referring to the settings but i am still missing somethign considering that when i try to do remote connecting just on the local network to the main computer its gives me that same error. all other computers i can do remote connections to through the local network. now form the main computer i can do remote connection TO other computers though.----
------ so basically yes i tried connecting internally on the network from another pc none of them can connect to it i get the error but the host pc can connect to any other pc on the network through RDC

Post by **YeOldeStonecat** » Thu Oct 09, 2008 8:52 am

One in a great while......when troubleshooting any remote control host issues.....after pulling what's left of ones hair out trying to figure out why it's not working....the video driver ends up being the culprit. It had been a couple of years since I ran across this issue up until last week in another networking forum...where updating the video driver fixed the problem.

chrisx03 · Post by **chrisx03** » Thu Oct 09, 2008 5:49 pm

wasn't the video drivers i shall try to start up my pc with the on board video and see if there is any difference. I have never been so stumped before, i don't want to reinstall windows!!!..
------
well now i get a different error

Post by **YeOldeStonecat** » Fri Oct 10, 2008 7:03 am

Can you test the computer and attempt to connect to it from another PC on the local network? Using the internal IP address...like 192.168.1.100?

Allowing remote desktop connections has been verified as turned on?
Any/all software firewalls on the host PC have exceptions to allow RDP traffic? Including the built in XP firewall if that's being used.

SG Broadband Community

Remote connection

Remote connection

Lol