Wolfgang Riedmann
2004-May-21 07:08 UTC
[Samba] Windows XP machine not connecting to Samba 3.04
Hi, after the installation of Samba 3.04 (upgrade from 3.02) a single XP notebook cannot connect to any share. The log shows these messages: [2004/05/17 11:48:18, 0] lib/util_sock.c:read_socket_data(367) read_socket_data: recv failure for 4. Error = Connection reset by peer [2004/05/17 11:48:18, 1] smbd/service.c:close_cnum(801) andreasxp (192.168.1.102) closed connection to service wolfgang [2004/05/17 11:48:18, 1] smbd/service.c:close_cnum(801) andreasxp (192.168.1.102) closed connection to service Daten [2004/05/17 11:50:46, 0] lib/substitute.c:alloc_sub_basic(505) alloc_sub_basic: NULL source string! This should not happen As far as I have understand the problem is on the client site, but there seems to be something on the samba side because before the upgrade the client could connect without any problem. In the same network there are other Windows machines (Win98, W2K, XP), all with the latest updates from Windows Update loaded. This client can connect fine to another Samba server (2.2.8a) in the same network (really it's a VMware virtual machine with Debian 8 on my W2K notebook). Can anyone point me in the direction where to seek? I have full access to the notebook and can do any configuration changes. The notebook is _not_ a part of the Samba owned NT domain (as the normal PCs are). Thank you very much for any help! Wolfgang -- -- Wolfgang Riedmann -- Individuelle EDV-L?sungen - Soluzioni informatiche personalizzate -- I-39012 Meran, V. Laurin-Str. 2d -- http://www.riedmann.it - wolfgang@riedmann.it
Maybe Matching Threads
- Re: Windows XP machine not connecting to Samba 3.04 after upgrade
- cannot access umlaut file names with Samba3
- Samba 3.2.4, Win 2008 AD require domain name for auth.
- clients that are not a part of the domain cannot authenticate
- Migrating from VMWare Workstation