Hi everyone!  I am trying to help some missionaries in Africa out with
trying to get Samba up and running.  However, we have run into a small road
block.  They are running FC2 and Samba 3.?.  We have a basic Samba system up
and running in a Windows workgroup envionment and things work fine with the
Windows "workgroup" PCs accessing a Samba share.  However, that only seems
to work as long as the Windows PCs are in the same workgroup as the Samba
server.

Here is the problem.  Sometime they have people come into their office from
the field with a laptop (running Win2k Pro or XP) that is setup to connect
to a domain (in THEIR home office).  When they get to "our" office we need
to let them have access to one or two shares on the Samba server.  When they
try to access the Samba shares all they get is the Windows username and
password screen over and over again!

I created a Linux AND a Samba user for them with the same name as their
Windows user id and password but that didn't work eather.  Anyone have any
other ideas?  Here is a little more info:

Workgroup (PCs and Samba server) = wrkgrp
(Visiting) laptop domain = abc.net

Thanks for any and all help.

Lamar

[ Post a follow-up to this message ]

On Wed, 11 Aug 2004 01:28:00 GMT,
"Lamar Thomas" <none@none.com> posted:

> Hi everyone!  I am trying to help some missionaries in Africa out with
> trying to get Samba up and running.  However, we have run into a small roa
d
> block.  They are running FC2 and Samba 3.?.  We have a basic Samba system 
up
> and running in a Windows workgroup envionment and things work fine with th
e
> Windows "workgroup" PCs accessing a Samba share.  However, that only seems
> to work as long as the Windows PCs are in the same workgroup as the Samba
> server.
>
> Here is the problem.  Sometime they have people come into their office fro
m
> the field with a laptop (running Win2k Pro or XP) that is setup to connect
> to a domain (in THEIR home office).  When they get to "our" office we need
> to let them have access to one or two shares on the Samba server.  When th
ey
> try to access the Samba shares all they get is the Windows username and
> password screen over and over again!
>
> I created a Linux AND a Samba user for them with the same name as their
> Windows user id and password but that didn't work eather.  Anyone have any
> other ideas?  Here is a little more info:
>
> Workgroup (PCs and Samba server) = wrkgrp
> (Visiting) laptop domain = abc.net

I suppose you could make your workgroup as "WORKGROUP", the default setting
on many Windows PCs, and that'd match many of the visitors.  But what's
probably easiest is to set up your own DHCP server and have it
automatically configure visiting computers to suit your network.  You might
even want to set up your system to work as a WINS server.  (Replacing all
the servers that they might have on their network, so everything they
expect is also on yours - DNS, DHCP & WINS).

I'm not familiar with Win2000 or XP to offer explicit advice on pandering
to their foibles, though.  I've done that sort of thing with Windows 95 and
98 PCs, so they can just plug in and join the network automatically.

--
If you insist on e-mailing me, use the reply-to address (it's real but
temporary).  But please reply to the group, like you're supposed to.

This message was sent without a virus, please delete some files yourself.

[ Post a follow-up to this message ]

Lamar Thomas wrote:
> Hi everyone!  I am trying to help some missionaries in Africa out with
> trying to get Samba up and running.  However, we have run into a small roa
d
> block.  They are running FC2 and Samba 3.?.  We have a basic Samba system 
up
> and running in a Windows workgroup envionment and things work fine with th
e
> Windows "workgroup" PCs accessing a Samba share.  However, that only seems
> to work as long as the Windows PCs are in the same workgroup as the Samba
> server.
>
> Here is the problem.  Sometime they have people come into their office fro
m
> the field with a laptop (running Win2k Pro or XP) that is setup to connect
> to a domain (in THEIR home office).  When they get to "our" office we need
> to let them have access to one or two shares on the Samba server.  When th
ey
> try to access the Samba shares all they get is the Windows username and
> password screen over and over again!
>
> I created a Linux AND a Samba user for them with the same name as their
> Windows user id and password but that didn't work eather.  Anyone have any
> other ideas?  Here is a little more info:
>
> Workgroup (PCs and Samba server) = wrkgrp
> (Visiting) laptop domain = abc.net
>
> Thanks for any and all help.
>
> Lamar
>
>

I have several Samba server running in a windows environment and can
connect to Samba shares without any problem whether the Windows (2000,
XP) clients are in the same workgroup or not. The laptops should be able
to see all workgroups in My Network Places->Entire Network->Microsoft
Windows Network->[workgroup-name]. Check your smb.conf and make sure
your shares allow either public access or that your users are typing the
correct samba-user/password combo to allow access. You can also try to
connect from the run bar as \\server\share.

...kurt

[ Post a follow-up to this message ]

On Sun, 30 Jan 2005 21:17:36 -0800, kurt wrote:

> Lamar Thomas wrote: 
>
> I have several Samba server running in a windows environment and can
> connect to Samba shares without any problem whether the Windows (2000,
> XP) clients are in the same workgroup or not. The laptops should be able
> to see all workgroups in My Network Places->Entire Network->Microsoft
> Windows Network->[workgroup-name]. Check your smb.conf and make sure
> your shares allow either public access or that your users are typing the
> correct samba-user/password combo to allow access. You can also try to
> connect from the run bar as \\server\share.
>
> ...kurt


Hi

Sometimes when I try and connect guest PC's to my network I get the same
problem, seems that Samba does not want to authorise them. The work around
I use is to map a network drive to the resource I need to use but rather
than using server name I use the server addres 10.0.0.x and I use the full
user name in the connect as another user client\username rather than just
the username. This works for me everytime I get the problems you are. Try
it.

Good Luck Dave

[ Post a follow-up to this message ]

If you are trying to Browse from NT or Windows 2000, remember to smbpasswd
the user you are trying to connect.
i.e.
adduser joe
passwd joe
then
smbpasswd joe

or depending the version of Linux, and if users already setup in Linux.
cat /etc/passwd | mksmbpasswd.sh > /etc/smbpasswd

I had this problem when running Win 2000/XP users.

Regards
Leigh

"kurt" <kurtl@olypen.com> wrote in message
news:10vrfrhgsbartf9@corp.supernews.com...
> Lamar Thomas wrote: 
road[vbcol=seagreen] 
system up[vbcol=seagreen] 
the[vbcol=seagreen] 
seems[vbcol=seagreen] 
Samba[vbcol=seagreen] 
from[vbcol=seagreen] 
connect[vbcol=seagreen] 
need[vbcol=seagreen] 
they[vbcol=seagreen] 
any[vbcol=seagreen] 
>
> I have several Samba server running in a windows environment and can
> connect to Samba shares without any problem whether the Windows (2000,
> XP) clients are in the same workgroup or not. The laptops should be able
> to see all workgroups in My Network Places->Entire Network->Microsoft
> Windows Network->[workgroup-name]. Check your smb.conf and make sure
> your shares allow either public access or that your users are typing the
> correct samba-user/password combo to allow access. You can also try to
> connect from the run bar as \\server\share.
>
> ...kurt

[ Post a follow-up to this message ]