Networking Forums

Networking Forums > Computer Networking > Windows Networking > Client authentication after NT Upgrade

Reply
Thread Tools Display Modes

Client authentication after NT Upgrade

 
 
Joe
Guest
Posts: n/a

 
      04-28-2004, 05:26 PM
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!


 
Reply With Quote
 
 
 
 
Phillip Windell
Guest
Posts: n/a

 
      04-28-2004, 06:29 PM
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!
>
>



 
Reply With Quote
 
=?Utf-8?B?Sm9l?=
Guest
Posts: n/a

 
      04-29-2004, 12:36 AM
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!
>>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
IAS Authentication With XP Workgroup Client Hiwj Windows Networking 1 12-16-2006 08:40 PM
Cisco 1232AP and Z-Com client card authentication problems seetext@body.com Wireless Internet 2 09-12-2006 06:52 PM
Linux Client Software To Enable Integrated Windows Authentication? Richard Huelbig Linux Networking 1 01-28-2005 03:50 AM
Microsoft 802.1x Authentication Client =?Utf-8?B?RG9taW5paw==?= Windows Networking 3 12-21-2003 08:46 AM
Enable Windows 95/98 client for NTLM 2 authentication Chuck Duchon Windows Networking 0 11-10-2003 06:25 PM



1 2 3 4 5 6 7 8 9 10 11