Remote desktop & Netgear router

[Leslie]

I am having difficulty connecting to my computer that has
access to the internet through a netgear router
(WGR614). I believe I have opened the port that allows
remote desktop to work. I also believe my trouble is
router related because I am able to connect to my
computer with the remote desktop feature when both
computers are inside the router

 

[Sooner Al]

You need to forward/open TCP Port 3389 through the router to the private LAN IP of the PC you want
to connect to. Call, from a remote location, using the public IP of the router.

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

 

[Leslie]

I logged into the router and went to the advanced tab and
clicked on the Port Forwarding tab. In there I clicked
on add custom service. There it asked me for a service
name, I left that empty because the choices available
weren't applicable to Remote Desktop. The next line
asked for the service type, I have tried this setting on
all 3 choices, which are TCP/UDP TCP UDP. The next
line asked for the Start Port, I set this to 3389. The
next line asked for the Ending Port, I set this to 3389.
The next line asked for Server IP Address, in this I put
the router assigned address for this particular
computer. I then applied this.

Is there something else I should be doing?

-----Original Message-----
You need to forward/open TCP Port 3389 through the

router to the private LAN IP of the PC you want

to connect to. Call, from a remote location, using the public IP of the router.

group for the mutual benefit of all of us...

 

[Sooner Al]

I don't have that particular router, but it sounds OK. You might want to check the users manual or
the Netgear support site for further help setting up that router for port forwarding.

How are you testing this? From a remote PC or via a dialup ISP? You can *NOT* reliably test from a
PC on your local LAN by calling the public IP of the router.

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

 

[Sooner Al]

From this support page at Netgear you should setup a custom port for TCP Port 3389. Call the service
"Remote Desktop" or "RemoteDesktop" or something similar for ease of troubleshooting...

http://kbserver.netgear.com/kb_web_files/N101145.asp

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

 

[Guest]

I've tried it 2 ways. I have used a dialup connection
and I have also tried it on my LAN connection.
I edited my connection and called it RemoteDesktop. I
have been to the Netgear web site but I really couldn't
find anything there that helped me, hence the reason I
turned to this form hopping to find a fix for my problem.

-----Original Message-----
From this support page at Netgear you should setup a

custom port for TCP Port 3389. Call the service

"Remote Desktop" or "RemoteDesktop" or something similar for ease of troubleshooting...

http://kbserver.netgear.com/kb_web_files/N101145.asp

group for the mutual benefit of all of us...

 

[Sooner Al]

Well, if you can connect to the PC from another PC using the "private LAN IP address" over your
local LAN then Remote Desktop is obviously setup right and working.

The issue then is the port forwarding on the router. You can test using this telnet test to see if
you can pinpoint the problem... Again, this test must be done from a remote PC, ie. outside your
local LAN...

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q187628

If you think you have a problem with the Netgear router and its specific configuration for port
forwarding TCP Port 3389, then I suggest you search or post to the DSL Reports Netgear forums for
help with Netgear specific issues...

http://www.dslreports.com/forum/netgear

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

 

[Leslie]

I know this may be a silly question, but how do I find
out the host name of my Terminal Server? In the web
address that you had sent for the telnet test it gave a
command line and in that line you are supposed to put the
host name as I understand it.

-----Original Message-----
Well, if you can connect to the PC from another PC using

the "private LAN IP address" over your

local LAN then Remote Desktop is obviously setup right and working.

The issue then is the port forwarding on the router. You

can test using this telnet test to see if

you can pinpoint the problem... Again, this test must be

done from a remote PC, ie. outside your

local LAN...

http://support.microsoft.com/default.aspx?scid=kb;en- us;Q187628

If you think you have a problem with the Netgear router

and its specific configuration for port

forwarding TCP Port 3389, then I suggest you search or

post to the DSL Reports Netgear forums for

help with Netgear specific issues...

http://www.dslreports.com/forum/netgear

group for the mutual benefit of all of us...

 

[Bill Sanderson]

Unless you are on the same LAN as the host you are trying to reach, this is
usually the IP address of the machine. In your case it would be the IP
address of the WAN port of the Netgear router.

 

[Sooner Al]

And to add, you can get that quite easily by going to either of these sites from a PC on the LAN
behind the router...

http://checkip.dyndns.org/

....or...

http://www.whatismyip.com/

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...