Hi folks, My client and I are having a problem getting a portable Esaote ultrasound machine to connect to a Samba server. The unit has an integrated laptop with a Windows XP version that can hardly be modified. Upon delivery the vendor only changed the user name and workgroup for us. When I asked for the user password to make a matching Samba account, the vendor refused because they use a key on a USB stick for that. They said to fill in a name and password for the server every time we needed to access the Windows share. So far I've experimented with the Samba "map to guest" and "guest account" options, which should work, but I'd really like to see this machine connect to the Samba server in the usual fashion. Does anyone have any suggestions? Any workarounds, or hacks that I might try? Thanks, Jaap
Hello Jaap, On Fri, May 18, 2012 at 08:06:22PM +0200, Jaap Winius wrote:> Hi folks, > > My client and I are having a problem getting a portable Esaote > ultrasound machine to connect to a Samba server. The unit has an > integrated laptop with a Windows XP version that can hardly be > modified. Upon delivery the vendor only changed the user name and > workgroup for us. When I asked for the user password to make a > matching Samba account, the vendor refused because they use a key on > a USB stick for that. They said to fill in a name and password for > the server every time we needed to access the Windows share. > > So far I've experimented with the Samba "map to guest" and "guest > account" options, which should work, but I'd really like to see this > machine connect to the Samba server in the usual fashion. > > Does anyone have any suggestions? Any workarounds, or hacks that I might try? > > Thanks, > > Jaap > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/sambaWhat do you mean with ``connect to the Samba server in the usual fashion''? I guess you want the XP client to be a member of the samba domain. Isn't it? For that, you need to have the rights on the XP client to make it a member of the samba domain (usually admin rights). Without these rights, it will be extremely hard to achieve your goal(s). -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy ************************************* W.K. Offermans
On 5/18/2012 11:06 AM, Jaap Winius wrote:> Hi folks, > > My client and I are having a problem getting a portable Esaote > ultrasound machine to connect to a Samba server. The unit has an > integrated laptop with a Windows XP version that can hardly be modified. > Upon delivery the vendor only changed the user name and workgroup for > us. When I asked for the user password to make a matching Samba account, > the vendor refused because they use a key on a USB stick for that. They > said to fill in a name and password for the server every time we needed > to access the Windows share. > > So far I've experimented with the Samba "map to guest" and "guest > account" options, which should work, but I'd really like to see this > machine connect to the Samba server in the usual fashion. > > Does anyone have any suggestions? Any workarounds, or hacks that I might > try? > > Thanks, > > JaapIsn't there a check box on windows for mapping a network drive "Connect using different credentials"? Then every time the machine tries connecting to the share it should be using the credentials provided for the mapped drive. Another option would be to reset the administrator password on the XP machine, google: "ntpasswd". As for samba tricks, give the machine a static IP or a reserved IP and allow write access from only that IP?
Quoting Willy Offermans <Willy at Offermans.Rompen.nl>:> What do you mean with ``connect to the Samba server > in the usual fashion''?Sorry for not being more specific. By "the usual fashion" I meant using smbpasswd to make an account on the server that has the same name, password and workgroup as on the workstation. Quoting Jaap Winius <jwinius at umrk.nl>:> ... They said to fill in a name and password for the server every > time we needed to access the Windows share.Luckily, this description is not accurate. I eventually discovered that I could map a network drive by making use of the "Connect using a different user name" option. It's stupid, but I thought Samba didn't support this and that it was always necessary to have a Samba account with the same name and password combination as the user's Windows account. That's simply not true. My wrong impression, formed many years ago, was based on that option's single limitation: it doesn't work when the user name of the Windows account is the same and only the password is different. It really does require that you "Connect using a different user name". Doh! Quoting Jorell <JorellF at fastmail.net>:> Isn't there a check box on windows for mapping a network drive > "Connect using different credentials"?This would have led me to the solution if I hadn't thought of it myself. Thanks very much!> As for samba tricks, give the machine a static IP or a reserved > IP and allow write access from only that IP?Already taken care of. Quoting Moray Henderson <Moray.Henderson at ict-software.org>:> If you have access to the command prompt or the ability to create batch > files, you could try "net use" commands.Good idea, but it looks like Esaote made sure those options are not available. Thanks for all your support! Cheers, Jaap