Re: Accessing a Windows Network
From: ac (aecnews_at_candt.demon.co.uk)
Date: 01/09/05
- Next message: Michael Heiming: "Stats alt.os.linux.suse (last 7 days)"
- Previous message: Kevin Nathan: "Re: Accessing a Windows Network"
- In reply to: Kevin Sutherland: "Accessing a Windows Network"
- Next in thread: apollo2011: "Re: Accessing a Windows Network"
- Reply: apollo2011: "Re: Accessing a Windows Network"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 09 Jan 2005 22:53:04 +0000
Kevin Sutherland wrote:
> I am a fairly new user to Linux and SuSE and have been using 9.0 for a
> year and just upgraded (Fresh Install) to 9.1 a couple of months ago.
> I have been trying to get my Windows network working under Suse. I
> have a couple other Windows XP machines on the same network as my
> Linux/Windows XP system. I have tried SMB4K and haven't been able to
> get it to work with the network. Can anyone help me with any tips or
> suggestions as to how I would get my Windows Network accessible under
> Suse?
Using a mixed suse and M$ network:
I am using 9.1(prof) in a win network apparently ok.
A number of questions come to mind:
1) online updates seemed to be important for at least one samba (network
related) item
2) yast was used to install and configure Network Services, Samba Client,
(also) Samba Server. At this point yast prompted me to insert the
various install CDs to complete installation of Samba installation. (If
I had installed via FTP I would have used the FTP install source).
3) Samba Client then needed the win workgroup name (I am not using a domain)
4) Samba Server needed 'enable', the workgroup name, a server description
and a netbios name, along with Sharing Type (File&Printer for me), and
then available shares to be stated.
(I use KDE)
5) KDE Control Centre:
Internet&Network, File Sharing (admin password etc) - allow
Internet&Network, Local Network Browsing, default user name and password
if relevant in lan, workgroup name.
6) Firewall activity is obviously relevant, both on the windowboxes and the
linux boxes.
7) On the various machines, the file:/home/user1 (linux) and
mydocuments (etc) (win) need to have sharing permissions set appropriately
Note 1
In 9.1 I have not been able to get the kde desktop 'Network Browsing/'
icon to work reliably/fully - it gives a konqueror window with Location as
service:/
and the windows network appears to be indicated. However, with 9.1 I
have seen reports of problems on some occasions - and my own experience
has been very mixed - settling to the existing situation where clicking
the windows network yields a kde error when trying to access smb:/
A work-around has been to simply use a konqueror window with a location as
smb://workgroupname/
This shows the local workgroup, and browsing is functional and reliable.
I made a new desktop icon for this.
Note 2
Having said all this, I have successfully used some (limited) file
sharing with a 9.1 prof installation and M$ PCs with only the KDE
Control Centre Internet&Network configured (I believe this is a limited
configurartion of the Samba Client (not Server) only). (This limited
method does not allow M$ PCs to see the linuxboxes, but it works vice versa
hth
-- AlanC
- Next message: Michael Heiming: "Stats alt.os.linux.suse (last 7 days)"
- Previous message: Kevin Nathan: "Re: Accessing a Windows Network"
- In reply to: Kevin Sutherland: "Accessing a Windows Network"
- Next in thread: apollo2011: "Re: Accessing a Windows Network"
- Reply: apollo2011: "Re: Accessing a Windows Network"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
