Solved

Computer name returning a different address then it is assigned.

Hello,

I have 2 servers. 1 is a terminal server windows 2003 sb terminal server.(working fine :) ) and the other is server 2003 small business DC configured with dhcp, dns, SQL, & wins.

Last week one of the network programs that is located on the DC started refusing connections.

So doing some trouble shooting I noticed that when I ping the server name I get a local address of *.*.*.42 when the address the machine is assigned is *.*.*.5. When I do an Ipconfig /all on the DC it only shows the *.*.*.5 number. I look in DHCP and *.*.*.5 is reserved for the DC Computer. And the *.*.*.42 isn't even in the address leases. I have also looked through the DNS settings and see no alias with the .42 number. And the number does not show up in the reverse lookup zone either.

Not sure where else to look. Any help would be appreciated.
5 answers Last reply Best Answer
More about computer returning address assigned
  1. Best answer
    WINS, not DNS is the issue

    http://en.wikipedia.org/wiki/Windows_Internet_Name_Service

    "Network address mappings are dynamically updated so that when a client needs to contact another computer on the network it can get its up-to-date IP address which may be issued by a DHCP server. Aside from this the WINS functionality provides a way of keeping the client names unique on the network."
  2. Thank you!

    I see, there were 2 wins address associations to that computer name. I deleted the incorrect one and all seems to be working fine. Any reason why that would have happened?
  3. WINS does not always work well in finding and cleaning up new and old data. It's not often when it does that, but it does happen. As to why this happens, you may want to poke around the Microsoft msdn site for any articles about it, last time I dealt with working on a live DNS and WINS setup was around the year 2000, I'm a bit rusty in my knowledge :-)
  4. hang-the-9 said:
    WINS does not always work well in finding and cleaning up new and old data. It's not often when it does that, but it does happen. As to why this happens, you may want to poke around the Microsoft msdn site for any articles about it, last time I dealt with working on a live DNS and WINS setup was around the year 2000, I'm a bit rusty in my knowledge :-)


    Well, thank you for the info. Much appreciated!
  5. Best answer selected by mledezma.
Ask a new question

Read More

LAN Windows Server 2003 Terminal Server Servers Networking