Host is wired to a router, gets a 192.168.2.2 address

My hostcomputer (XP) is wired with cable to a wireless
router, and gets a 192.168.2.2 address. I use a dynamic
dns service which gives the host a name like
johan.blahblah.com

From a client-laptop that is wireless and connected to
same router and has address 192.168.2.3 I can connect
with Remote Desktop when logging on to 192.168.2.2 but
not with johan.blahblah.com

And the same when trying over Internet, I can't connect
using johan.blahblah.com and of course not 192.168.2.2

I have enabled RD in host's firewall (xp's own)

I can ping johan.blahblah.com with success.


How can I enable access to johan.blahblah.com over
Internet??

The wireless router has address 192.168.2.1

First using the alias johan.blahblah.com from a PC on your LAN to access a PC on your LAN via your
router is not a valid test. So forget that. If you can connect over the LAN using the IP or by the
PCs local LAN name then your good to go as far as Remote Desktop being setup right.

The next problem is the router and the dynamic name service. If your positive you have TCP Port 3389
forwarded/opened in the router to the correct LAN IP of the PC your trying to control then its a
problem with the dynamic naming service.

One way to test the router is to do this telnet test using the IP of the router. You need to test
this from a remote location or dial into the internet using a laptop, etc.

http://support.microsoft.com/default...;en-us;Q187628

1. In your favorite browser, ie. Internet Explorer is mine, on the PC your trying to reach go to the
http://checkip.dyndns.org/ site and note the returned IP address.
2. Use the command...

telnet <IPAddress> 3389

where <IPAddress> is the IP returned in step 1. Troubleshoot according to the KB article...

To verify the correct alias to IP being mapped by the dynamic naming service do this...

1. In your favorite browser, ie. Internet Explorer is mine, go to the http://checkip.dyndns.org/
site and note the returned IP address.
2. Go to "Start -> Run" and type cmd at the command line. Next use the following command at the
prompt...

nslookup johan.blahblah.com

3. Verify the IP returned in step 1 is the same as the IP returned in step 2. If its not, then you
have a problem with the naming service.
--
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...

"Johan" <johan.m.eriksson@telia.com> wrote in message news:ee2b01c3f19c$833de650$a301280a@phx.gbl...

> My hostcomputer (XP) is wired with cable to a wireless
> router, and gets a 192.168.2.2 address. I use a dynamic
> dns service which gives the host a name like
> johan.blahblah.com
>
> From a client-laptop that is wireless and connected to
> same router and has address 192.168.2.3 I can connect
> with Remote Desktop when logging on to 192.168.2.2 but
> not with johan.blahblah.com
>
> And the same when trying over Internet, I can't connect
> using johan.blahblah.com and of course not 192.168.2.2
>
> I have enabled RD in host's firewall (xp's own)
>
> I can ping johan.blahblah.com with success.
>
>
> How can I enable access to johan.blahblah.com over
> Internet??
>
> The wireless router has address 192.168.2.1

Well, putting a PC in the DMZ is a big security risk particularly if your not running personal
firewall software on the machine.

What were the results of the testing?

--
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...

"Johan" <johan.m.eriksson@telia.com> wrote in message
news:5A8DAAED-BC77-464A-884A-78319C12BB60@microsoft.com...

> Thanks for your advice, but I managed after i wrote to fix this, please tell me if the solution

seems really okey:

>
> My router has a feature called Virtual Server Settings, where i configured
> DMZ = 192.168.2.2
>
> Internal IP Service port range
> 192.168.2.2 3389 to 3390
>
> Now it works to access johan.blahblah.com over Internet. Ain't this same as port forwarding?
> My friends says you must configure SSH to get this working over Internet and from our work, but it

works for me without SSH ??

> Or is SSH just to secure Remote Desktop, and something you strongly recommend me?
> Best regards Johan
>
>
> ----- Sooner Al wrote: -----
>
> First using the alias johan.blahblah.com from a PC on your LAN to access a PC on your LAN via

your

> router is not a valid test. So forget that. If you can connect over the LAN using the IP or

by the

> PCs local LAN name then your good to go as far as Remote Desktop being setup right.
>
> The next problem is the router and the dynamic name service. If your positive you have TCP

Port 3389

> forwarded/opened in the router to the correct LAN IP of the PC your trying to control then

its a

> problem with the dynamic naming service.
>
> One way to test the router is to do this telnet test using the IP of the router. You need to

test

> this from a remote location or dial into the internet using a laptop, etc.
>
> http://support.microsoft.com/default...;en-us;Q187628
>
> 1. In your favorite browser, ie. Internet Explorer is mine, on the PC your trying to reach go

to the

> http://checkip.dyndns.org/ site and note the returned IP address.
> 2. Use the command...
>
> telnet <IPAddress> 3389
>
> where <IPAddress> is the IP returned in step 1. Troubleshoot according to the KB article...
>
> To verify the correct alias to IP being mapped by the dynamic naming service do this...
>
> 1. In your favorite browser, ie. Internet Explorer is mine, go to the

http://checkip.dyndns.org/

> site and note the returned IP address.
> 2. Go to "Start -> Run" and type cmd at the command line. Next use the following command at

the

> prompt...
>
> nslookup johan.blahblah.com
>
> 3. Verify the IP returned in step 1 is the same as the IP returned in step 2. If its not,

then you

> have a problem with the naming service.
> --
> 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...
>
> "Johan" <johan.m.eriksson@telia.com> wrote in message

news:ee2b01c3f19c$833de650$a301280a@phx.gbl...

>
>