Post reply

Change of IP from Dyanamic to Static

  • July 14, 2003 at 9:38 am

    #64648

    I changed the IP Address of my database server from Dynamic to static. And ever since, users are not able to connect to the instance. They are able to ping the server and I can see it is using the new address when trying to connect to the machine. Please let me know what else should be done so that the users can connect.

    Thanks for all the help

  • July 14, 2003 at 9:47 am

    #465364

    Can you connect it with ip address? Check SQL Server errorlog for error message.

  • July 14, 2003 at 10:03 am

    #465368

    Make sure that name resolution (NetBios or DNS) is not the problem. Does the client connect using a host name vs. the actual IP address? If so, try changing it to the static IP address instead. See what happens.

    You can see what IP address NetBIOS has recently cached by using:

    NBTSTAT [-a RemoteName] [-A IP address] [-c] [-n] [-r] [-R] [-s] [interval] ]

    Use ping -a destination-host to determine the dns resolution.

    Just a thought.

    All the best,

    Dale


    All the best,

    Dale

    Author: An Introduction to SQL Server 2005 Management Studio

  • July 14, 2003 at 10:32 am

    #465372

    Thanks for the responses. I cannot connect with the IP either. And on one of the client machines, I put the static IP in the hosts file. Tried to ping the server and I see it uses the new IP and I get a reply back. But when I try the NBSTAT command with just the machine name, I still see the old IP address !!! Is the old IP cached somewhere?

    Thanks

  • July 14, 2003 at 10:42 am

    #465373

    If you use NBTSTAT with the -RR parameter, it will do a release and refresh. If you use NBTSTAT with the -R parameter, it will purge the contents of the NetBIOS name cache and then reloads the #PRE-tagged entries from the Lmhosts file.

    All the best,

    Dale


    All the best,

    Dale

    Author: An Introduction to SQL Server 2005 Management Studio

  • July 14, 2003 at 10:45 am

    #465374

    Please check your Errorlog file on the hard disk. See is there any Error number

    Shas3

  • July 14, 2003 at 11:48 am

    #465388

    Guys, thanks for the help. We figured it out at last. It is the issue with Firewall. The port which we configured for SQL Server to listen had to be opened.

    thanks

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply