steel1212 Posted March 9, 2012 Share Posted March 9, 2012 Buddy can't get on at work. Its not blocked but it keeps rerouting to old server. He also can't clear history as its on a network and he doesn't have access. Link to comment Share on other sites More sharing options...
Mark R Posted March 9, 2012 Share Posted March 9, 2012 (edited) Try this...make sure the ...\ETC\Hosts file does not have an entry for the old server in it or change it to new if he does. path in Windows is ... C:\WINDOWS\system32\drivers\etc path in Linux/uunix is /ETC Edited to add: you can edit the HOSTS file with notepad in winidows...vi in unix/linux Edited March 9, 2012 by Mark R Link to comment Share on other sites More sharing options...
Mark R Posted March 9, 2012 Share Posted March 9, 2012 Are servers local or across network/internet somewhere? What OS's are you using? Link to comment Share on other sites More sharing options...
D.Hayden Posted March 9, 2012 Share Posted March 9, 2012 hosts entry is the easiest way. My ISP (Bressnan) - kept the old IP on thier DNS for about 4 days... for some resaon it wasn't refreshing Hopefully..he can add this: brianenos.com 184.170.243.26 Link to comment Share on other sites More sharing options...
Classic_jon Posted March 9, 2012 Share Posted March 9, 2012 Depending on his network setup and computer security settings he can try a couple of things if he is running windows. 1) If he has access to a DOS prompt, at the C: prompt type in "IPconfig /flushdns" that will flush the internal DNS cache. 2) This is a bit of a "round about way" but... If he does not have access to a DOS prompt, and is in windows XP, vista, or Win 7 it may work. Turn the computer totally off (not a reboot, totally powered off) wait 10 seconds and back on at least three times OR turn the Computer off and leave it off for at least 15 minutes. That *should* force the computer to re-register its internal DNS table OR get the domain to think the computer is "off" and refresh the internal DNS table. The reason for the "three times" is that sometimes win XP and later will "cache" login and DNS info for three reboots. After that it will request updated info from the network. 3) If you do this, be willing to give websites as an example to the IT people. **If it will get him in trouble at work, don't do this.** Call the IT department and tell them "I am having problems with getting to some pages on the internet, or it is very slow getting there. They recently changed their server IP addresses so could you please take a look and see if we can refresh our DNS information and see if that fixes it? 4) Wait and see if it is just taking time to propigiate and refresh the DNS information to get to the correct place. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now