Mailinglist Archive: opensuse (2441 mails)
| < Previous | Next > |
Re: [SLE] 9.3: keyboard, zip disks, mounting encrypted FS, KDE Samba
- From: AmigaPhil@xxxxxxx
- Date: 12 Jun 2005 3:39:22 +0100
- Message-id: <1987.24T1107T2193284AmigaPhil@xxxxxxx>
Kevanf1 (kevanf1@xxxxxxxxx) wrote something I wish to comment :
(news:<7bca46c505061115361596728b@xxxxxxxxxxxxxx> posted on 11-juin-05
23:36:14)
>> - Samba / KDE
>> I'm trying to access my second computer using the KDE Samba client,
>> but I'm getting all sorts of errors like "connection timeout", ...
>>
>> Is KDE/Samba reliable or should I configure my Suse/Linux machine
>> as a Samba server ?
>>
>> Note: When I was using the 8.0 distribution, I found that the best
>> (stable) way to access my Amiga computer shares was to mount the
>> shares using LinNeighborghood (which is no more part of the 9.3)
>> I believe the Samba support has improve in recent distributions,
>> so I think I should still be able to access my Amiga shares now.
>> I would like to see the shares being mounted (if the remote
>> computer is available) as I log in as user.
>>
>
> I can't help with any of the other stuff but the Samba one...If you
> just want to access drives etc on another PC (MS Windows) you don't
> need to configure a Samba server just a Samba client. The server bit
> is if you want to be able to share stuff from your Linux PC onto the
> Windows one. It should set up automaitcally. It did with my 9.3 tin.
> Or was I just lucky? Take a look in YaST :-)
Thanks for trying to help.
I suspect the Suse firewall is preventing me to successufully access
the remote computer, as when I disable it completely, I can see the
workgroup and the computer (but not yet the shares).
Using Yast, I see that my network card is configured in the "external
zone", and I can from there allow access to "Samba server" for that
zone. But it seems it's not enough. I think I need to open some
ports "by hands", but which ones (nmb ? smb ?) ? And how to limit
that access for a specific IP ?
(Then, I still have to write a script (?) to mount the share and
place it somewhere in /home/ (?) )
AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1
(news:<7bca46c505061115361596728b@xxxxxxxxxxxxxx> posted on 11-juin-05
23:36:14)
>> - Samba / KDE
>> I'm trying to access my second computer using the KDE Samba client,
>> but I'm getting all sorts of errors like "connection timeout", ...
>>
>> Is KDE/Samba reliable or should I configure my Suse/Linux machine
>> as a Samba server ?
>>
>> Note: When I was using the 8.0 distribution, I found that the best
>> (stable) way to access my Amiga computer shares was to mount the
>> shares using LinNeighborghood (which is no more part of the 9.3)
>> I believe the Samba support has improve in recent distributions,
>> so I think I should still be able to access my Amiga shares now.
>> I would like to see the shares being mounted (if the remote
>> computer is available) as I log in as user.
>>
>
> I can't help with any of the other stuff but the Samba one...If you
> just want to access drives etc on another PC (MS Windows) you don't
> need to configure a Samba server just a Samba client. The server bit
> is if you want to be able to share stuff from your Linux PC onto the
> Windows one. It should set up automaitcally. It did with my 9.3 tin.
> Or was I just lucky? Take a look in YaST :-)
Thanks for trying to help.
I suspect the Suse firewall is preventing me to successufully access
the remote computer, as when I disable it completely, I can see the
workgroup and the computer (but not yet the shares).
Using Yast, I see that my network card is configured in the "external
zone", and I can from there allow access to "Samba server" for that
zone. But it seems it's not enough. I think I need to open some
ports "by hands", but which ones (nmb ? smb ?) ? And how to limit
that access for a specific IP ?
(Then, I still have to write a script (?) to mount the share and
place it somewhere in /home/ (?) )
AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1
| < Previous | Next > |