Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 220
  • Last Modified:

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
0
introlux
Asked:
introlux
  • 3
  • 3
1 Solution
 
DBAduck - Ben MillerPrincipal ConsultantCommented:
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.
0
 
introluxAuthor Commented:
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
0
 
DBAduck - Ben MillerPrincipal ConsultantCommented:
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?
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
introluxAuthor Commented:
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
0
 
introluxAuthor Commented:
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
0
 
DBAduck - Ben MillerPrincipal ConsultantCommented:
If the IP changed and there was a rule in the firewall, you would be impacted.  Everything in the error log looks good and it is listening on the local and global IPs at 1433. Go after the firewall. :-)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now