Results 1 to 4 of 4

Thread: Workstation resolving Server name to wrong IP

  1. #1
    Join Date
    Nov 2009

    Workstation resolving Server name to wrong IP

    I have a windows server 2003, with xp clients, that runs DNS...
    I changed the nic and the IP on the server and now the client wont resolve the correct IP when pinging...
    I have tried (ipconfig /flushdns), (arp -a) shows the correct mac for server1's new nic, (nbtstat -R)...
    When I ping the servers FQDN it resolves correctly...


    server1 IP =
    ping server1 (times out) looking for
    ping (reply from)

    I have a second server (server2) that I have no problems with, which was implemented after this problem...the DNS suffix in the client advanced tcp/ip settings are configured correclty

    what am I missing?

  2. #2
    Join Date
    May 2008

    Re: Workstation resolving Server name to wrong IP

    Just open DNS on the server to see the next and previous records. After getting all the records, you need to delete the incorrect ones, if you want your server should have the same IP address all the time, then you will need to assign it an IP outside the DHCP scope or just give a reservation in the scope itself.
    Last edited by Raine; 25-11-2009 at 01:47 AM.

  3. #3
    Join Date
    Dec 2008

    Re: Workstation resolving Server name to wrong IP

    I would think it is a DNS issue. Check through your (A)Host records for all incidents of that domain name and then check the IP within in it. If it was a DC before the IP address changed, it is borked. You can't just change the IP address of a DC. DC's have service records and what not in DNS that need to be changed.

  4. #4
    Join Date
    Apr 2008

    Re: Workstation resolving Server name to wrong IP

    Have you find the offending systems the system 1 and system 2. There may be some list in it. Is the current IPs matching with the old one. If their is any problem in your system have you command ipconfig / registerdns.
    If you are not finding any system records after checking the DNS event log from the server their may be a bigger problems then you have to have a couple of workstation. Their may be a host records in your systems. Their must be a ip addressing scheme in the look-up zone of your system and their must be a bunch of ptr records. I think you must tried the re-loader DNS on the server. You had not then do it. This is the best method to deal with the errors of the server as the 4004 and 4005s.

Similar Threads

  1. Windows server 2003 DNS not resolving
    By YeNNa!R@$K^LA in forum Windows Server Help
    Replies: 7
    Last Post: 15-02-2012, 01:51 AM
  2. How to use Windows Server as Workstation
    By RedZot in forum Guides & Tutorials
    Replies: 2
    Last Post: 15-06-2011, 07:50 AM
  3. Convert Windows Server 2003 To WorkStation
    By Andrew in forum Guides & Tutorials
    Replies: 3
    Last Post: 09-11-2010, 02:22 PM
  4. Replies: 3
    Last Post: 02-11-2010, 10:36 AM
  5. Using VMware server 1.0 on Workstation 5.5
    By fragranz in forum Networking & Security
    Replies: 5
    Last Post: 27-04-2010, 10:12 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts