An odd problem, and I'm not sure if it's a problem on the server side or the Windows side....

Created "%U".bat logon scripts in Samba as follows:

"%U".bat:
net use * /delete
net use F: \\server\username
net use P: \\server\programs
....etc.

Logged in from the workstation.

The script runs (Closes before I can read it) and gives no error messages.

The old network drives are still there except for F:, which no longer exists....

Oops. Change "Logon and Reconnect network drives" to "Quick Logon" under Client for Microsoft Networks. Delete all shares on the workstation. Re-write the batch file to change the UNIX carriage returns to DOS carriage returns. (Heh... Stupid DOS...)

Reboot.

Script runs.
No drives mapped.

Add "pause" to the end of the Batch, reboot

Batch runs, no pause, no drives mapped....

Run batch file from desktop.

Batch runs, drives are mapped.

I'm thinking the logon batch has been cached with the bad carriage returns, but I can't figure out where. Any ideas on whether that's the problem, or something else? I also thought maybe the batch is running before windows runs through its persistent connections, and Win98, being Win98, runs a "NET USE * /DELETE" first.

Windows doesn't cache scripts, but it does cache logon credentials - it's worth running a find in C:\Windows for *.pwl files and deleting those.

No go, but turning on extd_audit got me the following:

vfs_extd_audit: open CONFIG.POL failed: No such file or directory

Now, I was thinking about doing machine-specific Policy files through the logon scripts later, but why is it looking for it now, yet not looking for "%U.bat"?

try this...

If I'm not mistaken, /persistant is a Windows 2000 flag, and these clients are Win 98.

Also, it seems like the script is not running in the first place, as it neither attempts to access that file according to extd_audit, nor does adding "Pause" into the .bat file seem to have any effect.

it might be a windows 2k flag.. im not exactly sure...

Another thing to check is... did you make the batch file on windows or in linux???

If you made it in linux.. run this command on the file(s)...

unix2pc username.bat

that would take care of the carriage returns your think that might be the problem.

EDIT: If that doesnt work let me know... We can look into further configuration issues

Made them in Linux, realized my mistake, re-created them in Notepad from scratch.

I'm still wondering if the absense of a config.pol file is causing the "netlogon" script to error out... Perhaps I should go ahead and make a generic policy file and put it on there to see if that fixes the problem.


EDIT:

As I posted before, it's looking for a config.pol file, but doesn't actually attempt to access the .bat file. At this point it looks like either a Samba configuration error, or a Windows configuration error.

Got exactly the same prob.
The log file from samba shows nothing, so I think is a windows problem.
The bat file work fine from windows making netlogon browseable.
But windows just do not execute at the start of session.
Please help

Okay... Finally got some more information.

Logged in on a different system. This one has just enough lag that I can read what's going on.

>NET USE * /DELETE
Cannot Find Batch File

(Maps drives as usual)

So, my guess at this point is that the NET USE command is actually disconnecting the \\server\NETLOGON connection. Windows didn't cache the .bat file, so it errors out and just loads up the drives that were mapped manually previously. (I figure to fix that half, just un-map the drives.)

So, any suggestions? My current scripts look like:

NET USE * /DELETE /YES
NET USE F: \\server\share /YES
...etc.

I was thinking maybe something like:

del c:\username.bat
copy \\server\netlogon\scripts\username.bat c:\
c:\username.bat

ok, I think I know:

Samba server has to be a PDC, make the changes to the client like these link shows (see the end, windows client arranges):

http://linuxfocus.org/English/March2...ticle177.shtml

Tomorrow I'll try it and will tell.
Good Luck.

Samba is the PDC, and my systems are already set up that way. The only difference is that I am not using system policy files. (No need at this exact moment. Maybe later.)

Hi, now for me, without config.pol and the changes in smb.conf to be a PDC the logon scripts are working fine.

The clients are w98SE joined to the domain.

But now (always there is a 'but') I've changed the interfaces where samba is listening and got a problem of local master browser:

nmbd/nmbd_nameregister.c:register_name_response(109)
register_name_response: server at IP 172.26.0.2 rejected our name
registration of ADMINISTRACION with error code 6.

172.26.0.2 is a w98 pc who do not work very well cos do not reply to ping's and can't browse its files.

And can't be local master browser, as a result you do not see it in Net Neighbourhood but can access it as \\name_samba_server

Good Luck

The easiest way to get around that is to setup Samba as a WINS Server.

WINS SUPPORT = YES

Just make sure that the IP of the Samba Server is in your dhcpd.conf, or, if you're using static IPs, in your TCP/IP setup. Master Browser is now irrelevant.

Also, if that Win98 system isn't responding to pings when you use the IP address, I would look into possibly a bad network cable or bad NIC.

Thanks, tomorrow I will try the wins support (option netbios-name-servers ip_samba_server in dhcpd.conf, I never used it), but the samba server have been working in another subnet without broadcast problems, all boxes were visible.

I think this little prob of mine is because the crappy w98 is not working well in 172.26.0.2, in this pc you can ping any boxes or browse their files across the network but others can not do the same with it -- do not response to ping's or not let u browse its files--. It surfs the web without problem, and so, it can talk very well with the router. So I think it's not a nic problem, it's a smb-cifs windowze problem.

And what about your logon scripts prob?
Have u tried another boxes w98? Have you added them to the domain?
me its working with samba-server-2.2.8a

Regards

HI I have put wins support = yes in smb.conf
rearrange tcp-ip settings to add the wins server in clients

Still getting this in nmbd.log:

[2004/05/13 11:52:29, 0] nmbd/nmbd_nameregister.c:register_name_response(109)
register_name_response: server at IP 172.26.0.2 rejected our name registration of ADMINISTRACION<1d> with error code 6.
[2004/05/13 11:52:29, 0] nmbd/nmbd_become_lmb.c:become_local_master_fail2(425)
become_local_master_fail2: failed to register name ADMINISTRACION<1d> on subnet 172.26.0.101. Failed to become a local master browser.
[2004/05/13 11:52:29, 0] nmbd/nmbd_namelistdb.c:standard_fail_register(290)
standard_fail_register: Failed to register/refresh name ADMINISTRACION<1d> on subnet 172.26.0.101

The samba server is not seen in nethood by clients w98

but they could access it like \\ip_samba_server

ping 172.26.0.2 give no response
But the other clients w98 can access it in nethood (something get better)

Some ideas Please.