Win2K Roaming Profile Problem

[Garry S]

My romaing profiles path are configured correctly with the right permission
but I'm getting this error during log-on on WinXP Pro.

"Windows cannot locate the server copy of your roaming profile and is
attempting to log you on with your local profile. Changes to the profile
will not be copied to the server when you logoff. Possible causes of this
error include network problems or insufficient security rights. If this
problem persists, contact your network administrator."

DETAIL - The network name cannot be found

Please help.

Thanks in advance,
Garry

 

[Herb Martin]

My romaing profiles path are configured correctly with the right permission
but I'm getting this error during log-on on WinXP Pro.

It always worries me when someone with a problem says,
(words to the effect) "everything is configured correctly",
but down below is your likely problem.

"Windows cannot locate the server copy of your roaming profile and is
attempting to log you on with your local profile. Changes to the profile
will not be copied to the server when you logoff. Possible causes of this
error include network problems or insufficient security rights. If this
problem persists, contact your network administrator."

DETAIL - The network name cannot be found

Generally such problems are name resolution based. In a Win2000+
domain with 2000+ clients this probably means DNS (but NetBIOS is
also possible for share problems.)

Check that the DNS clients (including the servers, they are DNS clients
too) are all using ONLY the "Internal" dynamic DNS server (set) in
their NIC properties.
Double check that your DNS is dynamic, and that the expected server
is registered.

Try nslookup for resolving the server name (the one with the profile
share).

You can also mount it manually to insure it is accessible.

 

[Garry S]

Sorry i'm new to this, so please bear with me

Check that the DNS clients (including the servers, they are DNS clients
too) are all using ONLY the "Internal" dynamic DNS server (set) in
their NIC properties.

My PDC's IP address is set to 10.0.0.2, and its Primary DNS server is set to
the same IP (10.0.0.2).

My WinXP's IP address are set to 10.0.0.X and its Primary DNS is set to
10.0.0.2. Am I doing it right?

Double check that your DNS is dynamic, and that the expected server
is registered.
Try nslookup for resolving the server name (the one with the profile
share).

I'm prettey sure that my DNS is not dynamic since I've statically assigned
the Primary DNS Server (10.0.0.2). I got this message when I type nslookup
on the PDC:

**** Can't find server name for address 10.0.0.2: Non-existent domain
**** Can't find server name for address 10.0.0.2: Non-existent domain
**** Default servers are not available
Default Server: Unknown
Address: 10.0.0.2

You can also mount it manually to insure it is accessible.

As I've said, I'm novice to this, kindly guide me how to do this.

Thanks a lot for your time,

Garry

 

[Herb Martin]

Sorry i'm new to this, so please bear with me

Not an issue -- and don't be offended if we just correct
your errors without apology.

My PDC's IP address is set to 10.0.0.2, and its Primary DNS server is set to
the same IP (10.0.0.2).

If it's Win2000 then it is not really a PDC, but just a DC.

I presume your DC is also the DNS server; if so, the
above is configured correctly.

My WinXP's IP address are set to 10.0.0.X and its Primary DNS is set to
10.0.0.2. Am I doing it right?

IP sounds right. Your clients don't have a "PRIMARY" DNS server;
they have a PREFERRED server. Picky here about the language
because "primary" has another technical meaning in DNS.

I'm prettey sure that my DNS is not dynamic since I've statically assigned
the Primary DNS Server (10.0.0.2). I got this message when I type nslookup
on the PDC:

No, you need static IP addresses but you also need the DNS ZONE to
accept dynamic registration. On your DNS server, right click on the
zone\Properties\ and set the Dynamic Updates to "Yes" or to "Secure
Only."

Difference here is between the server as a machine, the server as a client,
and the server providing registration and resolution for a particular zone.

**** Can't find server name for address 10.0.0.2: Non-existent domain
**** Can't find server name for address 10.0.0.2: Non-existent domain
**** Default servers are not available
Default Server: Unknown
Address: 10.0.0.2

The above is an INNOCUOUS error of "nslookup" that can be safely
ignored in almost all case. This is JUST an artifact of the way NSLookup
tool works.

The key is what NSLookup reports AFTER that initial info...does it
resolve the address that you are trying to test or not?

As I've said, I'm novice to this, kindly guide me how to do this.

net use * \\servername\ProfileShareName * /useromainName\Username

Note the above is NOT a "fix" but rather a way to manually test
to try to isolate the problem.

 

[Garry S]

I appreciate your corrections, no worries. Your hints led me to resolving
the problem. My profileshared folder has a parent folder and i was stupidly
include it on the profile path.

Thanks a lot for your help.