Network geeks gather round for some troubleshooting

OK, here is the problem. I have a group of people inside a network who cannot reach a website.

www.clpa.com

They can reach ANY other website. They can all reach the website from OUTSIDE the network, as can I.

  • IP of the web server according to “host” 74.54.39.15

  • hosts file is clean

tracert output:

Tracing route to f .27.364a.static.theplanet.com [74.54.39.15]
over a maximum of 30 hops:

        1 Destination host unreachable.

Trace complete.

route print output:

===========================================================================
Interface List
0x1 … MS TCP Loopback interface
0x2 …00 07 e9 b9 16 95 … Intel® PRO/100 VE Network Connection - Packet
Scheduler Miniport

===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.60 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.60 192.168.1.60 20
192.168.1.60 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.60 192.168.1.60 20
224.0.0.0 240.0.0.0 192.168.1.60 192.168.1.60 20
255.255.255.255 255.255.255.255 192.168.1.60 192.168.1.60 1
Default Gateway: 192.168.1.1

Persistent Routes:
None

Can you help diagnose? Any other steps?

Only thing I can think of is the routing tables on the router, or someone has filtered the IP address on the router

Try tracerouting 74.54.39.14 and 74.54.39.16 and google post results…

Its probably a routing issue in your firewall…

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”

lol they need a good managed services company

OK

the mystery is unfolding

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.

All signs now pointing to DNS

does nslookup use ICMP?

nslookup doesn’t use icmp it uses udp and can use tcp

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.

edit: RESULTS ARE IN

nslookup www.clpa.com

*** Can’t find server name for address 192.168.1.5: Non-existent domain

*** Default servers are not available

Server: UnKnown

Address: 192.168.1.5

Name: www.clpa.com

Address: 66.235.193.54

booyah, DNS issue

:lol: amateur hour jesus

Ah, kinda sounded like a DNS issue…

haha, this is laughable indeed

yep, ipconfig confirms that 192.168.1.5 is his DNS Server

so the computers weren’t going through the DNS server?

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 assume they run a SBS or internal DNS for AD?

That happens a lot…people forget to update the internal DNS for a website.

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.

How do you update the internal DNS?

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…

but what do I know :lol:

Wow you are so smart I can only hope to be as smart as you one day

Maybe someday…but doubtful…

yeah, that is definitely out of the scope of my friend’s basic computer knowledge.

I am going to leave this one to the briliant “IT Guy” to figure out. I diagnosed the issue, it is now up to him to fix it.