Slow performance after IP change

Question

_{Friday, April 21, 2017 6:38 PM}

Recently we had to change internal IP Addressing, and since that change, network performance has been rather slow, with some timeouts through web sites.

We did this change by the book, meaning we changed IP's for all member servers, then immediately powered them off. The domain controller (Windows 2008R2) was last, and we powered it down. We brought it back up, rebuilt DNS and DHCP with new IP values, then the member servers. All servers are talking to each other fine and workstations are get correct DNS and DHCP values, but still there is a sluggishness I cannot explain.

Anybody have an idea where I can look to see what is causing this?

All replies (8)

_{Tuesday, May 2, 2017 7:23 AM ✅Answered}

Hi dhall1,

>>* As an example, occasionally, a database request will time out waiting for the SQL Server to respond.*

Please use network monitor to analyze the network performance when a database request times out occasionally.

Best regards

Candy

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Monday, April 24, 2017 9:14 AM}

Hi dhall1,

>> Slow performance after IP change

1.Type netsh winsock reset in command prompt and hit ENTER button.

2.Restart the computer in order to complete the reset, after that test to access your network or Internet again.

Please try to reset TCP/IP with the commands of netsh int tcp reset and netsh int ip reset.

With the command of tracerouteto display the route (path) and measure transit delays of packets across an IP network.

You could also use network performance analysis to check system’s memory, processor, and disk systems:

https://technet.microsoft.com/en-us/library/cc938654.aspx

Best Regards

Candy

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Friday, April 28, 2017 4:44 AM}

Hi dhall1,

Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

Best Regards

Candy

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Friday, April 28, 2017 1:19 PM}

I have done these steps, and have had minimal results, at best. The issues seem to be DNS-related, although the DNS settings have been all verified, and they do work. As an example, occasionally, a database request will time out waiting for the SQL Server to respond. At that time, the SQL server is fully operational and responding to other requests.

Also, logins seem sluggish, as if struggling to find domain authentication.

_{Friday, April 28, 2017 1:52 PM}

Hello,

Check all your DNS servers for duplicate entries of the old IP's and remove them if necessary.

Also check and statically assigned servers/pc's/devices for static DNS entries of the old IP addresses and make sure your DHCP server are assigning the correct DNS IP's of the new servers.

Lastly, make sure you update DNS delegation:

https://technet.microsoft.com/en-us/library/cc816882(v=ws.10).aspx

Miguel Fra
Falcon IT Services
https://www.falconitservices.com

_{Friday, April 28, 2017 2:06 PM}

This has also been done. The parent zone is pointing to the proper, updated IP addresses of all domain DNS controllers, and there are no entries for the old IP scheme

_{Friday, April 28, 2017 2:26 PM}

Are you using WINS ?

Have you cleared DNS cache on all affected systems + DC's ?

Miguel Fra
Falcon IT Services
https://www.falconitservices.com

_{Friday, April 28, 2017 2:29 PM}

No, no WINS at all. Yes, cache has been cleared - many times