[Samba] different win machines on PDC not accessible at diffe
rent times
Rauno Tuul
rauno.tuul at haigekassa.ee
Wed Jan 7 10:27:41 GMT 2004
This problem is something about SAMBA smbd.
It doesn't matter whether samba runs also as WINS server.
I wrote earlier:
http://lists.samba.org/archive/samba/2003-December/077722.html
My networks WINS server is WINDOWS 2000, not samba.
I had both my PDC and BDC upgraded to 3.0.1 once. The errors accessing W2K
workstation went away after downgrading both samba servers to 3.0.0. Even
BDC can cause these errors.
hopefully this helps someone...
Rauno Tuul
> -----Original Message-----
> From: John H. [mailto:mrmailer at myway.com]
>
>
> I am having nearly the EXACT same problem as
> http://lists.samba.org/archive/samba-technical/2003-December/0
33315.html
>
> I have samba 3.0.1-1 rpms and fedora core 1.
>
> Samba is set as a WINS server, which the win2k machines, who
> use DHCP from router, are pointed to by the WINS server
> address specified in router(each of the win2k machines, via
> ipconfig /all reveal they do in fact use the wins server).
>
> At different times, and different machines, the win2k clients
> get one of the two errors...
> "\\computer not accessible. the system cannot find message
> text for message number 0x%1 in the message file for %2"
>
> or
>
> "\\computer is not accessible
> an internal windows 2000 error occurred"
>
> while these unaccessible computers generate this message, if
> i try from the linux machine for the same \\machine, i get
> session setup failed: NT code 0xf90a8141
> via smbclient -L \\machine -U user
>
> later, it is accessible. it keeps going on and off. I was
> told this may be fixed if I install netbeui protocol on all
> win2k machines? This is a pretty annoying problem, and I've
> checked and checked my config, but have found no solution in
> it or on the internet. My smb.conf is attached. Any
> help would be appreciated.
More information about the samba
mailing list