Windows Clientes with samba PDC
 

I have machines clients with Windows 98/ME in my network, and when i try to open files in the pub dir in server, using windows explorer the client machines hangs.

I hate it when that sort of thing happens. Good luck with finding a solution. Maybe if you post your smb.conf and a little more info then people will be able to help you.

When the client machine hangs with the blue screen the message is something about a vserver.

Here is my conf file:

[global]

workgroup = grupo
server string = samba server
printcap name = /etc/printcap
load printers = yes
printing = cups
log file = /var/log/samba/%m.log
max log size = 0
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
unix password sync = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
pam password change = yes
obey pam restrictions = yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

os level = 33

domain master = yes

preferred master = yes

domain logons = yes

logon script = %U.bat

username map = /etc/samba/smbusers
dns proxy = no
case sensitive = no

#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writeable = yes
valid users = %S
create mode = 0664
directory mode = 0775




[netlogon]
comment = Network Logon Service
path = /home/netlogon
guest ok = yes
writable = no
share modes = no



[Profiles]
path = /home/profiles
browseable = no
guest ok = yes


[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
printable = yes



[pub]
path = /pub
public = yes
writeable = yes
create mode = 0777
directory mode = 0777
create mask = 0777

shares and vserver
 

Try making the share browseable in your smb.conf file and make sure that you have all of the updates for your Windows ver. install (there is no fun like installing updates from M$). I think I had vserver errors before (it's been a couple of years) and the solution was to get the latest service packs from M$....

Have you tried to attach to the shares from a DOS window? It might be a browser issue.