73-CHOM ERROR

This is a discussion about 73-CHOM ERROR in the Everything New Technology category; when trying to connnect to the internet I received a error 73-chom the first two times then it connected. what is a 73 chom error. what does it mean. sould I worry?.

Everything New Technology 1823 This topic was started by ,


data/avatar/default/avatar29.webp

1 Posts
Location -
Joined 2005-05-21
 
when trying to connnect to the internet I received a error 73-chom the first two times then it connected. what is a 73 chom error . what does it mean. sould I worry?

Participate in our website and join the conversation

You already have an account on our website? To log in, use the link provided below.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This subject has been archived. New comments and votes cannot be submitted.
May 21
Created
Jul 25
Last Response
0
Likes
1 minute
Read Time
User User User User
Users

Responses to this topic


data/avatar/default/avatar01.webp

1547 Posts
Location -
Joined 2002-05-29
Looks like somebody else on this forum has had the same error message. It could be related to a software firewall and/or security settings.
 
Check out the GOOGLE search and remember that Google is your friend

data/avatar/default/avatar04.webp

352 Posts
Location -
Joined 2003-03-28
Either something to do with a router, firewall, or 1973 Chevelle Owners Manual.

data/avatar/default/avatar01.webp

1547 Posts
Location -
Joined 2002-05-29
Originally posted by theefool:

Quote:Either something to do with a router, firewall, or 1973 Chevelle Owners Manual.  
I prefer the latter as I owned a 74 Chevelle
 

data/avatar/default/avatar20.webp

1 Posts
Location -
Joined 2005-07-25
Had this problem come up once before. It may not the router, but when I encountered this bastard, it was AO-Hell. Seems the culprit is/was corrupted network configuration in the OS thanks to the AOL software. After deleting the ACS files (Program Files-> Common Files -> AOL-> ACS), Calling AO-Hell support, I finally got in touch with someone who actually knew that they hell they were talking about. I had to go into the CMD box and do a little command line work with the "netsh" command and remove a log file whose name I can't recall. I recall I did have to remove the WINSOCK files from the Registry.