asked on

SQL Server Problem - IP Address Changed

IP Address has recently been changed on the server. We have used a number of different application to access the SQL Server. Using data source and applications such as Marsc now cannot access the server.

Any suggestions of what the problem is. Have ensured all the port numbers etc... are correct but still no luck and we have come to a brick wall dead end!

This doesn't appear to be a firewall issue on our side. We are only assuming it is most likely an issue with SQL Server itself or firewalling on the InterXion side of the link.

Any help will be appreciated on this matter.

Thanks,

introlux

DBAduck - Ben Miller

The IP Address changed on the SQL Server. Has the SQL Server been restarted? When SQL Server starts it listens on certain IP addresses and ports. If the IP address changes on the server, the server has to be ready to listen on that IP, so if you restart SQL Server service, then it should now listen on the new IP. This is the only thing I can gather from the information that you have provided.

If there is more information about your environment, let us know.

introlux

ASKER

Well we have already tried restarting the server. But still no luck. Any application that we try to use to access this server is not working. The only connections it allows is via RDP and Logmein that we use to do file transfer for the time being because the mapping of the drives cannot be done at present.

What other background info will you require to come up with solutions??

introlux

DBAduck - Ben Miller

You need to ensure that in the SQL Server Errorlogs that it shows that when the SQL Server started up that it was listening on the IP address that is new on the machine. Then once that is true then we can go from there, but that is the first thing you need to check.

What version of SQL Server? 2005? 2000? What edition? Standard? Workgroup?

introlux

ASKER

The version we are currently using is Windows 2000 Service Pack 4, standard edition.

I have also attached the error log.

Thanks,

introlux
log.txt

introlux

ASKER

It looks like it was a firewall issue from the sql server. Port number 1433 has now been given access and now works :-) hopefully all the other services we are awaiting has the same issue!

Thanks for all the guidence on this topic!

introlux

ASKER CERTIFIED SOLUTION

DBAduck - Ben Miller

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer