why does Remote Desktop Connection work with an IP address and not the name of the PC?

  • Thread starter Thread starter Kelvin
  • Start date Start date
K

Kelvin

I have no problem connecting to a PC on my network by its IP address, but if
I try and use its name, the connection fails.
The firewall is off on the PC I'm trying to connect to.
It's a member of the domain.

I use Remote Desktop Connection to connect to numerous other PC's on my
network and have no problem.
I've just rebuilt this PC so it shouldn't have any odd software...
I have installed MS Office and XP SP3.
I have Office on other PCs...
Are there issues with SP3 that might cause this?

Any help would be appreciated!

Kelvin
 
Kelvin said:
I have no problem connecting to a PC on my network by its IP address, but
if I try and use its name, the connection fails.
The firewall is off on the PC I'm trying to connect to.
It's a member of the domain.

I use Remote Desktop Connection to connect to numerous other PC's on my
network and have no problem.
I've just rebuilt this PC so it shouldn't have any odd software...
I have installed MS Office and XP SP3.
I have Office on other PCs...
Are there issues with SP3 that might cause this?

Any help would be appreciated!

Kelvin
Click to expand...

Do you get replies if you ping it by name?

Is this on a workgroup?
 
When I ping the workstation by name it looks like this:
Pinging partssales2.cit.local [198.134.209.170] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 198.134.209.170:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

This part looks odd to me "partssales2.cit.local [198.134.209.170]"
I looked on my DC at the DHCP Address Leases and there is no
[198.134.209.170] listed there.
When I ping [198.134.209.170] I get this,

Pinging 198.134.209.170 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 198.134.209.170:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Any idea what the [198.134.209.170] is going in the mix?

Thanks for your time

Kelvin
 
Kelvin said:
When I ping the workstation by name it looks like this:
Pinging partssales2.cit.local [198.134.209.170] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 198.134.209.170:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

This part looks odd to me "partssales2.cit.local [198.134.209.170]"
I looked on my DC at the DHCP Address Leases and there is no
[198.134.209.170] listed there.
When I ping [198.134.209.170] I get this,

Pinging 198.134.209.170 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 198.134.209.170:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Any idea what the [198.134.209.170] is going in the mix?

Thanks for your time

Kelvin


Olórin said:
Then the problem isn't with RDP per se, but name resolution on your
network.

<still wonders if this is a workgroup set-up...>
Click to expand...
Click to expand...
So, you can't ping the machine by IP but you can RDP to it by IP? Odd.

Obvious question is: on this remote machine, partssales2 or whatever, do an
ipconfig and see what its IP address IS - as opposed to what your machine
thinks it is. Maybe an "ipconfig /flushdns" on your machine will help it
pick up a change in the remote one's address.
 
Back
Top