Re: Connecting and authentication on server

Malke wrote:

Tony Kidd wrote:

OK
I've set up my samba server. Everything went fine until I fired up the
winXP machine. I should start by saying I know nothing about
windows-even less than I know about linux. I have 2 machines the
server (SUSE linux running samba-don't worry I know how to use this
one. Just assume it's running XP server)

Anyway the samba server works. I have been able to connect to shares
and printers. The problem is when I wanted to authenticate from the
server. I set up the smbpassd file etc and went to the windows
machine. I set the "domain" and tried to log on. When I did it told
me:

The following error occurred attempting to join the domain "fedora":

Multiple connections to a server or shared resurce by the same user,
using more than one user name, are not allowed. Disconnect all previus
connections to the server or shared resource and try again...

OK, fair enough but (finally the question):

how do I disconnect from the server? I can't turn off file sharing or
the server coz I won't be able to re-connect. When I fire up the
windows machine it automatically connects. This is a pretty simple
question i know but can't find the answer. Anyone help? Please?


OK, I think you've set up your Samba server incorrectly. From your
description, there is no reason to be emulating a Windows domain.
Usually you would only be involved with the Samba domain settings when
you want your Linux box to join a Windows Server domain. What does
Fedora have to do with this? I thought you only have two machines: a
Windows XP one and a SUSE (which version please?).

Here is my standard blurb on setting up Samba. Doing it this way works
perfectly on both my small network of 5 XP boxen, 1 Win2k box, and 2
SUSE 10.1 machines. I've also used this successfully when setting up a
Samba server for a school laptop program (~170 laptops and a Samba
server running SUSE 9.3).

1. On Windows boxen, make sure all accounts are properly named (no
damned spaces) and there are no null passwords. Configure any firewalls
to allow lan traffic. Create shares as desired. Note that if any boxen
are XP Pro, you should disable Simple Sharing (Folder Options>View).

2. On SUSE, create identical user account/passwords with YaST.
3. Make sure you've installed Samba server/client with YaST.
4. Using YaST System Services (Runlevel), make sure nmb and smb daemons
will start at bootup.

5. Now add your users to Samba. Make these match the ones on Windows. I
think the easiest way is from the console, so open one, su to root, and
type:
smbpasswd -a username [enter]
(enter password)
(enter password again)

6. Go to YaST and under Network Services set your Samba server and
client Identity to match your Windows Workgroup name.

(Perhaps this is where you went wrong - you do *not* want to set SUSE to
be the domain controller - you have no domain.)

7. I use KDE, so if you use Gnome or another window manager you'll need
to figure this next bit out yourself. Open up the Control Center and go
to Internet/Network and then Samba. Click on the Administrator Mode
(enter root password). I use User security level. Check to make sure
Shares (these are for the SUSE box of course) are the way you want
them. Apply and close that part.

8. Click on File Sharing and enable Administrator Mode. Check "Enable
local network file sharing". I have mine set on "Advanced sharing".
Check the box for "Use Samba" rather than NFS.

And that's pretty much it. Now if you want to make a new share - say a
folder that isn't in your /home, you can right-click it to set Sharing
Properties. If all you want to share is your /home, you're done. Since
9.3, SUSE has a useful Network icon on the desktop (at least in KDE it
does) where you can find your Windows Workgroup and see all the smb
shares.

Malke

Thanx Malke, that got me started again. I was able to follow your
instructions and get it working.

Let me clear up one thing-I'm using suse 10. What I want to do is use that
as a server and use the windoze machines as clients. I've now done that
with your help-thanx a billion.

let me clear up the fedora thing as well. That's the name of my server-it's
not running fedora. It's named after Roger coz he's a good server.

The key to fixing it was disabling "simple sharing"-didn't know anything
about this.

Anyway, Thanx again. Now I have to set up email....


.

Relevant Pages

  • Re: Fileserver question
    ... >> another box running both 9.0 and Windows. ... >> computers in the same room and connected to a router. ... otherwise you will need to run a DHCP server on one ... > of the machines, preferably the server, or give both machines static ...
    (alt.os.linux.suse)
  • nslookup times out on some WinXP clients
    ... Basically, nslookup times out on some Windows machines, but not on others. ... we currently have a Windows 2000 Server DNS & DHCP Server serving IP ...
    (RedHat)
  • Re: New: LanMan98 V2 Not connecting
    ... all) Windows machines, the computer name as found in the system ... essentially Windows was rejecting the connection because it hadn't ... LanMan98 appears to be one, ... uses a low-level message protocol called SMB (Server Message Block). ...
    (comp.sys.acorn.networking)
  • Re: DST Updates - fun, fun
    ... Most XP machines received the daylight savingtimeupdate ... thesystemtimeis jumping ahead an additional ... all Windows XP, sp2 computers have been patched and verified. ... all Windows 2003 Server machines ...
    (microsoft.public.windowsxp.general)
  • Re: DST Updates - fun, fun
    ... Most XP machines received the daylight savingtimeupdate ... all Windows XP, sp2 computers have been patched and verified. ... all Windows 2003 Server machines ... All patches applied. ...
    (microsoft.public.windowsxp.general)
Loading