Remote Access - Wrong Computer Name Displaying

I'm not sure how to explain this but I will try.   I am at home connected to my VPN.  I had our staff leave their computers on when they left at end of day so that I could remote access into them to install a screensaver on each computer.  When using Remote Desktop, I am typing the computer name to access the computer.  I have a seating map with the computer names on them.  I recently re-imaged all of these computer and named them according to this seating map so I know they are named accordingly.  

When I log into the computer and go to look at the name of the computer it is completely different.  Some of these computers that i am actually logging into are somewhere else in the building....and have not been re-imaged.  That is how I know it is not accessing the proper computer.

Does this make sense to anyone?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Well I can come up with a couple of explainations.

1> The names are already used. To verify this open a command prompt and type nslookup <computer name>. this will tell you the ip addresses of all the computers with this name. To solve this rename the computer.

2>DNS list is wrong. To solve this go to command prompt and type ipconfig /flushdns and try again.

3>IP conflict. if your using DHCP this should not be a problem.

Also a better way to deal with these type of remote installations is to statically assign IP addresses, then use the ip address to log onto that computer. This does not require DNS resolution and therefore is more acurate.

Good Luck with your problem

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jbartleydccAuthor Commented:
I did a NSLOOKUP on the computer name and got 1 IP address....I go into that address and that computer is called something completely different.  Then I decided to RDP into the server and NSLOOKUP the same computer name and got a different IP address.  When I RDP to that IP it is the right computer.  Weird.

I then did the ipconfig /flushdns on both my computer AND the server that I was logged into and both are still bringing up the same addresses for that computer name (different ips)

We are running DHCP so it is probably not an IP conflict I'm guessing.

Thanks for your help!  I can now at least check the ips both ways and find the right computer in a round-about way!  Thanks.  I definately have something to look into when I go back to work on Monday.

This also sounds like a DNS issue to me. I would look at the DNS records on your server to see what it shows in comparison to the list you have.
Depending on which server and client OSes you are using, you can also look into your DHCPsettings. In the area where DNS is configured, there should be an option to discard the records once the lease is up.
In the computers in question, also have a look at the TCP/IP properties of the network adapter. Look under advanced, and try checking the check box next to Register this connections addresses in DNS. Normally it is checked by default. Sometimes it isn't for whatever reason.
If all else fails, you can try deleting a DNS record for the PC in question, doing an ipconfig release and renew, and then trying to ping it by name to see what you get.
Let us know...
jbartleydccAuthor Commented:
I'll definably look into that when I get to work this week.  I also realized that we have 2 domains setup at work (it was set up very strange before I came into the department).  When I log into the VPN I believe I am somehow not connecting to the domain that I thought I was.  If I refer to them as domain 1 and domain 2, when I login to my laptop from home and connect to the VPN I think I am connecting to domain 1 but the computers I was trying to do an NSLOOKUP on and trying to RDP to are on domain 2.  When I did a RDP to the server which is on domain 2 I was of course getting the correct IP address when doing NSLOOKUP for the same computer.  Once I took THAT IP address I was able to RDP into the correct computer from my laptop (connected to domain 1 I think).

I have no idea if what I typed will make sense to you or not but I tried my best to explain how I understand it.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.