odlaw_J5
asked on
SQL 2005 fails after a LAN IP change
Hello Experts,
Windows Server 2003 with SQL 2005 SP1 installed and running in a single server enviroment.
Was working absolutely fine until I changed the LAN IP in network properties. Gateway and DNS also changed to match the new range.
Now I am seeing the following error:
Failed with the error: SQL Exception Error: .Net SqlClient Data Provider - An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Am I missing something? Is there more to just changing the network properties?
ANy help at all greatfully accepted.
Windows Server 2003 with SQL 2005 SP1 installed and running in a single server enviroment.
Was working absolutely fine until I changed the LAN IP in network properties. Gateway and DNS also changed to match the new range.
Now I am seeing the following error:
Failed with the error: SQL Exception Error: .Net SqlClient Data Provider - An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Am I missing something? Is there more to just changing the network properties?
ANy help at all greatfully accepted.
ASKER
Hi Kevin,
yes I checked that and altered to the correct address, tried reboot as well
Jake
yes I checked that and altered to the correct address, tried reboot as well
Jake
Where are you seeing the error? Wherever it is, try to see if you can ping the SQL Server by name, noting the IP address it resolves to. It is possible the DNS A record is pointing to the old address.
ASKER
Ok I thought that maybe this was going to be a simple setting I'd missed but it maybe more. Please let me fill in the blanks as best I can.
We have a server (LIVE ORIG.) that was setup by another individual and we do not have any instructions to set up this server. Another server (LIVE NEW) is now required to be setup indentically except for the IP addresses. All the hardware is also indentical.
So this is my 'rough' procedure so far to bring LIVE NEW to be as LIVE ORIG.
1) Setup router with the same LAN IP range as the LIVE ORIG. With internet access but completely disconnected from any other LAN.
2) Installed windows server 2003, SQL 2005 and installed windows updates.
3) Restore a series of tape backups. System State and full restore of Hard drives inc C:
4) using MS SQL Studio retore latest database.
NOTE: before I go on I will mention a 3rd party service working in the background. This service connects to an external email exchange account, strips the attachment and then applies it to the SQL database. This service also logs what it is doing and it is this log where I have seen the error mentioned earlier.
NOTE 2: at this point it is also worth mentioning that the LIVE NEW is now virtually identical to the LIVE ORIG. even using same LAN IP range.
5) performing a test proves successful and all is working fine
Making network changes.
1) Change the router LAN settings to the new IP range.
2) Change IP range on LIVE NEW and re-booted and re-connected everything.
3) Point the config.xml file for the 3rd party service at the new IP
4) test fails
Changes and settings I have checked/changed so far:
1) Your suggestion Kevin in your first post has been rectified.
2) DNS A record of the new IP exists and I have entered DNS forwarders to match the new network and ISP.
As you can probably guess the error is still occurring.
I hope this helps and I hope I've provided enough information but please let me know if you need more,
many thanks
Jake
We have a server (LIVE ORIG.) that was setup by another individual and we do not have any instructions to set up this server. Another server (LIVE NEW) is now required to be setup indentically except for the IP addresses. All the hardware is also indentical.
So this is my 'rough' procedure so far to bring LIVE NEW to be as LIVE ORIG.
1) Setup router with the same LAN IP range as the LIVE ORIG. With internet access but completely disconnected from any other LAN.
2) Installed windows server 2003, SQL 2005 and installed windows updates.
3) Restore a series of tape backups. System State and full restore of Hard drives inc C:
4) using MS SQL Studio retore latest database.
NOTE: before I go on I will mention a 3rd party service working in the background. This service connects to an external email exchange account, strips the attachment and then applies it to the SQL database. This service also logs what it is doing and it is this log where I have seen the error mentioned earlier.
NOTE 2: at this point it is also worth mentioning that the LIVE NEW is now virtually identical to the LIVE ORIG. even using same LAN IP range.
5) performing a test proves successful and all is working fine
Making network changes.
1) Change the router LAN settings to the new IP range.
2) Change IP range on LIVE NEW and re-booted and re-connected everything.
3) Point the config.xml file for the 3rd party service at the new IP
4) test fails
Changes and settings I have checked/changed so far:
1) Your suggestion Kevin in your first post has been rectified.
2) DNS A record of the new IP exists and I have entered DNS forwarders to match the new network and ISP.
As you can probably guess the error is still occurring.
I hope this helps and I hope I've provided enough information but please let me know if you need more,
many thanks
Jake
ASKER
I understand I have a 3rd party service to investigate but I would have expected changing an IP range of a server to be fairly straight forward.
question ? forgetting the 3rd party service:
If I wanted to change the IP range in a single server enviroment with SQL 2005 installed would I just normally alter the TCP/IP settings for the NIC and the SQL network TCP/IP protocols. Should that work ?
question ? forgetting the 3rd party service:
If I wanted to change the IP range in a single server enviroment with SQL 2005 installed would I just normally alter the TCP/IP settings for the NIC and the SQL network TCP/IP protocols. Should that work ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks,
I have made some progress I'd somehow managed to edit the wrong *.config.xml file related to the 3rd party service I mentioned, after edited the correct one the error message has gone. Thank the lord, I was pulling my hair out.
As is the way with computers though I remove one issue and find another. But that's another story and, I think, unrelated to SQL.
You answered what I was presuming anyway and that it should not be rocket science to change an Ip range on a single server with SQL.
Thanks again for your input, the one thing I do find useful with this site is just being able to discuss the issue. That can help a lot.
I have made some progress I'd somehow managed to edit the wrong *.config.xml file related to the 3rd party service I mentioned, after edited the correct one the error message has gone. Thank the lord, I was pulling my hair out.
As is the way with computers though I remove one issue and find another. But that's another story and, I think, unrelated to SQL.
You answered what I was presuming anyway and that it should not be rocket science to change an Ip range on a single server with SQL.
Thanks again for your input, the one thing I do find useful with this site is just being able to discuss the issue. That can help a lot.
Have you tried to open SQL Server Configuration Manager and check the SQL Server Network Configuration | Protocols for MSSQLSERVER (or your instance name) | TCP/IP | IP Addresses tab to ensure it lists the proper, new, IP address?
Kevin