samba - Nov 2003 - WinXP and Samba

I recently upgraded my laptop from Win2k to WinXP, and now Samba doesn't 
work.  I have two shares on my linux server (red hat 7.2) and under Win2k, 
they worked fine.  Now under XP, I cannot connect to them, I either get an 
"unknown username or bad password" error or "Network Path was not
found"
error.  I did not change the configuration of Samba at all between upgrades. 
  The error messages occur randomly, they change back and forth, with no 
apparent pattern.  Does WinXP not work with Samba anymore? (at one point a 
few months ago I could connect from WinXP) did MS release an "upgrade"
that
stops samba from working as per their threats?


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

I've been experiencing the same problem with Samba and XP.  I've tried
Samba 2.2.4, 2.2.5 and the latest 3.0 alpha and no dice.

Moreover, some XP computers on our network have no problems connecting
to the shares (my XP laptop, for example) but some computers have terrible
problems getting the drive mapped.

For the folks that can't map the drive, if they reboot enough times, 
eventually they can map it (i.e. mapped earlier with "reconnect at
login"),
but it's not guarantee that it will remap the next time they reboot.
>From looking a the log for the computer that is failing, from samba's 
perspective, it looks like the drive is mapped (connect messages in the
log, shows up when you do a smbstatus) but the user gets the one of the 
messages you described below.

Any insight on this?

-----Original Message-----
From: Christensen Tom [mailto:paveraware@hotmail.com]
Sent: Tuesday, July 16, 2002 6:37 PM
To: samba@lists.samba.org
Subject: [Samba] WinXP and Samba




I recently upgraded my laptop from Win2k to WinXP, and now Samba doesn't 
work.  I have two shares on my linux server (red hat 7.2) and under Win2k, 
they worked fine.  Now under XP, I cannot connect to them, I either get an 
"unknown username or bad password" error or "Network Path was not
found"
error.  I did not change the configuration of Samba at all between upgrades.

  The error messages occur randomly, they change back and forth, with no 
apparent pattern.  Does WinXP not work with Samba anymore? (at one point a 
few months ago I could connect from WinXP) did MS release an "upgrade"
that
stops samba from working as per their threats?


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Follow-up.. 

(currently running Samba version 3.0-alpha18)

One interesting thing I saw in the logs for the computer that's having 
a hard time is this:

[2002/07/20 18:38:06, 0] smbd/service.c:make_connection_snum(648)
   is not a directory

Strange that it's printing a blank.  I assume there's supposed to be
something before the "is not a directory"

Also, I see a lot of these messages:

[2002/07/22 06:25:48, 0] lib/charcnv.c:convert_string(147)
  convert_string: Required 35, available 16

I'll try to get a complete session of the bad computer trying to log 
on today and post that as an additional follow-up.

Thanks,

Eric

-----Original Message-----
From: Ladner, Eric (Eric.Ladner) 
Sent: Monday, July 22, 2002 8:41 AM
To: 'Christensen Tom'; samba@lists.samba.org
Subject: RE: [Samba] WinXP and Samba



I've been experiencing the same problem with Samba and XP.  I've tried
Samba 2.2.4, 2.2.5 and the latest 3.0 alpha and no dice.

Moreover, some XP computers on our network have no problems connecting
to the shares (my XP laptop, for example) but some computers have terrible
problems getting the drive mapped.

For the folks that can't map the drive, if they reboot enough times, 
eventually they can map it (i.e. mapped earlier with "reconnect at
login"),
but it's not guarantee that it will remap the next time they reboot.
>From looking a the log for the computer that is failing, from samba's 
perspective, it looks like the drive is mapped (connect messages in the
log, shows up when you do a smbstatus) but the user gets the one of the 
messages you described below.

Any insight on this?

-----Original Message-----
From: Christensen Tom [mailto:paveraware@hotmail.com]
Sent: Tuesday, July 16, 2002 6:37 PM
To: samba@lists.samba.org
Subject: [Samba] WinXP and Samba




I recently upgraded my laptop from Win2k to WinXP, and now Samba doesn't 
work.  I have two shares on my linux server (red hat 7.2) and under Win2k, 
they worked fine.  Now under XP, I cannot connect to them, I either get an 
"unknown username or bad password" error or "Network Path was not
found"
error.  I did not change the configuration of Samba at all between upgrades.

  The error messages occur randomly, they change back and forth, with no 
apparent pattern.  Does WinXP not work with Samba anymore? (at one point a 
few months ago I could connect from WinXP) did MS release an "upgrade"
that
stops samba from working as per their threats?


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx


-- 
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

After searching the archives here and at MS, have been unable to find a
solution to this issue.
When browsing the network using WinXP explorer,  the network is clobbered by
its search for
desktop.ini files for each folder.  I have 2 Samba servers (1 running 2.2.7
and 1 running 3.0.0).
Everything works OK except for a slight delay in the initial directory
display.  When I looked at the network
traffic using ethereal, there is a "desktop.ini file not found" error
for
every folder.  It repeats for each folder as
I tree down.  Has anyone ran across this and found a way to resolve it?