NBTSTAT does work and is "secure" (at least in one domain - I have never used it in more than one). The only problem will be if the organisation does not have a SOE (Standard Operating Environment) and you may end up with NBSTAT reports that dont contain the information you need or you may have a mess finding out the correct ID of the logged in user.
I wonder if people missed what is being asked here..... He wants to be able to authenticate someone WITHOUT having to have them supply any other authentication (ie. the grey popup box). Not all networks provide the CGI authentication variables. NBTSTAT is a reasonably reliable alternative - and you can get people to authenticate if you can't do it via NBTSTAT. In terms of authenticating across two domains - you can probably sort the domains out by the IP address (even if they are dynamically alllocated) because they would still have to be in a range. We attempted to use Active Directory with LDAP in the same environment and the problem was that the LDAP information was not acurrately maintained in the AD environment. Regards, Gary Menzel --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
