Solved

Why does the client machine still point to the old computer name?

Posted on 2008-10-15
13
385 Views
Last Modified: 2012-08-14
I had two users that switched computers.  To reflect the computer name with thier job role, I renamed the computers.  They are on the same Windows 2003 server domain.  I renamed ACCOUNTING to SECRETARY and then renamed SECRETARY to ACCOUNTING.  I did this first by removing both PC's from the domain adding them to a workgroup.  I removed the computers in Active Directory and then renamed the PC's then added back onto the domain.  Now if I try using RDP or ping SECRETARY it is pinging the ACCOUNTING computer which is the old SECRETARY computer.  Same thing with RDP, it connects to the old computer.  Is this an issue with a GUID?  Any help is much appreciated.  Thank you.
0
Comment
Question by:TeddyZ83
  • 6
  • 3
  • 3
  • +1
13 Comments
 
LVL 14

Expert Comment

by:Kutyi
ID: 22727408
Have you flushed your DNS on the PC you are RDPing from: ipconfig /flushdns
0
 

Author Comment

by:TeddyZ83
ID: 22727460
Yes, I did do ipconfig /flushdns
0
 
LVL 14

Accepted Solution

by:
Kutyi earned 250 total points
ID: 22727481
In your server DNS console does it show the correct IPs?  If not delete the records and release and renew the IPs on the boxes to update DNS.
0
 
LVL 42

Expert Comment

by:paulsolov
ID: 22727537
check thee arp cache, dns cache on the dns server and wins (if you're using it)
0
 

Author Comment

by:TeddyZ83
ID: 22727557
If I look under the forward lookup zones in DNS, it shows both ACCOUNTING and SECRETARY having the same IP address.  Should I delete the SECRETARY or ACCOUNTING?  Or both?  
0
 
LVL 42

Assisted Solution

by:paulsolov
paulsolov earned 250 total points
ID: 22727582
You should delete the one that doesn't match.

Check on both systems to see which ip address each machine is using and make sure that they're not using the same one.  Once you know which machine should ahve the correct ip address you can delete the entry that does not correspond.

You can also delete both and do a  "ipconfig /registerdns" from the workstation to register correctly
0
Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

 

Author Comment

by:TeddyZ83
ID: 22727635
I deleted the problem one: SECRETARY and then because I'm working remotely, I went to both machines and performed a repair on the local adapter.  This cleared the DNS cache and now everything is working well!  Thanks a lot for your help guys!  Very much appreciated.
0
 

Author Comment

by:TeddyZ83
ID: 22727711
I spoke too soon.  I rebooted the machine that I removed from DNS on the server and after logging back in, I'm back to the same issue.  Maybe I need to clear the ARP cache on the client?
0
 
LVL 42

Expert Comment

by:paulsolov
ID: 22727718
do the two systems have the same ip address or different ip addresses?
0
 

Author Comment

by:TeddyZ83
ID: 22727754
I did ipconfig /registerdns from the problematic computer.  Now they are showing up as different addresses fine.  RDP now works by it's computer name which before both connected to the same machine.  So that's fine but I noticed if I ping SECRETARY I get "request timed out."  It is looking at the correct IP address.  But if I ping SECRETARY from the actual SECRETARY PC, it responds fine.  
0
 
LVL 14

Expert Comment

by:Kutyi
ID: 22727766
That could be a firewall setting on the SECRETARY PC.  So long as DNS resolves correctly your good, or do you have to ping?
0
 

Author Comment

by:TeddyZ83
ID: 22727776
I don't have to ping but I just wanted to make sure everything is up to par.  I can live without pinging the machine just as long as no conflicts between the two machines on the network.  Thanks.
0
 
LVL 38

Expert Comment

by:ChiefIT
ID: 22727866
Sounds like WINS/Netbios or DNS records on the DC.

Have you flushed your WINS cache records, (Also known as your Netbios Cache)?:

At the command prompt type:
NBTstat -rr

Remove host A records and reregister them in DNS?

Remove WINS records and reregister them in WINS, if you use a WINS server?

It appears like you already flushed the DNS cache.
IPconfig /flushDNS
0

Featured Post

New My Cloud Pro Series - organize everything!

With space to keep virtually everything, the My Cloud Pro Series offers your team the network storage to edit, save and share production files from anywhere with an internet connection. Compatible with both Mac and PC, you're able to protect your content regardless of OS.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A common practice in small networks is making file sharing easy which works extremely well when intra-network security is not an issue. In essence, everyone, that is "Everyone", is given access to all of the shared files - often the entire C: drive …
Learn about cloud computing and its benefits for small business owners.
Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…
In this video I am going to show you how to back up and restore Office 365 mailboxes using CodeTwo Backup for Office 365. Learn more about the tool used in this video here: http://www.codetwo.com/backup-for-office-365/ (http://www.codetwo.com/ba…

910 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now