Re: Home Network with Suse 9.3!

From: Jeff (jeff_at_naol.com)
Date: 09/11/05


Date: Sat, 10 Sep 2005 20:39:42 -0400


"ac" <"aec$news"@candt.demon.co.uk> wrote in message
news:3oh1ibF5t6r3U1@individual.net...
> Jeff wrote:
>> "David Speight" <dsp8@comcast.net> wrote in message
>> news:KoOdnS5SQcJvSb_eRVn-3g@comcast.com...
>>> AJP wrote:
>>>
>>>> I have four PC's here at Home. My main one is running Suse 9.3. Another
>>>> one Ubuntu (Hoary Hedgehog), one Windows XP Pro and another one Windows
>>>> XP
>>>> x64. All are connected to a netgear switch (which is connected to my
>>>> cable
>>>> modem. All can access the internet.
>>>>
>>>> What I want to do is create a small home network to share files and the
>>>> printer.
>>>>
>>>> I am new to networking under linux, and tried to google a good step by
>>>> step guide to set up such a network, but didn't find any.
>>>>
>>>> If anyone could point me in the right direction I would be most
>>>> grateful.
>>>>
>>>> Best regards,
>>>>
>>>> Alex
>>> Try using samba (smb).
>>> I share files and printers between SuSE 9.2 & W2k machines.
>>
>> I'm at the same point. My wireless home lan consists of 2 desktops
>> running XP, a laptop running XP and one laptop running Suse 9.3.
>>
>> I read the Suse help and then using YaST I went to configure Samba
>> Client. The only entry for Samba Workgroup is "TUX-NET".
>
> afaik you should be able to change the workgroup name to MSHOME with no
> problem, I can.
>
> I suggest that it is not the best idea anyway to use have the existing
> workgroup under the M$ default name, I chose another one (all PCs of
> course).
>
> After the changes which should work in yast the most you might need to do
> is stop and re-start samba (say, restart the user session at most?) I
> would think.
>
>> Since my home lan was setup in Windows they are in a "MSHOME" workgroup.
>> I assume I need to change the workgroup name to MSHOME to see the other
>> computers in the lan,
>
> yes I think so
>
>> however YaST will not let me enter anything in that field
>
> Which field?

The field that has "TUX-NET" in it. I can select it by double clicking, but
nothing I tgype with the keyboard appears to replace it.

> yast, samba client, membership domain or workgroup (change field),
> (finish)
> similar for the samba server I think. I cannot understand why you woul
> dnot be able to enter another workgroup name. It is possible to have more
> than one workgroup in a lan (I have not done this), and have a PC to be a
> member of more than one workgroup also I think.
>
>> even though I had to enter my Administrator password to get this screen
>> to open. Is this normal or a keyboard misconfiguration or something
>> else?
>
> If you are using yast, network services then I think it is certainly not
> normal, something seems wrong.

That is what I think too, but because I am new to Linux I did not know if it
was something I am doing or the installation. Also, being a newbie I do not
know how to find out why that is happening or what the problem is.

>> Funny thing is that if I log off the session, and relogin as root and
>> then reach the same YaST screen, it will permit me to type data in that
>> field. Same thing happened when I was configuring my network adapters.
>
> When you boot up, do you have to login as the normal user, or are you
> using the default installation of 'auto-login' ?

I do not auto-login. I created a normal user and I login with that
password. It is very frustrating n ot to be able to type in what I want. If
I give up, logout of the session and re-login as root, evedrything works
fine and I can enter wshatever I type in any field including that one.

> I found some strange and inconvenient things with yast on versions
> preceeding 9.3 unless I set suse up for user initial login. I have not
> tried with 9.3. I prefer the marginally better security with user login
> anyway.
>
>> Would appreciate some advice about why this is happening or if I am doing
>> something wrong.
>> Thanks
>> Jeff
>
> btw if you are having peculiarities with samba etc then I found that
> webmin was really good, and I could solve a lot of questions using it.
> (also see other postings in this thread)

I'll look into using webmin. But the above keyboard entry problem has
happened to me also when, again in YaST, I tried to enter the ESSID name for
my home network. It just would not let me enter anything for ESSID unless I
logged out of YaST and the session as normal user and then re-login as root.
This is in Suse 9.3 eval which I downloaded from the Novell website.

When you are a newbie you just do not know if it is something you are doing
wrong or the system that is not working right.

Jeff



Relevant Pages

  • Re: Home Network with Suse 9.3!
    ... a laptop running XP and one laptop running Suse 9.3. ... > I read the Suse help and then using YaST I went to configure Samba Client. ... afaik you should be able to change the workgroup name to MSHOME with no ...
    (alt.os.linux.suse)
  • Re: Home Network with Suse 9.3!
    ... >> afaik you should be able to change the workgroup name to MSHOME with no ... >> After the changes which should work in yast the most you might need to do ... samba client: ... > This is in Suse 9.3 eval which I downloaded from the Novell website. ...
    (alt.os.linux.suse)
  • Re: script to disjoing/rejoin domain
    ... be able to take it to workgroup and then rejoin domain for now ... Machines shouldn't just be 'falling off the domain' without reason. ... By default a normal user can join 10 machines to a domain. ...
    (microsoft.public.windows.server.general)
  • Re: script to disjoing/rejoin domain
    ... This posting is provided "AS IS" with no warranties, and confers no rights. ... only reply to Newsgroups ... to take it to workgroup and then rejoin domain for now without calling ... By default a normal user can join 10 machines to a domain. ...
    (microsoft.public.windows.server.general)
  • Re: script to disjoing/rejoin domain
    ... Windows Server - Directory Services ... By default a normal user can join 10 machines to a domain. ... To remove a computer form the domain you need a local admin account to bring the computer to a workgroup. ...
    (microsoft.public.windows.server.general)