Sunday, February 03, 2013 7:32 PM
One of my clients
got bought out and they wanted me to change the IP's. So I changed the
modem/router from 192.168.0.1 to 192.168.10.1 then I changed the server, all
workstations and the printers to 192.168.10.xxx from 192.168.0.xxx. Everything seemed
fine but only 1 workstation was very slow. So I ran some hardware diags on it
and then left for the day. The next day I got a message that the one slow workstation
is fine now but other ones are slow and getting errors or cant connect to the
program they use that there data is on the server. I called them today and now
most of the workstations are working fine.<o:p></o:p>
Can someone please point me in the right direction to fix this or what i did wrong?<o:p></o:p>
Sunday, February 03, 2013 8:56 PMdns? wins?
legacy hosts file?
- Edited by CountryStyle Sunday, February 03, 2013 8:56 PM
Sunday, February 03, 2013 10:04 PMYes it is a domain, no wins, what do you mean by legacy hosts file?
Tuesday, February 05, 2013 3:21 AMCreate record in the local host file should speed up the process.
Tuesday, February 05, 2013 11:25 PM
When the network address range was changed, have all the DNS updated server IP address been updated on the clients. And the have all "A" Records for the clients been updated in DNS.
- When a workstation is having problems, can you connect via IP address.
- Can you ping via Hostname and IP
- What does nslookup resolve the application server to when the workstation is having problems
Wednesday, February 06, 2013 7:33 AM
it's only one workstation right?
have you tried going to an elevated command prompt and type:
ipconfig /all and check whether it has the correct IP?
it could be also that the workstation has a fixed IP (with the previous settings) so it has to be changed manually.
Every second counts..make use of it.
- Marked As Answer by Aiden_CaoMicrosoft Contingent Staff, Moderator Wednesday, February 20, 2013 2:49 AM
Monday, February 11, 2013 3:04 AMModerator
How are things going? I just want to check the status of the issue. If you have any update or concern, please feel free to let us know.
If you have any feedback on our support, please click here
TechNet Community Support
Monday, February 11, 2013 11:56 AMas you have changed all your Ip subnet After doing this you will have to point your workstation to the new dns server ip address.