Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
SQL Server issue due to Server IP Change

Answered SQL Server issue due to Server IP Change

  • Saturday, May 05, 2012 10:11 AM
     
     
    Sign In to Vote
    0

    Hi,

    I have changed my IP address for my Database Server. I'm using a VB application for our Hospital HIS System. Application was accessing the Database using the IP Address previosly, now after the IP Change i couldnot access the DB using the IP .. Now i'm connecting the application using Server Name. I have read many Forums. And i have found the IP Address in SQL Server Configuration-->SQL Server Network Configuration--> Protocols for MSSQL Server-->TCP/IP .

    So could some one help me if i change the IP Address in SQL Server Configuration-->SQL Server Network Configuration--> Protocols for MSSQL Server-->TCP/IP with my new  IP whether this will corrupt my DB? Please find the Sreenshot below regarding the IP Address.

    Regards

    Shijin Prasad

    Shijin Prasad

     

All Replies

  • Saturday, May 05, 2012 12:35 PM
     
     
    Sign In to Vote
    0
    For a normal SQL Server instance, not a cluster, this should be a transparent change. My first guess: Check the firewall settings on the server and the clients.
     
  • Saturday, May 05, 2012 1:38 PM
     
     
    Sign In to Vote
    0

    Could you please tell me what i have to check on the firewall settings on my DB Server? Because my Firewall on all my Clients are already disabled through Group Policy..

    Shijin Prasad

     
  • Saturday, May 05, 2012 2:25 PM
    Moderator
     
     Answered Has Code
    Sign In to Vote
    2

    So could some one help me if i change the IP Address in SQL Server Configuration-->SQL Server Network Configuration--> Protocols for MSSQL Server-->TCP/IP with my new  IP whether this will corrupt my DB? Please find the Sreenshot below regarding the IP Address.

    Under the Protocols tab of the TCP/IP properties, you can specify Yes for "Listen All" so that SQL Server listens on all network interfaces.  The IP Addresses tab may be used to selectively listen on some but not all if you have special needes.  IP addresses are automatically picked up from the Windows network config so you don't normally need to change those.  Any changes require a restart of the SQL Server service.

    If you can connect by IP address but not name, it is likely due to a name resolution problem.  Try pinging the server by the same name in your connection string.  Perhaps a DNS needs to be updated.

    The Powershell command below will verify connectivity to port 1433 by server name.  Just replace "YourServerName" with the actual server name:

    1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect("YourServerName",$_)) "server listening on TCP port $_" }

    Dan Guzman, SQL Server MVP, http://weblogs.sqlteam.com/dang/