📎 AI Summary:
The thread discusses a DNS and server login issue where a client machine's hostname and IP address seem to be mismatched or duplicated within the network. The original poster describes confusion over hostname resolutions and server connections, especially when RDP connections show unexpected hostnames. A respondent suggests common causes such as static IP or DNS configuration overlaps as potential reasons for the problem.

hairyprogrammer

New Member
Member details
Joined
May 7, 2020
Messages
1
Thread Author #1
I have a client machine on the network that seems to have the same DNS entry as a server?



When i go on to our certification authority server and listed on Server Manager...looking at our active rdp connections i can see the AD account name of a client having an issue that i want to help them with: abc123



We have 2 x RDS servers...so i look in here to see which RDS server the account is logged on to.



I then go to the RDS server in question...into Task Manager and look at the Users tab, locate the AD username and see what machine hostname they are connecting with....that's all fine until i RDP to the machine...and when i do so.....my laptop tries to connect to a server that has a completely different hostname

vm-sun123 when i use the hostname of abc123

if i do an nslookup on the abc123 it gives an IP address of whatever 192.168.1.200

When i nslookup 192.168.1.200 it gives me the hostname of the sever...



can anyone assist and she light, please?
 

Solution
A few common scenarios come to mind.

Either both machines have statically assigned IP addresses, someone added one or both DNS entries manually or one system (likely the server) is set with a static address which is also overlapping into a DHCP address scope

Neemobeer

Windows Forum Team
Staff member
Member details
Joined
Jul 4, 2015
Messages
8,995
A few common scenarios come to mind.

Either both machines have statically assigned IP addresses, someone added one or both DNS entries manually or one system (likely the server) is set with a static address which is also overlapping into a DHCP address scope
 

Solution