Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
Networks - Servers
 | |
| |
| |
| |
| |
| |
|
- !!Users, Workstations, Domains and Machine Domains Explained
- 1932 Winexec when Opening MultiUser Files on a Network
- 523 Error Enumerating Network Resources
- App not Launching from Mapped Root
- Backslashes with Servers - Volumes - Directories
- Changing Password in Windows 95
- Client IP Configuration script
- Connect to Servers via DOS batch files
- Detect Existence of Client32
- Determine if a Tree of Directory is Mappable
- Determine if a User has Admin Rights
- Disable NetBIOS over TCPIP
- Disconnect Mapped Drives Ex Dialog
- Display a Banner or Message Box on Remote PC
- Find out what Drive Letter is Mapped to Server
- Find Users Logged on Other Machines
- Finding and Listing Processes on Remote
- Getting Currently Connected Usernames to NT Share
- Global Net Map Setting
- Hiding Drive Mappings
- How do I see Im logged on
- Installing your Network via Windows Setup
- Is Network Alive
- Log Off User after an Amount of Time
- MSIE Proxy Server Control
- Net Use Command and Passing Passwords
- NT to Novell Translator
- RASSAPI.dll not Found
- Remote Launch of Winbatch
- Replication Manager - Replicate BDCs
- Sample Code Extracts Authenticating Server Name
- Segment Load Error
- Send Messages to Users
- SNMP in WinBatch
- Test Network Drive Mappings
- Unexpected Network Error
- Update All NT Existing-New User Registry Configs
- Use of Newer Network Extenders with Older Winbatch
- Using a BAT File to Launch Subsequent Operations
- Validate a Userid and Password
- Wake up Machine on LAN
- Who is Logging on to Remote NT Server
- Win32 Network Errors
- Workaround for Network Error 510
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
WIL Extender Error 52: Unexpected Network Error.
Keywords: 52: Unexpected Network Error.
Question:
I have an executable which resides in the NETLOGON share along with the requisite dlls (www95...,wb..., radmin.., rlocal...). I get an error when the netlogon share, Z: is released upon completion of the logon script processing, and something doesn't get cleaned up properly. I can attach to NETLOGON after the fact and execute the WIL program with no problems.Any suggestions about placement of the dlls, or should they be ok in the NETLOGON share along with the compiled WIL program?
I also have another "quirk" that I can't seem to resolve.
- Start WFW.
- Logon to domain.
- WIL program runs. Since WFW can only process batch files during logon. I have replaced the LMSCRIPT.EXE with the WIL program that I want to execute. This all seems to work, except that the DOMAIN LOGON Window had to be closed from within the WIL program. Am I missing something that needs to be done to "POST" the logon processing complete? (I've heard rumours about an LMSCRIPT.$$$ semiphore file). Hopefully, you can enlighten me on that one.
- User logs off of the domain.
- Another User logs back on to the workstation. This is where it gets interesting. When the WIL executes a second time, the first attempt to attach to a network drive results in a WIL Extender Error 52: Unexpected Network Error. The Wil program terminates.
- User closes out the Domain logon processing window
- User logs off
- User logs back on. This time the WIL program will run to completion.
What do you think I've got screwed up?
Answer:
It sounds kinda like WinBatch is on one of those network shares that is getting cancelled. Can't find its EXE or DLL and crashes.Move the compiled EXE and the two win95 dlls to a directory on the client's path, such as the C:\windows directory, to resolve the problem with the 95 logon scripts creating an illegal operation.
Additionally, a lot of people have had a lot of luck running WinBatch EXE files from a BAT logon script via the:
START /w abc.exemethod where the WinBatch script is launched via the DOS START command. Search for START on our website to find examples of how to do this.
Article ID: W13500
Filename: Unexpected Network Error.txt
File Created: 1999:04:15:16:54:26
Last Updated: 1999:04:15:16:54:26