We are no longer able to connect to our SQL Server 2000 database via ODBC (or OLEDB) from any computer OUTSIDE the server's subnet! Weird.
Here's what happened: We replaced our production NT4/SQL Server 6.5 machine (finally) with a W2K/SQL 2000 machine. They were both in the DOMAIN named "Warehouse", the NT4 machine being a BDC and the Win2000 machine an Active Directory Domain controller.
Basically, we swapped IP addresses between the two machines. My suspicion is that, because we cannot (to our knowledge) change the machine's network name of the Active Directory Domain controller, SQL server is running the old machine's name. This table might help:
So the network name (and therefore SQL Server service) is still named "ken", but the IP address has changed. The main DNS server (external to our Win2k domain) still allows connections to "wh2.company.com" - that was the whole point of simply switching the IP addresses.
We are attempting to connect via ODBC using TCP/IP, and have tried both IP Address and domain names. Nothing works unless the machine is IN the 123.456.123.* subnet! Doesn't even have to be IN the Active Directory Domain. Just IN the subnet. We've also tried Named Pipes just to see if that works, but no-can-do.
Any suggestions? Anyone seen this type of behavior before?
Can we "switch" the network and/or SQL Server service names on a live production box? Whenever we go into My Computer, Properties, Network Identification tab, it says "The identification of the computer cannot be changed because: The computer is a domain controller". I'm also under the assumption (perhaps incorrectly) that SQL Server automatically assumes the name of the computer on the network. At least it did when we installed it. So to change its name, we'd have to change the network name of the computer?
I'd appreciate any info/help on this.
Thanks!
Marie
Here's what happened: We replaced our production NT4/SQL Server 6.5 machine (finally) with a W2K/SQL 2000 machine. They were both in the DOMAIN named "Warehouse", the NT4 machine being a BDC and the Win2000 machine an Active Directory Domain controller.
Basically, we swapped IP addresses between the two machines. My suspicion is that, because we cannot (to our knowledge) change the machine's network name of the Active Directory Domain controller, SQL server is running the old machine's name. This table might help:
Code:
BEFORE THE SWITCH:
Network Name IP Address SQL Service Name
------------ ------------- ----------------
Old machine: wh2 123.456.123.1 wh2
New machine: ken 123.456.123.5 ken
AFTER THE SWITCH:
Network Name IP Address SQL Service Name
------------ ------------- ----------------
Old machine: wh2 (NOW OFFLINE) n/a
New machine: ken 123.456.123.1 ken
We are attempting to connect via ODBC using TCP/IP, and have tried both IP Address and domain names. Nothing works unless the machine is IN the 123.456.123.* subnet! Doesn't even have to be IN the Active Directory Domain. Just IN the subnet. We've also tried Named Pipes just to see if that works, but no-can-do.
Any suggestions? Anyone seen this type of behavior before?
Can we "switch" the network and/or SQL Server service names on a live production box? Whenever we go into My Computer, Properties, Network Identification tab, it says "The identification of the computer cannot be changed because: The computer is a domain controller". I'm also under the assumption (perhaps incorrectly) that SQL Server automatically assumes the name of the computer on the network. At least it did when we installed it. So to change its name, we'd have to change the network name of the computer?
I'd appreciate any info/help on this.
Thanks!
Marie