Server Moved To New Machine; Network DNS Errors
-
I am currently at work and we have our network of computers. We have a few servers running Windows Server 2003. One of them crapped out and someone simply hooked up a new system, transferred the old data and set the new system up with the same name on the network. This server also hosts an instance of MS SQL Server 2008 Express. The issue, however, is that all the computers in the network must now connect to the SQL Server using its IP Address, rather than the computer name. When I ping by IP it resolves the computer name correctly. However, when I ping the computer name it gives me the server's OLD IP Address. How can we correct this?
djj55: Nice but may have a permission problem Pete O'Hanlon: He has my permission to run it.
-
I am currently at work and we have our network of computers. We have a few servers running Windows Server 2003. One of them crapped out and someone simply hooked up a new system, transferred the old data and set the new system up with the same name on the network. This server also hosts an instance of MS SQL Server 2008 Express. The issue, however, is that all the computers in the network must now connect to the SQL Server using its IP Address, rather than the computer name. When I ping by IP it resolves the computer name correctly. However, when I ping the computer name it gives me the server's OLD IP Address. How can we correct this?
djj55: Nice but may have a permission problem Pete O'Hanlon: He has my permission to run it.
-
I am currently at work and we have our network of computers. We have a few servers running Windows Server 2003. One of them crapped out and someone simply hooked up a new system, transferred the old data and set the new system up with the same name on the network. This server also hosts an instance of MS SQL Server 2008 Express. The issue, however, is that all the computers in the network must now connect to the SQL Server using its IP Address, rather than the computer name. When I ping by IP it resolves the computer name correctly. However, when I ping the computer name it gives me the server's OLD IP Address. How can we correct this?
djj55: Nice but may have a permission problem Pete O'Hanlon: He has my permission to run it.
Few steps to find a resolution: - Go to your DNS or WINS server and flush the name/IP of the old machine from there. - Its also possible to store it as a static IP from there (in name resolution server) so make sure its not stored as a static address. - Finally, make sure none of your computers have an entry in the hosts file directing them to the old IP address. Good luck! :)
-
Few steps to find a resolution: - Go to your DNS or WINS server and flush the name/IP of the old machine from there. - Its also possible to store it as a static IP from there (in name resolution server) so make sure its not stored as a static address. - Finally, make sure none of your computers have an entry in the hosts file directing them to the old IP address. Good luck! :)
I did check the hosts file on the affected systems, none of which contained any entries in them. We also do not have actual access to our DNS servers. That is only accessible by corporate IT. It's no big deal though. I just changed the software to use the IP address of the server rather than the computer name. And I had to manually update them (only the one time; my application updates itself when it has a valid server path). So the worst part of it is over. :-P Thank you for the responses though.
djj55: Nice but may have a permission problem Pete O'Hanlon: He has my permission to run it.
-
I did check the hosts file on the affected systems, none of which contained any entries in them. We also do not have actual access to our DNS servers. That is only accessible by corporate IT. It's no big deal though. I just changed the software to use the IP address of the server rather than the computer name. And I had to manually update them (only the one time; my application updates itself when it has a valid server path). So the worst part of it is over. :-P Thank you for the responses though.
djj55: Nice but may have a permission problem Pete O'Hanlon: He has my permission to run it.
As long as it works! :)