General

[Omar]

When I try to log into Win 2K in the network, after typing
user name and password, I get the msg Loading your
personal settings, then nothing happened! any idea why?
P.S. I can log on as an admin to the local machine and
strangely enough I find my profile there!! even though I
haven't fully loggod on. P.S.2 I did delete my profile a
few times, yet to no avail! thank you

 

[SaltPeter]

When I try to log into Win 2K in the network, after typing
user name and password, I get the msg Loading your
personal settings, then nothing happened! any idea why?
P.S. I can log on as an admin to the local machine and
strangely enough I find my profile there!! even though I
haven't fully loggod on. P.S.2 I did delete my profile a
few times, yet to no avail! thank you

First of all, if you didn't have a local administrator account available to
you at that station, that W2K installation couldn't possible exist. You
can't install W2K without creating that account (although it can be
renamed). This is true whether you installed manually or used an unattended
deployment scheme.

Second, we can't guess about how your network is organized. Is it a domain?
If yes, is it a W2K domain? If you are attempting to join a domain from a
fresh installation, you must use credentials with the right to create a
computer account on the domain (a restricted right). All NT-based domains
require both a valid user account AND a valid computer account to
participate.

Last but not least, W2K can't locate/resolve anything in a domain without
DNS name resolution. The client must be able to communicate with the
domain's DNS server to find a DC and therefore achieve authentication. The
fix is to modify the client's tcp/ip properties or specify the dns
ip_address in the dhcp scope options.

All of the above is basic W2K domain 101.