Hello Rauno,
Thank you for your comment in
http://lists.samba.org/archive/samba/2004-January/078040.html
I have the same problem here. It occurs only when accessing a Windows
2000 Server machine. In the lower network layers everything works as
expected. Only SMB has these problems.
For now I
We have the same problem:
And we can find that in our logfiles:
--
log.smbd-[2004/01/07 07:38:52, 0] lib/util_sock.c:get_peer_addr(948)
log.smbd: getpeername failed. Error was Transport endpoint is not connected
--
John H. wrote:
I am having nearly the EXACT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 6 Jan 2004, John H. wrote:
I am having nearly the EXACT same problem as
http://lists.samba.org/archive/samba-technical/2003-December/033315.html
I have samba 3.0.1-1 rpms and fedora core 1.
Please test 3.0.2pre1. If the problem
I am having nearly the EXACT same problem as
http://lists.samba.org/archive/samba-technical/2003-December/033315.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
downgrading to 3.0.0 seems to fix it!(at least from linux, will try from win machines
tomorrow) I will report a bug to bugzilla if it's still there when i try 3.0.2pre1
sometime. I would have never thought to downgrade had I not seen someone else had a
similar problem on this list.
