Followup clarification ...
It doesn't matter whether the remote client's machines are WinXP boxes
or that the machines have been joined to the NT domain. They can
still use the Netbios domain name as part of their user logon.
Thanks again for your help!
----- Phillip Windell wrote: -----
I think keeping a WINS Server running in the system will keep you covered on
that. You probably want to keep "Netbios over TCP/IP" enabled on all the
involved machines as well.
We went fron NT4.0 to Server2000 to Server2003 and have never had to change
anything from the user's perspective.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Joe" <(E-Mail Removed)> wrote in message
news:590201c42d46$02d5e770$(E-Mail Removed)...
> I have questions regarding remote clients
> and pop email account users after upgrading
> an NT domain to AD domain. There is still
> an Exch 5.5 server which will be upgraded
> to Exch 2003 in phase 2.
>> After the upgrade, will remote clients
> who use a cisco vpn client to authenticate
> on IAS\Radius be required to signon with
> FQDN name or can they still use
> nt domain\username to authenticate?
>> Also, will remote pop account users still
> be able to authenticate with nt domain\username?
>> Thanks for the help!
>>