User Accounts Static IP address

[Paul Hadfield]

In the Dial-in settings for a user account, why is it that I can assign a
static IP address if the account is a local account, but not if the account
is a domain account?

How do you give static IP addresses to a user account within AD for use when
that user connects to the network using a VPN without using local accounts
on the VPN server?

Cheers,
Paul.

P.S. AD is running on Windows 2000 servers and the VPN server is a Windows
2000 member server with routing and remote access service enabled.

 

[Herb Martin]

In the Dial-in settings for a user account, why is it that I can assign a
static IP address if the account is a local account, but not if the account
is a domain account?

Likely due to your domain being in Mixed mode
since that is one of the features enabled on the
Domain by Native+ modes.

How do you give static IP addresses to a user account within AD for use when
that user connects to the network using a VPN without using local accounts
on the VPN server?

Native mode. Then on the AD (Users & Computers)
you can check the box on the User's property sheet
and give them an IP individually for their account.

Reason: Such a setting would "confuse" a BDC (or
be unavailable if a BDC authenticated) and going to
Native mode eliminates the possibility of BDCs.

Cheers,
Paul.

P.S. AD is running on Windows 2000 servers and the VPN server is a Windows
2000 member server with routing and remote access service enabled.

Member servers have this ability for COMPUTER(server)
based accounts since they don't replicate to any legacy
machines (i.e., NT4 like the BDCs)
[/QUOTE]

 

[Paul Hadfield]

Ahhh, I see. Our domain is in mixed mode and I have been thinking for a
while now about changing to native as we have no NT4 devices at all.

The only problem is that it is a live system that has been running for a few
years now and I wouldn't want to risk rocking the boat.

Besides the no BDC emulation, are their any other systems or services that
may be effected by switching to native mode?

Cheers,
Paul.

Likely due to your domain being in Mixed mode
since that is one of the features enabled on the
Domain by Native+ modes.


Native mode. Then on the AD (Users & Computers)
you can check the box on the User's property sheet
and give them an IP individually for their account.

Reason: Such a setting would "confuse" a BDC (or
be unavailable if a BDC authenticated) and going to
Native mode eliminates the possibility of BDCs.


Member servers have this ability for COMPUTER(server)
based accounts since they don't replicate to any legacy
machines (i.e., NT4 like the BDCs)

[/QUOTE]

 

[Herb Martin]

Ahhh, I see. Our domain is in mixed mode and I have been thinking for a
while now about changing to native as we have no NT4 devices at all.

The only problem is that it is a live system that has been running for a few
years now and I wouldn't want to risk rocking the boat.

Backups are your friend, although it isn't likely to matter.

Remember you are for more likely to have hard drive and

Besides the no BDC emulation, are their any other systems or services that
may be effected by switching to native mode?

Not negatively. DCs, AD, increase their abilities.

No BDCs, and thus you can never return to an NT
domain -- which is only an issue for those who have
just recently upgraded.

--
Herb Martin

Cheers,
Paul.

[/QUOTE]

 

[Paul Hadfield]

Thanks for your help here.

We switched the domain over to native mode and had no problems at all. Can
now give domain accounts static IP's

Cheers,
Paul.

 

[Herb Martin]

Cool. Do let us know if you experience or suspect
any problems -- you won't in all likelyhood.