Can't connect from Windows 2000

[jennyw]

Yes, I found this on the Web also, and it works. I still have no idea what
the original problem was. It just kind of went away yesterday.  Weird. The
thing is, I've seen it reported by others, just no answers (except for the
one that involves changing the code which kind of scared me off).

Thanks!

Jen

----- Original Message -----
From: "Barker, Brian W." <BRIAN.W.BARKER at saic.com>
To: "'jennyw'" <jennyw at dangerousideas.com>; "Ahmad Yahya"
<getlucky at telkom.net>; <samba at lists.samba.org>
Sent: Monday, December 03, 2001 1:44 PM
Subject: RE: Can't connect from Windows 2000


> If my memory is correct, I got this message awhile back (others
> have seen this message also). I had changed from Win95 (which was
> working) to Win2000, Samba stopped working and I got your message.
> I had to add:
>
> encrypt passwords = yes
>
> to smb.conf and then also run:
>
> smbpasswd...
>
> on my Unix machine, then set up the same username and password
> on my Unix machine and my Win2000 machine. I still can't get it
> to work for both the Win95 and Win2000 machines at the same time...
>
> Brian W. Barker
> SAIC
> Rosslyn, VA
>
> -----Original Message-----
> From: jennyw [mailto:jennyw at dangerousideas.com]
> Sent: Monday, December 03, 2001 3:56 PM
> To: Ahmad Yahya; samba at lists.samba.org
> Subject: Re: Can't connect from Windows 2000
>
>
> Thanks. I can ping back and forth. Mysteriously I'm now getting a
different
> message:
>
> >From Windows:
>
> The account is not authorized to log in from this station.
>
> This is even though I have in smb.conf:
>
> hosts allow = 192.168.1.
>
> Which should allow the whole subnet.
>
> Thanks!
>
> Jen
> ----- Original Message -----
> From: "Ahmad Yahya" <getlucky at telkom.net>
> To: <samba at lists.samba.org>
> Sent: Sunday, December 02, 2001 10:23 PM
> Subject: Re: Can't connect from Windows 2000
>
>
> > Fisrt, I am not using Woody or Debian.
> > May be you need to rejoin to Samba.
> > Or check the connection, usually using 'ping' from both Samba/Woody and
> w2k.
> >
> >     hth
> >     yaya
> >
> > From: "jennyw" <jennyw at dangerousideas.com>
> >
> > > Does anyone have any ideas on this?  I've been trying everything I can
> > think
> > > of but I can get no further ...
> > >
> > > Thanks!
> > >
> > > Jen
> > >
> > > ----- Original Message -----
> > > From: "jennyw" <jennyw at dangerousideas.com>
> > > To: <samba at lists.samba.org>
> > > Sent: Wednesday, November 28, 2001 6:36 PM
> > > Subject: Can't connect from Windows 2000
> > >
> > >
> > > > I recently upgraded my Linux install (Debian potato to woody) and
now
> > > Samba
> > > > is no longer  playing nice with Windows 2000. I can use smbclient on
> the
> > > > samba machine to connect to itself,  so at least that's working. The
> > error
> > > > from Windows is: "The semaphore timeout period has expired.".
> > > >
> > > > I deleted the smb.log file at one point in an effort to reset it.  I
> > > figured
> > > > it'd be created again but I haven't seen it ... This is even after
> > > removing
> > > > and re-installing Samba.  How do I get this back?  There are files
in
> > > > /var/log/samba, though, for smbd and nmbd.log. The file log.smbd
> > contains
> > > > these errors which might be related to the problem:
> > > >
> > > > [2001/11/28 10:41:03, 0] lib/util_sock.c:read_socket_data(478)
> > > >   read_socket_data: recv failure for 4. Error = Connection reset by
> peer
> > > > [2001/11/28 10:44:18, 0] lib/util_sock.c:read_socket_data(478)
> > > >   read_socket_data: recv failure for 4. Error = Connection reset by
> peer
> > > > [2001/11/28 10:44:27, 0] lib/util_sock.c:read_socket_data(478)
> > > >   read_socket_data: recv failure for 4. Error = Connection reset by
> peer
> > > > [2001/11/28 10:48:33, 0] lib/util_sock.c:read_socket_data(478)
> > > >   read_socket_data: recv failure for 4. Error = Connection reset by
> peer
> > > > [2001/11/28 10:48:43, 0] lib/util_sock.c:read_socket_data(478)
> > > >   read_socket_data: recv failure for 4. Error = Connection reset by
> peer
> > > >
> > > > I did a Web search for this problem and came across several posts
from
> > > folks
> > > > who have experienced the same problem, but only one solution. I'm a
> bit
> > > > hesitant to implement that solution because it involves changing the
> > > source
> > > > code. I'm not even sure the source file is part of samba (in fact,
the
> > > file
> > > > isn't on my system).  The fix is  documented at:
> > > >
> > > > http://ptolemy.eecs.berkeley.edu/~cxh/sapub/samba.html
> > > >
> > > > so if anyone has an opinion on it I'd like to hear it!
> > > >
> > > > Ideally, though, there's a solution that doesn't involve changing
> code.
> > > Any
> > > > suggestions?
> > > >
> > > > Thanks!
> > > >
> > > > Jen
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > To unsubscribe from this list go to the following URL and read the
> > > > instructions:  http://lists.samba.org/mailman/listinfo/samba
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > To unsubscribe from this list go to the following URL and read the
> > > instructions:  http://lists.samba.org/mailman/listinfo/samba
> >
> >
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  http://lists.samba.org/mailman/listinfo/samba
> >
> >
> >
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>
>
>