Remote Desktop Issues

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 ? I have changed the port numbers, but I dont
see why this should matter.

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

TDM <(E-Mail Removed)> 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.....

When you changed the port on the Windows box, did you update the firewall
rules? Maybe your communication with the server is being blocked @ the
perimeter. Try switching the port back to the default. You can do so through
the use of PSEXEC and the reg command. Try googling "remote registry change
psexec" .

Thanks,

Richard
"TDM" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> 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 ? I have changed the port numbers, but I dont
> see why this should matter.
>
> 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
>

"Lanwench [MVP - Exchange]"
<(E-Mail Removed) hoo.com> wrote in message
news:(E-Mail Removed)...
> TDM <(E-Mail Removed)> 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. 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

"Richard Raseley" <(E-Mail Removed)> wrote in message
news:74E6B22D-2233-4C13-89FE-(E-Mail Removed)...
> When you changed the port on the Windows box, did you update the firewall
> rules? Maybe your communication with the server is being blocked @ the
> perimeter. Try switching the port back to the default. You can do so
> through the use of PSEXEC and the reg command. Try googling "remote
> registry change psexec" .
>
> Thanks,
>
> Richard
> "TDM" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>
>> 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 ? I have changed the port numbers, but I dont
>> see why this should matter.
>>
>> 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
>>
>

The Firewall is turned off on the server for testing, and with a NAT router
in front of the server, it would be just another obstacle in the way.

And just in case anyone else asks, the server is set up for DDNS with
DnsMadeEasy.com, hence the reason that nslookup works. I guess
common sense tells me that if the hostname resolves via DNS(nslookup),
then remote desktop should also be able to connect via the hostname.

Any other ideas ? Is anyone else seeing this behavior ?

Thanks for the reply.

TDM

TDM <(E-Mail Removed)> wrote:
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) hoo.com> wrote in
> message news:(E-Mail Removed)...
>> TDM <(E-Mail Removed)> 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

"Lanwench [MVP - Exchange]"
<(E-Mail Removed) hoo.com> wrote in message
news:%23W3Wd5$(E-Mail Removed)...
> TDM <(E-Mail Removed)> wrote:
>> "Lanwench [MVP - Exchange]"
>> <(E-Mail Removed) hoo.com> wrote in
>> message news:(E-Mail Removed)...
>>> TDM <(E-Mail Removed)> 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.


TDM

TDM <(E-Mail Removed)> wrote:
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) hoo.com> wrote in
> message news:%23W3Wd5$(E-Mail Removed)...
>> TDM <(E-Mail Removed)> wrote:
>>> "Lanwench [MVP - Exchange]"
>>> <(E-Mail Removed) hoo.com> wrote in
>>> message news:(E-Mail Removed)...
>>>> TDM <(E-Mail Removed)> 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

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

If you have an entry for the target host in the hosts file then ping would
return a different IP than nslookup. This is just one example. You have to
use all the tools and compare results to see what is really happening.

--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca/phpBB2/