Hi (whatever your real name is, but we all use our real names here, you
should follow this rule!),
i do not recommend to use a domain controllers main network interface
over a wireless network, because if you have heavy logons and data
transfer, this could end up in serious speed problems and it is also
a great security threat when someone was able to crack your encryption
keys, he will be able to "sniff" your data. Your networking
Interface should be activated when you boot and your system shows
the logon screen. But if you have some special drivers or connection
software that needs someone to logon, you should write a starter
programm or a strartup script e.g VBS or a language you like to
start the application with system startup. The Interface should, if on
a server, statically configured or when dhcp is used assign a static
address with MAC Reservation for the Interface. But if you have some
special GPO's that deactivate or prevent your interface from
connecting/working
with the Network Environment you must reconfigure them!
Everbody who has accees to your network whether wired or wireless,
cann connect to your domain when he/she/it has the sufficiend access rights
and all the passwords. There are some limitations on ActiveDirectory and
GPO's between XP and 2000 but most of them you will never use or are
in most env. unnecessary. I can tell you this, because i am a BOFH and
responsible
for over 200 Systems including *nix, Novell, Mac and Windows NT-based
Machines. ;-)
Best Regards
Kerem Gümrükcü
"M P" <(E-Mail Removed)> schrieb im Newsbeitrag
news:%(E-Mail Removed)...
> Hi!
>
> I am planning to use wi-fi instead of wired network, but it seems that
> wi-fi network only activates when user logged on to user. I have a Windows
> 2000 domain and users need to connect to the domain to run scripts and be
> able to access network resources. I have users running Windows XP
> Professional SP2 and SP1. Can this be possible with this setup or do I
> still need a wired network?
>
> Me
>
|