On three Ubuntu based computers cannot access the server
The fourth computer is the server, running POP-OS the others are a desktop running Ubuntu Unity (installed inn 2021), a Dell Vostro running Linux Mint and a System76 Darter laptop running POP-OS.For many years now the three have accessed the server using NFS quite successfully.
Now however for a few months this has been haphazard. I blamed it on the Shaw Modem, got a new one , no change . So I bought a new router and there was no improvement. The only one where this command: (sudo mount -t nfs -o proto=tcp,port=2049 192.168.0.104:/mass /media/mass) worked was the desktop connected by WiFi running Ubuntu Unity. There it stayed, the same command on the two laptops resulted in the partition being mounted but only stayed for about 20 seconds.
The Tech I contacted at the router provider, after seeing sections of the syslog determined it was not a router problem.
Thus this long story.
A bit if syslog:
ystemd: service name='org.
Mar 9 19:35:52 seanix systemd[1012]: Starting GNOME Terminal Server...
Mar 9 19:35:53 seanix dbus-daemon[1044]: [session uid=1000 pid=1044] Successfully activated service 'org.gnome.
Mar 9 19:35:53 seanix systemd[1012]: Started GNOME Terminal Server.
Mar 9 19:35:53 seanix systemd[1012]: Started VTE child process 11937 launched by gnome-terminal-
Mar 9 19:35:53 seanix wpa_supplicant[
Mar 9 19:35:59 seanix wpa_supplicant[
Mar 9 19:36:00 seanix autonfs.sh[730]: Fileserver is up.
Mar 9 19:36:00 seanix autonfs.sh[730]: /media/mass is already mounted.
Mar 9 19:36:00 seanix autonfs.sh[730]: NFS share not mounted; attempting to mount /media/mass0:
Mar 9 19:36:02 seanix wpa_supplicant[
ea@seanix:~$
Note the line at 19:35:53 What does that mean?
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- actionparsnip
- Solved:
- Last query:
- Last reply: