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.
Workaround for "510: The network is not present" Error
Keywords: error 510 error
Question:
I'm seeking a workaround for the 510 error which occurs if the client is not logged into the network. I've tried a few variations of err=LastError(0) without success because WinBatch considers the 510 error FATAL and shuts down before the error trap can work. In good old BASIC the syntax OnErrorGoto (or equiv.) was nifty. Is there an equivalent here? How can I detect negative connectivity to a network without winbatch choking??Answer:
I quick glance at a couple of w95 computers running as Primary Login "Microsoft Network" shows that the registry setting @REGMACHINE, Network\Logon[LMLogon] is equal to 01,00,00,00 if you are logged in and 00,00,00,00 if you are not. Netware and Banyan logins have their own registry settings that show logged in status (they also have the dos WHOAMI call which tells you if logged in or not).Check the computers in your environment and check the above registry setting in both cases, whether logged in or not. This may tell you in your specific case whether your users are logged in or not before they get a dreaded 510 error.
Article ID: W13505
Filename: Workaround for Network Error 510.txt
File Created: 1999:04:15:16:54:28
Last Updated: 1999:04:15:16:54:28