Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
Logon Issues
- Automagically Log onto Win98
- Automated Login Problem for Windows2000
- Can Winbatch Automate the Logon to a NT-Domain
- Get Username and Copy Shortcut in Login Script
- How to Enable Automatic Logon in Windows XP
- Logon and Get MAC - Sample from User
- Logon Message on Windows NT
- Logon to unix server from WinNT using Samba
- More Login Script Details
- MS Logon Script Handles Netware Shares
- NetLogon Hints
- Novell List of users and last login times
- NT Login and Environment Variables
- NT Login Script Example
- NT Login Script for Slow Dialup Connections
- Problem using Winbatch scripts in Netware login script
- Run a Batch File Before Logging on to Your Computer
- Synchronous Logon Script in Windows 95
- Unattended Login Tips
- Win95 AutoLogon Considerations
- Winbatch in Netware Login Scripts and McAfee Issues
- Winbatch in Windows Login script considerations
- Write LOG File During Logon
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Logon Message in Windows NT
Keywords: logon login dialog
Question:
I am logging on to NT w/o connecting to a domain (I will connect later) and I want to clear the "Logon Message" Dialog box that states "A domain controller for your domain could not be contacted. You have been logged on using cached account...". The standard WinClose function does not work, because it seems the message is on another layer. Does anyone have any ideas on how to close this window??Answer:
There are a couple of ways around your problem.- In order to close the window,
use SendKeysTo or SendKeysChild (my favorite) to give it the OK function. If you are
not sure of the Child Windows, look in the Tech Support Database for "Parent and
Child Windows" to get a short script that allows you to figure them out; or you can use
the Control Panel Extender.
- To prevent the Window from showing up at all, Unclick the Logon to Domain setting in
Network properties. You are still logging into the network, so your permanent drive
mappings and shares will work, but you will NOT (try to) run a Domain Login script, so
will not get an error message.
This is the way that we have our systems setup as we login to a Novell network and map shares to an NT network whose domain controller is remotely located; it works well.
Article ID: W13509
Filename: Logon Message on Windows NT.txt
File Created: 1999:04:15:16:54:30
Last Updated: 1999:04:15:16:54:30