__________________
A retired member of the Canadian Armed Forces and a Proud member of the Forum Fighters and the Online warfare Pact Forum Fighters official site | Online warfare Pact
Any man who is under 30, and is not a liberal, has not heart; and any man who is over 30, and is not a conservative, has no brains. - Winston Churchill
Registered: Jan 2002
Location: Frankfurt, Germany
Posts: 1164
It helped me too m8, thx for putting it on the main page.....I would of...but can't.
Hope it helps more DOD fans!
p.s. If required, I can also host the file for us.
__________________
A retired member of the Canadian Armed Forces and a Proud member of the Forum Fighters and the Online warfare Pact Forum Fighters official site | Online warfare Pact
Any man who is under 30, and is not a liberal, has not heart; and any man who is over 30, and is not a conservative, has no brains. - Winston Churchill
Registered: Mar 2002
Location: Saskatchewan, Canada
Posts: 970
I think I have the same problem, when I log onto a server I get the message that woncom ID or some crap failed. But never seems to prevent me from logging on to a server. Problem is I have no idea what this is
Registered: Jan 2002
Location: Frankfurt, Germany
Posts: 1164
This error is caused by the client's inability to communicate with the Secure Master servers properly trying to validate the security module being used on secure servers. It can be caused by a few different problems. Clients need to communicate with the Secure Master servers (port 27012). Here are some things to try:
1) Make sure you do NOT have a file called "woncomm.lst" in your \dod folder. If you do, delete it. This file should ONLY reside in your \valve folder.
2)the "woncomm.lst" file in your \valve folder (using notepad) and make sure there is an entry that looks like this at the bottom of the file:
3) If your "woncomm.lst" file DOES have the "Secure" entry and you still can't connect properly to the Secure Master servers, it might be a DNS problem. Try changing your "Secure" entry to look like this:
Secure
{
:27012
:27012
:27012
}
Here are the 'guts' of the file 'woncomm.lst' given for download above:
// Server Lists
//
Titan
{
half-life.east.won.net:6003
:6003
half-life.central.won.net:6003
}
Auth
{
half-life.east.won.net:7002
:7002
half-life.central.won.net:7002
}
Master
{
half-life.east.won.net:27010
:27010
half-life.central.won.net:27010
}
ModServer
{
half-life.east.won.net:27011
:27011
half-life.central.won.net:27011
}
Secure
{
half-life.speakeasy-nyc.hlauth.net:27012
half-life.speakeasy-sea.hlauth.net:27012
half-life.speakeasy-chi.hlauth.net:27012
}
As you can see, they have changed the middle server to the ip and away from the DNS name, except for the Secure servers. Seems the DNS's are acting up in certain locations, as usual.
Ping the servers themselves (use the DNS) to check their connection and use then use the ip given if you wish to change all DNS entries to the ip's for testing.
A word of advice. If you must punch the wall, have a good working knowledge of where the 2x4's are........
__________________
A retired member of the Canadian Armed Forces and a Proud member of the Forum Fighters and the Online warfare Pact Forum Fighters official site | Online warfare Pact
Any man who is under 30, and is not a liberal, has not heart; and any man who is over 30, and is not a conservative, has no brains. - Winston Churchill
