Mapping a samba share from XP BIG problem.

[Anonymous]

Im hoping someone will have some ideas to help me resolve this

I have a win2k3 network and a 10.4 network. I followed the AD-OD integration doc (damn fine doc that apple themselves should have written ). Anyway I have all my mac user home folders stored on the mac server, and the windows users have their home folder redirected via group policy to point to this location as well. All works perfectly, then randomly after a while I get errors from our vb login script that state incorrect username and password when mapping a drive to the mac server. This occurs mostly after I’ve logged into an XP workstation 2 or 3 times. Mostly after a reboot I can log in and succssfully map the drives, but then after a few logins the error returns. All through this I can manually open the ‘denied’ share by using the UNC path from the run dialog box with no issues.
I’ve checked my smb.conf file and this problem still occurs. My DNS is set up correctly (DNS is running on Win2k3). On friday last week I removed the autoconfig lines from edu.mit.kerberos file and the problem stopped. But today (tues) it started up again. I’ve double checked my permissions on shares. I also reinstalled both the Win2k3 and OSX server multiple times. It seems that everything I try to resolve it appears to fix the problem, but a few hours later it starts up again.

Has anyone got any ideas, short of running 2 separate networks and doing away with integration? (unfortunately if I can get this solved I have to tell the school Im doing it for on thursday that it will be 2 networks )

HELP?

[Anonymous]

yup. I can type in \\servername\sharename and access the share no problem. I can also run the win2k3 logon.vbs script manually and it connects drives perfectly.

[Anonymous]

the logon script just maps out drives based on group membership. Nothing fancy. The first line that fails is a mapping that does not rely on membership. Mappings to the shares on Win2K3 work fine via the script – it’s only ones to OSX that fail every second or third login. Once the failures start I have to reboot the workstation and then logins work again for a little while before failure again.

It’s almost as if the XP workstations try to map drives and authenicate via kerberos during login, but fail sometimes for some unknown reason. I’m heading back out to the school in about an hour or two, so I can post snippits of logs if you want.

Cheers

[Anonymous]

OK somehow managed to fix the problem by specifiying the FQDN in active directory for the home folder, but 4 hours later the issue returned. Now it seems I can reliably fix it by restarting SMB, but it can crap out from anywhere from 5 mins to many hours again.
I cant cron smb to restart every 10 mins or so, as one of the apps runs across the network and therefore it breaks if the network is interupted.

nmbd is running even when the problem occurs. Im assuming by restarting SMB that nmdb is restarted. What other child processes are started (maybe ones relating to kerberos?)

[Anonymous]

Still no go – happens less frequently now after I tinkered with some more settings and configuration, but still happens.
no-one here or the apple boards could offer any suggestions (not even one idea came forth), so we split the network yesterday into separate mac and pc networks. OSX was (is)unreliable and needs too much babysitting. Hopefully apple will work out the kinks in the future.
Unfortunately the final outcome of the project is to recommend phasing out the macs in favour of windows machines (eek didnt think I would ever recommend that).

[s_groening]

have you remembered the ‘winbind separator = +’ statement in your /etc/smb.conf ??

This seems to have solved this issue for me…

[Anonymous]

yup that was already in there (it solved slow XP logins for me adding that).

[Author]

Posts