(no subject)

[chaoslore.livejournal.com]

me: the error "an operation was attempted on something that is not a socket" is operating system related so you will need to contact the manufacturer of the computer.

customer: I don't believe you, my computer was working just fine yesterday.

me: so was your Homeportal (dsl modem/router)

customer: *dead silence for about 30 seconds* *defeated tone of voice* ...Okay...I'll call Dell.

me: *does his closing*

Comments

[snoopyh42.livejournal.com]

Actually, it is an internet-related problem. Customer needs to uninstall and reinstall TCP/IP.

[chaoslore.livejournal.com]

TCP/IP and Winsock are still part of the OS...and we don't touch it in any way shape or form. The most we're allowed to do regarding tcp/ip is delete network bridges and hardcode ip addresses...

Fact of the matter is that part of the OS (In this case TCP/IP) is not functioning properly and I *can't* touch it.

[valiskeogh.livejournal.com]

hehehehe, yup, that error is a lil bitch, haven't a clue WHAT they do to cause that error, but i'll be DAMNED if i'm walking some tard through the registry to rebuild his farking tcp/ip stack...

[valiskeogh.livejournal.com]

that doesn't always work. in order to INSURE that it works, you must delete 2 registry key's. and walking an idiot through the registry is begging for trouble, and something normal inet tech support just dont do

[chaoslore.livejournal.com]

I was actually trying to point out the most simple way to stop a potential arguement w/ a customer when they say "it was working yesterday so it cant be my computer and has to be your router" the fact that there is no way a router can corrupt winsock is besides the point...

[teriwyn.livejournal.com]

From what I remember, McAffee used to cause this if you would make any changes to TCP/IP after installing a certain version of their firewall. Would chew the hell out of the stack, indeed.

[chaoslore.livejournal.com]

I've seen that happen before too, from what I understand the only way to fix that is to uninstall using the removal utility on the cd or via the directions on their site. I was under the impression though that it would only happen if you added a new network device to the computer essentially altering the NW Stack itself.

[valiskeogh.livejournal.com]

actually, i had a very simple method to quell that argument.


yesterday my car was working fine.
today it wont run at all.
it CANT be my car cause it was working FINE yesterday.

[valiskeogh.livejournal.com]

ugh, both mcaffee and norton cause their fair share of problems...

from time to time norton choses to change your incoming pop server to "127.0.0.1"

[dmsalem00.livejournal.com]

You know how many times a day I have to dig through that registry key?

Only takes five minutes, but still...

People wonder why I scoff when they say "but I use Nooortooon.."

[justsomegurl.livejournal.com]

you are one lucky duck. we are required to work with tcp/ip where I work. And i have /had/ to walk a computer dummy through removing the winsock keys. that is not fun. but lucky me another tech here found a tool that does it all. yay

[teriwyn.livejournal.com]

Yeah, at the ISP I worked for, we used to call this "NAV Syndrome". There was even a call resolution with that name that we would attach to the tickets.

Of course, certain versions of NAV always did this. We only heard about it when it stopped working. NAV would redirect the pop connections to 127.0.0.1, and then it would start listening on port 110 for the mail client to try to check email. I'm sure you also noticed that it would put the actual server name in the username field. (Something such as 'username/mail.myisp.com') When the mail client would pass that username to the "mail server" that NAV had set up, NAV would go out and check the email for the user, and pass it through. Middleware at its worst. But at least those users had SOMETHING on their PC to protect them from the virus ridden internet.

[kerberos.livejournal.com]

Don't forget those with norton ,on a modem and their pals just sent them 5+ Mb of email. Sure norton tries to suck it down, scan it then deliver it to the emailprogram, but the emailprogram goes "WTF no answer in the $timeout time, I guess I'll hang upp".

So the client doesn't get their email and call and bitch.
Yay Norton!