Freakin' stupid ISP techs!

Viper GTS

Lifer
Oct 13, 1999
38,107
433
136
Some dumbass ISP tech sent a customer to me (network support) for a customer with 5 PC's that couldn't browse. Everything appeared normal as far as her DSL router, so I asked her to open up a command prompt. "Oh, we already did this. Just 10 minutes ago." I had her do it anyway. She can ping the router, she can ping the internet by IP address. But she can't ping by domain name... Hmm... What the HELL could that be?

People need to learn to do their freakin' jobs, & not pawn everybody off on the LAN team.

:|

Viper GTS
 

Viper GTS

Lifer
Oct 13, 1999
38,107
433
136
Or lack thereof.

For some reason the ISP's servers aren't giving the DSL router the DNS addresses, so they weren't being supplied by DHCP. Hardcoded the DNS addresses, & everything works perfectly.

But because they're on a LAN it MUST be a network issue.

Viper GTS
 

IBhacknU

Diamond Member
Oct 9, 1999
6,855
0
0
/me smiles cause he had some idea what the problem was

(and no training WHAT-SO-EVER! :) )
 

Viper GTS

Lifer
Oct 13, 1999
38,107
433
136
Not to mention that the customer is a total asshole. I told the guy that we'd fixed the main issue, & that what was left was browser & possibly line issues. His response?

Customer: "Fellow, you're blowing smoke. It's doing the same goddamned thing it's been doing for the last 24 hours."
Me: "Sir, there are multiple layers to your problem. When you called me you were unable to ping by domain name. I've fixed that issue. Your connection IS working, it's just a matter of making the browser function properly."

My only consolation is the tech I got for him actually knows what he's doing, & is working quite well with the customer.

Viper GTS
 

guyver01

Lifer
Sep 25, 2000
22,135
5
61
Viper GTS .. that's not as obvious a problem as it seems... its usually NOT a DNS issue.

Here's the surefire test..

goto a dos prompt.. and try to FTP by domain name. If you get a SOCKET response... it's a problem with the WINSOCK stack.

I work as a Tech for an ISP, and 99% of the time, if they can ping by IP, but not FQDN, it's an OS issue.... sure way to find out... FTP... or use Netscape... if it gives you "cannot make a socket connection" .. there ya go!

 

Viper GTS

Lifer
Oct 13, 1999
38,107
433
136
guyver01...

In this case it was the DNS servers. My experience has been 99% the other direction... If they can ping by IP address, & not domain (getting an unknown host error), it's DNS.

Viper GTS
 

Poontos

Platinum Member
Mar 9, 2000
2,799
0
0
guyver,

1.) If the ping times out and no host is found via domain name, but the IP works, then it's normally a DNS issue.

2.) If the ping (or any network command; telnet, ftp, tracert, etc.) gives a socket error, then we have a Winsock problem or operating system malfunction. Un-install all network components and re-install.