New computer cannot access NAS

[Fuzz]

I have just setup a win 2000 machine, and joined it to the domain. When I attempt to connect to the NAS I get a request for password. I tried entering my name and password, but it won't give me access. I have admin access for the domain, so it shouldn't be a problem.

The NAS is setup in domain security mode. Server 20003 is the domain controller. I also have one other machine(that I know of so far) that has the same problem. if I browse to \\[NAS]\home\[domain] from another machine, I see a list of users and computers as folders. I am assuming these are created when a machine logs on to the NAS. I don't see the names for the 2 machines that I can't access the nas with. Anyway, any ideas on why I can't connect with these machines? All other compters havn't had a problem. I have the NAS device mapped through a logon script, so most computers are showing up fine.

Update: If I use the IP address, instead of the NAS name, I can connect.

[yoh-dah]

I wonder if this might be a Windows login caching problem. Have you tried rebooting the Win2K system?

[Fuzz]

ya, a few times. The other machine that hasn't been able to connect is running windows XP.

[Fuzz]

Interesting . . . after installing SP4 on the 2000 machine, the drive mapped through the login script without a problem. It now also has a folder in the home directory. Is there somthing dependent on a newer service pack, perhaps? The XP machine is still misbehaving. The only difference I can see on that machine on the network is that it runs PC-Cillin AV. The rest are on Nod32.

[Skywalker]

I can't imagine the AV software making a difference with Domain Authentications, but I suppose it is possible. Can you make sure that your client (the XP machine in this case), the server, and the ReadyNAS all have synced clocks? When you register the ReadyNAS with the domain, it should try to sync up to the domain server's clock, but it didn't do this in earlier RAIDiator releases. Clock skew is one of the more common problems with AD authentication.

[Fuzz]

Your right on the time thing. It is about 8 minutes out, and I think the server is set for a 5 minute window. I'll try fixing that. I'm not sure why that one machine isn't syncing with the time server though. Computers are so much fun. It's also interesting that I am able to connect if I use the IP address, but not when I use the machine name.

[Skywalker]

If you use the IP address instead of the hostname, it doesn't use kerberos tickets.

[Fuzz]

Ok, that makes sense then. Is there any good reason not to loosen the time limit abit(or get rid of it altogether?) with regards to syncing for kerberos? Will this cause major problems, or just result in file timestamps possibly not being all that acurate?

[sirozha]

Ok, that makes sense then. Is there any good reason not to loosen the time limit abit(or get rid of it altogether?) with regards to syncing for kerberos? Will this cause major problems, or just result in file timestamps possibly not being all that acurate?

If the system time is syncrhonized via NTP, you can stop and then restart the network time service in Windows. This ususally fixes the time synchronization issues.

[Fuzz]

Ok, went to restart the service, and it was turned off. That would explain things

[Skywalker]

Ok, that makes sense then. Is there any good reason not to loosen the time limit abit(or get rid of it altogether?) with regards to syncing for kerberos? Will this cause major problems, or just result in file timestamps possibly not being all that acurate?

It's mainly just for security purposes. But with the network time service on, all domain clients should automatically sync up to the server. You might have to manually enter it in as an NTP server for ReadyNAS, since network time service wasn't started when you did the initial join with the ReadyNAS.