Re: Accessing a Windows Network
From: Malke (malke_at_nospoon.com)
Date: 01/11/05
- Next message: houghi: "Re: SUSE-Linux-9.2-mini-installation.iso"
- Previous message: Ruel Smith: "Re: Software updates via YOU?"
- In reply to: apollo2011: "Re: Accessing a Windows Network"
- Next in thread: Kevin Nathan: "Re: Accessing a Windows Network"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 10 Jan 2005 18:41:31 -0800
apollo2011 wrote:
Hi, Apollo. See my comments inline:
> Is there anyway to do it without creating identical users? That seems
> inefficient and un-Linux somehow...
This is the way a Workgroup on Windows works with guest disabled (the
right way, the Linux and grownup os's way). You don't have to create
identical local users if you have a domain with a server os because the
authentication is done on the server. If you have a peer-to-peer
network (called a "Workgroup" in Windows), user authentication has to
happen on the local level. So yes, you have to create identical user
accounts/passwords on all machines if you want those users to be able
to get resources. The authentication is for each user on the local
machine. Think about it - there has to be a way for the machine being
asked to allow access to its resources to know whether the request is
coming from someone who is allowed to do that on that machine.
>
> I installed the Samba Server, I previously only had the client but all
> I really need to do right now is access my other machines from Linux
> (although vice versa would be nice ;-)
I always install both because that way I can get files from whatever
machine I want from wherever I happen to be working.
>
> You suggested the Workgroup to be TUX-NET, but shouldn't the workgroup
> match that of all the other machines I am trying to see from in Linux?
No, I didn't suggest you name your Workgroup "TUX-NET"; I said that is
the default in the Samba configuration on SuSE. Rename the Workgroup to
match your real Windows Workgroup name. Windows doesn't need all the
machines to be in the same Workgroup, but it's neater that way.
>
> I also believe that NetBIOS not being enabled in Windows could be a
> problem because I am quite sure that that is not enabled on any of my
> machines.
So it's easy to do. See my previous post.
>
> The question that I keep wondering, is 'Why does Linux need to have a
> username and password to access the shares. On Windows-Windows
> network, you do not need to have a log on on every machine to access
> the shares on that machine, so why in Linux, do you need to have a
> username and password for the other machine?
See my answer to this question in the first paragraph. You actually *do*
have to have a user account and password Windows-Windows; because most
home users have XP Home they just don't realize they have an account
and the password is usually blank. Blank passwords can cause networking
problems Windows-Windows, so all security issues aside, it's a good
idea to assign passwords. Because Windows XP Home uses something called
"forceguest", the Guest account is enabled and you can't change this. A
Guest account is not meant to be used for when you are being
hospitable ;-) and in well-secured systems it is always disabled. Guest
is disabled by default in Windows 2000 and *nix systems, for example.
>
> The other thing I need to know is how to add specific ports to the
> firewall, I looked at the Firewall control panel in YaST and cant see
> anyway to say Always allow 192.168.1.100-192.168.1.105 (my network IP
> range).
>
I'll let someone else answer your question about the SuSE firewall
because I don't have it set up right now since I'm using something
else, but I'm sure there is a way. As a general firewall rule, you
don't want to open ports per se, but rather to enter your lan as
Trusted. So your lan range would be 192.168.1.0-192.168.1.254.
HTH,
Malke
-- "I have a cunning plan..."
- Next message: houghi: "Re: SUSE-Linux-9.2-mini-installation.iso"
- Previous message: Ruel Smith: "Re: Software updates via YOU?"
- In reply to: apollo2011: "Re: Accessing a Windows Network"
- Next in thread: Kevin Nathan: "Re: Accessing a Windows Network"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
