Error Code 499: Unrecognized Network Error

Keywords: Error Code 499  WIL Extender error unrecognized network error

---

499: WIL Extender Error: Unrecognized network error -53

• This error message indicates that the WIL extender isn't finding your network path.

• Make sure there's a \ on the end of your net path. When that is missing, you can sometimes get this error.

---

Error 499: Unrecognized network error 1245: Username=W95GetUser(@default ...

• User is getting this error message when using NetGetUser. Also gets this same error with the W95GetUser function.

• This error indicates that the user is not currently logged on. For NetGetuser to work, the user has to have completely logged into the system. With Win95, this is usually due to a timing problem. WinBatch doesn't wait for the user to finish logging in. If you can manually log in OK but not with the script, it's probably a timing problem. You will need to put in a TimeDelay(15) (some specified length of time that's enough to guarantee that the user has finishing logging in) to get NetGetUser to work.

---

Error 499: Unrecognized network error 1219

What I am trying to do is a netaddDrive command and it works sometimes yet doesn't work other times. I have not yet been able to establish a pattern. Any ideas???

1. The 1219 error indicates a credential conflict:

   	"The credentials supplied conflict with an existing set of credentials"
   

   Sounds like maybe the user is already mapped to the server with a different password, or something like that. In that case, try disconnecting the other userid connected to that server, and remap the drive.

   TIP: To Overcome User Conflict:

   When connecting to a share on another system (for example, MACHINEA), if you suddenly receive the message:
   "The credentials supplied conflict with an existing set of credentials."

   This occurs when you have connected to the machine with another user ID. If you are not aware of what user ID you used and you want to use another ID, you can disconnect the previous share by entering the following command:

   	NET USE \\MACHINEA\IPC$ /DELETE
   

2. This error can also occur with wNTAddDrive and w95AddDrive, when another userid is already connected to that server (and authenticated) from that workstation.

---

Error 499: Unrecognized Network Error 1240

I am getting extended error 499 unrecognized network error 1240 when trying to execute the NetAddDrive command. This is only happening with NT 4.0 on new computers. Older NT 4.0 systems contine to make connections with no problems.

• 1240: "The account is not authorized to login from this station."

• Sounds like a server configuration problem.

---

Error 499, unrecognized network error 1326:

I've got a program which reads an IP from a file, then uses the default administrative share on a windows NT 4 system, like the following:

UNC = StrTrim(IP)
UNC = StrCat("\\",UNC)
UNC = StrCat(UNC,"\C$")
Message("UNC is:",UNC)

if xDriveReady("L:") then
wntCancelCon("L:",@false,@false)
endif

Mapped = wntAddDrive("administrator","pw",UNC,"L:",@false)
if Mapped then 
FileWrite(LogFile,"Mapped using pw")
goto success
endif

I receive an error 499, unrecognized network error 1326 when the wntAddDrive command is executed.

If the password isn't correct, shouldn't the map operation fail and have the program continue? or is the problem the use of the default share "c$"? if I drop to a command prompt and give the command "net use L: \\[IP address]\C$ "pw" /user:administrator it does map the drive.

Answer:

The error from the docs is:

// MessageId: ERROR_LOGON_FAILURE
//
// MessageText:
//
// Logon failure: unknown user name or bad password.
//
#define ERROR_LOGON_FAILURE 1326L

I would avoid C$ as it is usually an "administrative" share for intercomputer communications. Try a real share.

---

Article ID:   W12959

Filename:   499 Unrecognized Network Error.txt