Re: Remote Desktop Issues

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

TDM <rpuffd@xxxxxxxxx> wrote:
"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%23W3Wd5$PIHA.4276@xxxxxxxxxxxxxxxxxxxxxxx
TDM <rpuffd@xxxxxxxxx> wrote:
"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:ODcsPY0PIHA.4656@xxxxxxxxxxxxxxxxxxxxxxx
TDM <rpuffd@xxxxxxxxx> wrote:
Hello all,

First, my apologies if this is the wrong NG.

I am having some issues with Remote Dektop connections.
I am trying to connect to a remote server over the internet.
I have set up Dynamic DNS to the Windows Server 2003.
I can resolve the Hostname just fine via an nslookup. However,
when I try to connect to the remote server using the Hostaname,
it fails. If I use the resolved IP Address, I can connect just
fine. I have tried connecting with both XP Pro and Vista Ultimate,
same issue. Are there any issues with connecting via the hostname
versus the IP ?

No, shouldn't be.

I have changed the port numbers, but I dont
see why this should matter.

Nope, shouldn't matter at all.

This does not work :

servername.domain.com:12345

This does work :

xxx.xxx.xxx.xxx:12345

I did some googlin, but found nothing useful.

TIA

TDM

Ping servername.domain.com and ensure you're getting the same IP
address you think you ought to. NSlookup isn't needed - a simple
ping will tell you what IP address you're currently using for that
name. You might double check with your dynamic DNS update
client.....

Ping is not an option, there is a router in front of the server with
Echo turned off, as it should be.

That's a good config, but isn't relevant here. If you ping your
dynamic DNS hostname, you should get the IP
address returned - whether it replies or not.

Nslookup tells me that DNS resolves
the name so I naturally figured that Remote Desktop would as well.
Any other ideas ?

Thanks for the reply.

TDM





Point taken, I guess I just prefer nslookup. We all have our bad
habits.

But nslookup != ping .

....and ping is the fastest way to find out whether your hostname matches the
IP you wish, or vice versa.

Since you've established that you can connect using the IP address, you just
need to verify that your dynamic DNS hostname is being properly updated.
There's nothing else to it....nothing in your router or computer would be
preventing it (nor could they).





TDM



.

Relevant Pages

  • Re: Remote Desktop Issues
    ... I am trying to connect to a remote server over the internet. ... I have tried connecting with both XP Pro and Vista Ultimate, ... Ping servername.domain.com and ensure you're getting the same IP ...
    (microsoft.public.windows.server.networking)
  • Re: Remote Desktop Issues
    ... I am trying to connect to a remote server over the internet. ... I have tried connecting with both XP Pro and Vista Ultimate, ... Ping servername.domain.com and ensure you're getting the same IP address you ...
    (microsoft.public.windows.server.networking)
  • Cant connect from one location
    ... Any computer at one remote location can no longer connect to the Windows ... we have a netscreen box as a firewall and provides the tunnel. ... They can ping the TS ... if it connecting for a moment but drops out with, ...
    (microsoft.public.windows.terminal_services)
  • Re: when connecting to a pc through Remote Desktop Connection (locally or remotely) local drive is n
    ... Click Services tab and select Hide All Microsoft Services and Disable ... 40932648-when connecting to a pc through Remote Desktop Connection (locally ... <Subject: Re: when connecting to a pc through Remote Desktop Connection ... I can see pc x's local drives on pc y. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop Service not behaving properly but no error
    ... Even after a reboot of the REMOTE computer, I try to connect to it, ... network connectivity problems. ... I've tried entering my password before connecting and waiting to enter ... It may have something to do with the screensaver timeout maybe because ...
    (microsoft.public.windowsxp.work_remotely)