I have confirmed that navigating the browser to http://74.54.39.14 works, so a traceroute there should work.
I am not on the network. A friend of mine works at a small business and their IT guy is apparently retarded.
It definitely sounds to me like there is a filter setup on the router that is messing with this IP address, but why would it be just this one? I think they need a new “IT Guy”
pings and traceroutes are being filtered by the router/firewall apparently. So no ICMP commands are going to work to diagnose. He actually can navigate to http://74.54.39.15, but they are getting a different website. Multiple sites on 1 box probably, no biggie. So that tells me that ICMP is being filtered and were not gonna get anywhere with traceroutes and pings.
yes you are right, dns look-ups DO use UDP. It is all coming back to me now. Should have an answer from him soon what the result of the nslookup is. I am betting there is a domain controller on the network that handles DNS and it has a bad cache.
no the DNS server is feeding the wrong IP back to the workstations. Hence, no website is reached.
They recently switched their hosting company, my guess is that there is a static DNS Entry setup on the server pointing to the IP address of the old hosting company’s server. Silly “IT Guy” never switched the DNS Entry.
I don’t think they have AD setup. I think it is just a basic Domain Controller, but honestly, I am not by any stretch of the word a Windows Admin.
I have a feeling that this “IT Guy” has no fucking clue what it is I told to my friend. Ironically, in normal, I don’t know what the fuck to do, fashion, the guy is going to reboot the server tonight and hope that it fixes itself.
He is clueless.
I should just sit through the damn training videos and start freelancing at small business shops like this. I would make a god damn killing.
AD relies on DNS…most of the time places use theirdomain.com so on the domain controllers Microsoft DNS is running…You use the DNS tool and change the A record for WWW and the A record for theirdomain.com to the correct IP.
Its in Start|All Programs|Administrative Tools|DNS or the real path is %SystemRoot%\system32\dnsmgmt.msc
Depending on how your DNS server is setup in windows you can either forward requests on to another DNS server or perform the DNS lookup on your own off root servers…
If the domain you’re having issues with is not related to the AD environment there could be other issues…an extremely long TTL for the DNS records of that domain…or whatever DNS server you use are setup incorrectly…or the DNS is taking forever to propagate…