- This topic has 12 replies, 5 voices, and was last updated Dec 2-11:41 pm by Robin.
-
Posts
-
Alexntix
I’m using google translator…….sorry.
I have recently been using Antix 21. I find the system fantastic.
I am not a great expert of the linux operating system. but I like to mess around with the different distributionsbut I ran into severe problems in terms of connectivity. the Connectshares program manages to list the servers, but not the shared folders.
I know that these folders exist, they are accessible from other devices.+ adding the shared folder in the configuration file by hand does not result in a successful connection.
+ this happens with all computers that I try to connect to from Antix.
+ the Firewall in all computers is down.
+I am connected to a wired network, as are the servers.
+I’m not sure what other information to put …
Robin
Hello Alexntix,
try to look into your ~/.config/connectshares/connectshares.conf file. There should be at least the following entries, depending whether you want to connect Windows network shares or NFS shares.:
REMOTE=<Name or IP> SAMBA=y WORKGROUP=<Name_of_Workgroup> SHAREUSER=<sharefoldername_1>,<sharefoldername_2>,<sharefoldername_3>, CREDAUTO=y CREDNAME=<login_name> CREDPASS=<password> SHAREGUEST=<sharefoldername_4>, NFS=y SHARESIPDNS=<sharefolder_name_5>,<sharefoldername_6>, NFSOPT=rw,hard,intr,timeo=30,retry=0,After editing this file with a text editor you only need to start “Connectshares”, without its configuration/setup wizard. It will try to connect to all shares set in this config file, and in case you have set everything properly the share(s) will be a available in your default file manager immediately.
Only in case you run an outdated samba share server you’ll have to add the line
SAMBAOPT=vers=1.0,
to the config in order to be able to connect.Make sure not to omit the trailing commas in some of the lines, it won’t work without these.
Windows is like a submarine. Open a window and serious problems will start.
Alexntix
I just tried, the configuration file I wrote as you showed me. test with and without “vers=1.0”
+ using the name of the PC, throws the error “unable to connect”
+using the IP instead of the name, stop connecting and then the message “did not mount -shared folder on IP” appears
-shared folders are accessible from android, windows and other linux systems. I can also access them from Antix 21 but only mounting by hand from the terminal.
dirkd
It’s just a suggestion, but I connect my Antix system to remotely shared folders exclusively via the /etc/fstab configuration file. This works very well for me, but could be cumbersome if you have to change a number of connections regularly.
using the name of the PC, throws the error “unable to connect”
Means there is some kind of configuration error. It might be a wrong spelling, or case sensitivity, but also a non functioning network connection or a DNS server misconfiguration. So next thing I would try is, from console window:
sudo ping <name_of_PC>You should get back some lines of ping answer from the PC and read “0% packet loss” below, otherwise there is a network problem. Make sure to solve the network problem before trying to connect to your shares. If the basic network connection is fine, connectshares should work immediately.
Windows is like a submarine. Open a window and serious problems will start.
olsztyn
I just tried, the configuration file I wrote as you showed me. test with and without “vers=1.0”
It has been some time since I used Connectshares as I am using FSTAB now, but when I did use it it worked fine if you specify all correctly in the config file. Looking at the above Config file one thing pops up to me that both SMb and NFS are specified as ‘Y’. When using SMB only the SAMBA should by ‘Y’, and NFS should be ‘N’.
I do not know if this is the only issue here but all specification in Config must be correct in order to work.
If you did connect from terminal then you have all parameters that should be used in the Config, just remember the trailing ‘,’, as Robin mentioned…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersAlexntix
thank you for all the interest in my little problem.
I try with the PING, Robin, returned “Name or service unknown”.
tried several times, in case I was wrong with the capital letters.the computer with the ANTIX 21 system is the only one that presents this problem. the other PCs (windows/linux) can work with the names without any problems.
do not know anything about configuring network. apart from configuring very basically SAMBA. and mount the shared folders. so I wouldn’t know where to look
dirkd
@Alexntix: you should first do a ping with the IP address, and afterwards with the hostname. Make it (the hostname I mean) fully qualified: ‘antixpc.local’ in stead of merely ‘antixpc’
Alexntix
@Alexntix: you should first do a ping with the IP address, and afterwards with the hostname. Make it (the hostname I mean) fully qualified: ‘antixpc.local’ in stead of merely ‘antixpc’
something interesting found with your suggestion, dirkd.
although Antix21 cannot PING other computers on the LAN by HOSTNAMES (with or without .LAN/.LOCAL). the other PCs only achieve PING with Antix21 with the HOSTNAME “Antix1.local” or IP.
Dave
I suspect you may get the same error as when trying to use the ip address but this may be worth mentioning.
Try adding the hostname of the machine you are trying to connect with to the /etc/hosts file to relate it to the ip address.
EX: 192.168.0.55 |MyPcShareHostname- This reply was modified 1 year, 5 months ago by Dave.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
If your ping doesn’t go through, you could try
arp -a
in console window to see whether the PC you want to reach is seen within your network neighbourhood. This will show you the fully qualified name of the device and also it’s recent IP. If not, you’ll have to check whether your local dns/dhcp server works properly. It’s often integrated within your router/dsl-modem. antiX should retrieve the DNS server to be used from this DHCP server on startup and hold the resolved names in its own local dns cache at 127.0.0.1. (Mostly the router provides a local dns server along with an DHCP server) Only in case of configuration errors you won’t be able to connect (e.g. in case you run the devices in different subnets (e.g. 192.168.178.41 and 192.168.179.42), you need to build up a network bridge from e.g. 192.168.178.x to 192.168.179.x or force the devices to run in a single network segment (e.g. both within 192.168.178.x). Normally all this should work automatically… Maybe you have added manually a non compliant network address or a wrong subnet mask for a device.Windows is like a submarine. Open a window and serious problems will start.
Alexntix
this is the only thing the command ARP -A throws.
$ arp -a
? (192.168.0.98) at c0:25:67:89:f0:88 [ether] on eth0
? (192.168.0.167) at 6c:f0:49:92:e0:8e [ether] on eth0
_gateway (192.168.0.1) at 02:10:18:aa:b6:d4 [ether] on eth0
? (192.168.0.105) at 2c:f0:5d:d6:62:4f [ether] on eth0
$ arp Antix1
Antix1 (127.0.0.1) — no entry(unless I have used it in the wrong way)
I never touched the network settings of my computers. none should be in a subnet or have something different from what is automatically generated
Strange thing. Instead of the question mark in the beginning of the output lines I’d have expected the fully qualified name of the network device, right in front of the IP in parentheses. Obviously many things have changed in modern linux, so the old strategies don’t apply anymore. I would have used now the console commands ifconfig -a, traceroute, dnstraceroute, dig, nmcli, nm-tool, nslookup, host -l and so on, but many of these are obviously not present on antiX. There is a more recent tool simply called “ip”, may be you’ll be able to suck some honey from it. It runs like “ip neighbor show” (be aware of the spelling of neighbour), but it doesn’t give back neither the default dns server recently in use on the system nor the fully qualified name of the network device behind an IP.
As I’ve read: nowadays it is not enough anymore to cat e.g. the content of /etc/resolv.conf as we did before, since it now shows the local cache only.
So maybe somebody else may step in here to show us the recent alternatives used in antiX for this task, checking the complete local network infrastructure systematically to make it work.One thing is sure: Connectshares will start functioning the very moment, you’ve solved this networking problem you face here.
Windows is like a submarine. Open a window and serious problems will start.
- You must be logged in to reply to this topic.
