You are not logged in.
- Topics: Active | Unanswered
#1 2005-02-17 15:43:42
- MillTek
- Member
- Registered: 2005-01-30
- Posts: 442
Network access with Tux Commander - can anyone help??
Hi,
I'm using Tux Commander as my file manager (latest release). I use it with Fluxbox over Arch. We have a small Lan with 2 MS win boxes and two Linux boxes. If I use XFFM I can see and get at all the other machines through the SMB Network option.
One of the TuxC options is Network and when I select that it then has an option for 'Open Connection'. Next you get to define each 'connection'. I enter the following values into the following fields;
Name >> OURSERVER
URI >> smb://administrator.***@OURSERVER
Server[;port]: >> OURSERVER:
Username: >> administrator
password >> ***
When I select 'connect' it replies with;
'Couldn't open the URI specified. Please check the consistency of the resource identifier and the access permission.'
Does anyone have a clue? I have scoured the net for detailed docs on Tux Commander and found none although it is a good file manager and I'd really like to be able to use it.
Thanks,
Jim
Offline
#2 2005-05-02 10:26:47
- Cotton
- Member
- From: Cornwall, UK
- Registered: 2004-09-17
- Posts: 568
Re: Network access with Tux Commander - can anyone help??
Any chance of a PKGBUILD for tux commander?
Offline
#3 2005-05-02 21:47:47
- swiergot
- Member
- From: Kraków, Poland
- Registered: 2005-01-08
- Posts: 145
Re: Network access with Tux Commander - can anyone help??
Any chance of a PKGBUILD for tux commander?
Offline
#4 2005-05-02 22:03:21
- phrakture
- Arch Overlord
- From: behind you
- Registered: 2003-10-29
- Posts: 7,879
- Website
Re: Network access with Tux Commander - can anyone help??
well, if it's standard URI format, it should be:
protocol://username:password@address
protocol = smb
username = administrator
password = ***
address = OURSERVER
smb://administrator:***@OURSERVER (you had a period)
Also, try it w/o the password and it should ask for it.
This is all, of course, if TuxCommand supports the smb protocol...
You may also need a way to resolve the server names if TuxCommander doesn't use NetBios to resolve them
Offline