I'm trying to mount an NFS share from my Gentoo computer on my FC12 laptop, but every time I try to mount the share my laptop completely crashes. The end result is that I have an unresponsive laptop which switches from X to a blank screen and I'm unable to switch to any VT's or reset X. I never had any issues with my laptop freezing like this when I had Gentoo on it, but I'm giving FC a shot.
Server:
NFS version: 3
Code:
$ cat /etc/exports
# /etc/exports: NFS file systems being exported. See exports(5).
/mnt/OSX192.168.*.*(async,rw,no_root_squash,no_subtree_check)
Running rpcinfo on the server (command run from client)
[Code]...
Anyone recognize these symptoms or know which log files to look in to begin diagnosing? Currently, I'm only able to transfer files via ssh, so I'd like to be able to do that properly.
So my brother has a home network that is setup with multiple workgroups (don't ask why - I have no idea and he refuses to change it). Anyways I just installed Mint 9 (Ubuntu 10.04) on my mother's computer and I need it to be able to access the fileserver in her house where her data is stored. The Mint system is part of the default workgroup and can only see one other system in this workgroup.
The workgroup the file server is a part of is called "hobnw", the server's name is "fileserver", and the share I want to connect to is called "TV Shows" How can I connect to this network share on Linux? (I also know the username and password) When I browse the network under nautilus all I see is the default workgroup and no others. All of the Windows systems on the network (Windows XP, Vista, and Win7) all see and can access the file server without issues.
My question is that I have a handful of servers, Server 1 is a Suse Linux machine and Server 2 is a Windows Server 2003 machine. I can mount and access the files/shares on the Linux machine no problem but when I come to using the Server 2003 shares I encounter problems ... here is a snip of my fstab ...
Code: //10.0.0.20/applications /myfolder/applications cifs username=user1,password=pass1,auto,uid=user2,gid=group2,0 0 user1 and pass1 is the username and password of a user (local to the remote machine) and user2 and group2 are taken from the machine performing the mount.
Am I doing it right, is that how I should be mounting a share from a (Domain enabled) Windows Server 2003?
I've got a mostly Debian Lenny network but I've set one machine up with Squeeze. One the Squeeze machine I can mount my NFS shares manually but can't get them to mount at boot time. Here's my /etc/fstab file:
Code: # /etc/fstab: static file system information. # # Use 'vol_id --uuid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass>
Using Xubuntu 10.04 to connect to some Windows XP shares by adding lines to fstab. The network shares are not mounted at boot, but can be mounted from the command line, after the OS has booted and everything is up. I am suspecting the network isn't up yet, when fstab is processed. I tried adding the option "_netdev" to the relevant network share lines in fstab, but the shares still don't mount automatically at boot up. I read that this option only works for NFS and I am using CIFS. Can someone confirm that _netdev only works for NFS ?
I've seen solutions involving running a mount script after the OS is fully loaded, or running a cron job to periodically check the status of the share and mount if needed. Good workaround but doesn't address the root cause. Is there any other way (besides the _netdev option) to delay mounting of network shares that appear in fstab until the network interface is up ?
I setup samba file sharing to auto mount in fstab. Everything works great except when a computer has more than on user account.
The folders in mnt are owned by root and ownership changes to the first user account no matter what user logs in. So only the first user can edit files in the mounted share.
Anyone got a clue why this is happening? Seems the mount folders should be changing ownership to the user that is logged in.
My network is barely functional. I'm running 2 linux servers connected by openvpn (tun) through routers on both sides. There are Windows clients (98 and XP) on both subnets. One server (ls3) acting as PDC for the domain. The Windows clients use the respective linux boxes as gateways. On the server side (ls3 which is both openvpn server and samba server), all the clients can read/write properly to shares on both sides. The problems are all on the client side. Share connections to the server side disconnect after a few moments.
Browsing on the client side windows machines is fine. I can see shares on the server side. Some server side files open and are readable, writable, other server side files will not open. Some samba logon scripts on the server side can be opened from the client side. Others open after a long wait to a blank file! Permissions on server side files are set to 777 for testing. If a file won't open or reads "blank", that doesn't change no matter how many times you try. A non-readable/writable file overwritten by a readable/writable one can be read and written to!
I can ping successfully from any client on either side to any other client by either ip address or workstation name. Firewalls on both side are set to forward tcp and udp traffic going to port 1194 to the respective gateway linux boxes. Iptables on both linux gateways are down for testing. I tried reversing the openvpn server/client roles with the same result; the same physical side of the network had the problem. On one of the windows 98 clients, I wiped out the networking configuration completely and rebuilt it from scratch. Same result.
One one of the windows xp clients, I tried to rejoin the domain. It went through successfully but the result was the same as above. The network was operating smoothly for several years until the client side dsl modem broke last week. It was replaced with a newer model and at the same time I migrated from a pptp connection to openvpn. How to resolve this, Is this something to do with openvpn? Is this a network hardware problem? Am I missing something in the port forwarding on the routers? My smb.conf files are ancient except I added interface tun0. I have never seen 2 files sitting next to each other in the same directory where one opens and the other doesn't!
I'm running Mandrake 9.2 on the client side and Mandriva 2008 on the server side. I have a Sonicwall firewall on the server side, a Westell 7500 on the client side. I note that during the modem install, the http port was opened to the linux box on the client side and the access log got huge over the weekend and I ran out of disk space until I closed it down and deleted the log. I tried a simple test while viewing /var/log/daemons/errors on the client side. From a windows workstation in the client subnet, I opened a dos window and tried to print a file located on the samba server on the openvpn server machine which I knew NOT to be problematic.
The file printed and there were no errors reported in the log. I repeated the test with a known problematic file. The file would not print. The errors log noted: Authenticate/Decrypt packet error: packet HMAC authentication failed I regenerated the static.key file on the server side and scp'd it to the client side and restarted both openvpn's. I checked for duplicate files named static.key on both sides. Same error.
I setup a Samba share and I cannot connect. I can mount in on local host but when I CD to the folder I mounted the share on I get access denied when I run ls.
I've been having terrible trouble with my 64bit Desktop v10.04 ever since I upgraded it. Has been a long battle - but I think I have it down to just one remaining issue which I suspect is more related to the network than to the upgrade. So I'll ask here also... The old system always used grub as the bootloader, and has always worked just fine. I have now had to do a complete fresh install, which incorporated a change to grub2 (first time I have used it).
It would seem now, that grub2 is unable to deal with mounting the samba shares on my lan at boot time. The boot always fails, dumping the user to the cli rather than the gui desktop. The error given indicates that the network is unreachable. Most users of the system have given up on Ubuntu altogether because of this, and fallen back into the clutches of the evil empire (the machine dual boots XP). If I log in, and manually startx to open the desktop, the network is there, and the shares are mounted just fine. Everything seems to be working ok - but for crashing out of the boot process with network errors. The fstab file follows, in case there is some cause there I'm not seeing (I have edited names and passwords prior to posting)...
I have a machine acting as a gateway for a private network. While it can ping hosts on that private network, I can't use samba (smbclient or smbmount) to access shares on hosts on the private network from that machine. Other machines on the private network can access shares on other machines - just not the gateway server.
Here's how the gateway is configured:
When I try to connect to ports 139 or 445 (via smbclient or smbmount) the mount() system call times out. As I mentioned above, I can ping those hosts, so UDP packets work but TCP packets seem to get blocked or lost.
I have an Ubuntu 10.10 server and client. The server is stable, but the client crashes when writing to an nfs mount.The server has a software RAID, and I have tried every combination I can think of for mounting the share (udp, tcp, write size, nfs, nfs4 and so forth).
I don't have any security on the share, and it only appears to happen when writing to the share (so far). It happens fairly consistently when writing large files (over one GB). The copy starts to stall/start, then the whole interface freezes. I can't drop to other levels (ctrl-alt-f1), but there is still disk activity, and I had it beep at me after a freeze when I clicked several keys....
Tested with diffrent parameters. And another problem also with samba shares, when I edit file from editor (eclipse) after save i got 'file changed dialog'. seems like file is written with some delay ? and timestamp dont agree (its my blind quess). On 9.04 no problems. Tested with 2 instances of Eclipse. One copied from 9.04 and second fresh install. Other editors raport the same problem. Its anoying as hell.
I'm using ubuntu 10.04 (gnome) - at some point, I had manually mounted a samba share on the home fileserver,
mount -t cifs //homeserver/sharename /serverfiles
It now boots up automatically every time, which is definitely convenient but I don't know how it's being done. I'm going to be mounting the same share using sshfs when I'm away so I'd like to know how it works. When I googlify this, there is mention of altering fstab (which has not been done) or gnome-mount (which does not seem to be it). There is nothing in preferences/startup applications, what is the automounting mechanism being used?
I run opensuse 11 at work. I'm trying to see the list of shares on a "server" that is running windows server 2000. If I try smb://server, it doesn't show any shares, but I can browse directly to it such as smb://server/share1. If I use smbclient, it returns the list of shares correctly. I guess I just don't understand why smbclient shows the list of shared folders, but nautilus cannot.
I am posting this as I have tried several times to work this out. I have read article after article, post after post and tutorial after to tutorial to sort this issue. I have an Ubuntu 10.04 machine running as the LDAP and NFS server with two Opensuse 11.3 desktop machines. Both of the Opensuse machines can login using the LDAP server for authentication and this works fine. The server also exports the NFS Shares no problem but I am unable to mount the shares from the Opensuse machines. I have been using Yast, NFS Client to mount them.
Yast NFS Client can see the shares and lists them however when I apply the settings it states:
'Unable to mount entries in etc/fstab' I need to mount the shares according to the LDAP details as I want the users to be able to access their files no matter which machine they login at. Can anyone shed any light on the issue. Any help would be great and I would be enternally grateful as I am now beginning to pull my hear out slightly.
I'm using Opensuse 11.4 updated from 11.3, update from 11.2 updated from. I'm mounting at boot time (in fstab) some shares from an opensuse 11.2 server. Mounting worked fine in 11.2, 11.3 and also in 11.4 but suddenly (maybe an automatic update?) It stopped working.... sometimes.
Sometimes they are mounted properly but sometimes they aren't. When mount fails I get a log error: "rpc.statd is not runninf but is required for remote locking. Either use '-o nolock' to keep locks local or start statd"
If I run manually (as root) mount -a the shares mount properly always, so I thought it was a problem of timing (the service starting late) so I tried to get a script to run after the network initialitation, the script does: "mount -a". But it doesn't work either.
I've been asked to investigate the possibility of using LTSP in our school to provide a more "real world" programming environment to our students. We have a Windows 2003 Server domain and no plans to change it.I've set up the LTSP server, joined the domain and everything seems to be working fine, I can login to the LTSP server with a student account.
The next thing I want to achieve is give the students access to their "My Documents" folder on the Windows 2003 server. Is it possible to have a student log on to the terminal server (who has never logged in before) and have it automatically mount their share on the windows server?
NFS share is up. it's set to r/w. This is Ubuntu 10.10 NFS4 i believe. exports file looks like this; /data/feeder 10.10.10.1/255.255.255.0(rw,async,no_root_squash,no_subtree_c heck)
on the client, /etc/fstab looks like this; 10.10.10.1:/data/feeder /opt/feeder nfs rw 0 0 when I ls -la into /opt/feeder I see all the persmissions as: 4294967294:4294967294 instead of root:root
I wrote a little script that will automatically mount two Samba shares to my home directory and I was wondering if a) You guys/gals had any input as to how I could improve on this script and b) Tell me how I would go about having this script automatically execute when I log on via SSH.
Code:
#!/bin/sh mount -t smbfs -o username=Myuser,password=Thepassword //192.168.1.102/Data1 /home/user/Data1 mount -t smbfs -o username=Myuser,password=Thepassword //192.168.1.102/Data2 /home/user/Data2
I run a mediaserver on Archlinux, working perfectly (or almost). I have set up NFS v3 and that worked for me on these clients:
- Debian Lenny - Archlinux 64bit
Now I've upgraded my Lenny-box to squeeze and I see that 2 of my 3 shared folders (tdone and twatch) are mounted like they should and the third one (media) doesn't come up. A 'mount -a' as root gives this error: mount.nfs4: access denied by server while mounting (null) My relevant fstab-lines:
I have the following problem:I have to networks in remote places.I have an opnvpn client in one network that connects to the the router (openvpn server).My question is,can i connect the network where the openvpn client is,throught the computer with the client to the other network.If yes,how? (please make it an idiot proof anwser because i have limited knowledge about iptables). I was thinking like forwarding (the router in the network with the openvpn client is also firewalling with iptables) the request of the ip class of the openvpn network to the computer with the client,which masquarades the interface
I'm just staring with fedora 11 and I want to know how to do the following: 1- Connect to windows shares on another PC. 2- Set these shares to be accessible in the Computer location at all times.
After upgrading my Sony VAIO from Fedora 12 to Fedora 13 my NFS shares don't seem to be working correctly. First of all, mounting them via /etc/fstab is quite slow now. More importantly, When I transfer files from my laptop client to my NFS share, the owner/group on the client become "nobody". However, on the NFS server, they are both "root". I am using a script containing "cp" commands to perform backups of certain directories, retaining original owner/group info. Since the Fedora 13 upgrade, the script complains with each file that it was unable to preserve the information, and the end of the line always contains "Invalid argument".
As a last resort, I upgraded the 'server' (a 64 bit version) from Fedora 12 to Fedora 13. There has been no improvement.
This is a bit of a shameless cross-forum bump, as I'm really trying to crack samba in the hope of getting some server action going, and this is the closest I've been to actually understanding what I'm playing with. "Well, I've lasted a lot longer than usual before resorting to asking around, but I've finally gone delightfully mad. I've been trying to access shares based on Windows 7 Ultimate with limited user access on said shares. I've managed to get into my XP machine, another mate's Vista machine and various Linux boxes with no issues, but that's only for shares that are accessible by everyone. The moment I try to get into a share that requires user credentials, I get "Error returning browse list: NT_STATUS_ACCESS_DENIED"
If I try to access restricted shares (be it machine or folder) through Nautilus, I will get a user logon prompt, but it fails. Using smbclient results in just as little success, and now I'm munching through O'Reiley's Samba manual from '99, after realising that I need to basically learn Samba in its entirety to have a hope in hell at getting this to work. The trouble is though, every HOWTO and relevant forum post I get my hands on all seem to concentrate more on the server side of things, and usually servering from a linux box, not the other way around as I'm trying to.
The above Windows 7 machine won't even allow me to view its share contents, whereas the XP machine will allow me to browse, but won't allow me to access folders with restricted access. I'm pretty sure there aren't any major issues with the way the Windows 7 machine is setup, as it can be accessed with logon from my Xbox, Ubuntu machine, XP and Vista, with only Fedora having problems getting in as it constantly fails logon. What I'm trying to establish is, if Ubuntu can get in, is there something in my Fedora samba config I'm missing that's preventing me access? My thanks in advance to those of you who've been able to put up with me rambling"As you'll see in my original fedoraforum post, the workgroup misreport issue mysteriously fixed itself after a few updates, although I'm inclined to blame my mate's Win 7 box...call it force of habit, I've just generally come to mistrust an OS that tries so diligently to shift focus away from its shell.
After latest samba updates from updates-testing (F11) I can't copy any file from the network via samba: when copy process reaches almost end of the file, error message appears 'Invalid argument'. Such error happens with any read attempt on a network file - the last ~5% of a file can not be read.
I am unable to mount Windows shares on Fedora 12. From Nautilus, I can navigate to the shares, but when I attempt to open one I get a dialog "Password required for share ... on ..." asking for username (prepopulated with my username), domain (prepopulated with MYGROUP) and password. I have the same username on the Windows box, but when I enter the password and click Connect, the dialog just pops up again. I'm not sure what "domain" is, tried with my Windows workgroup name, no good. If I blank out either username or domain, the Connect button is disabled.
I tried using the mount command:mount -t cifs //192.168.0.2/... /tmp/mnt -o username=adrian,password=...,iocharset=utf8,file_m ode=0777,dir_mode=0777 That did work once, but now gives the useful error message:mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) I can run Windows instead on the client machine, and that gives me access to the shares, no problem.
I have libsmbclient-3.4.5-55.fc12.i686, but that was installed a month ago. I don't see any more recent changes to anything relating to the samba client. I've never had to enter a password to access Windows shares. Actually, it looks like the problem may be on the Windows side, although as far as I know, nothing has changed there. Using smbclient with debuglevel set high, I see failures with this error:SPNEGO login failed: NT_STATUS_REQUEST_NOT_ACCEPTED Every now and again, I can connect to one or more shares, but after a few attempts, I can't connect to any more. Tried rebooting the Windows box, but that's had no effect. Oh, and "smbclient -L" shows domain as the host name of the windows box, but anonymous login (smbclient -L -N) shows domain as the workgroup name.
After booting, the sda5 and sda8 mounts work fine, but the Windows shares haven't been mounted. If I enter the command: mount -a everything works fine. I don't know if this a timing issue, or something to do with the new systemd stuff, but it has happened in previous Fedora releases from time to time.
Currently I am trying to get some fedora shares to simply connect to each other to access a read-only shared folder on a host machine (no security/encryption even required for these files!). I've tried to get a smb network share going but that didn't work (can't connect with nautilus), I've tried a quick fix with daap and rhythmbox so that they can at least access the music, but rhythmbox fails very miserably trying to connect/create that (and mt-daapd didn't help much) - Basically I get errors saying the host is unreachable.
I haven't even set up a firewall yet for this network and already I'm running into these fundamental problems. Currently I'm using Fedora 15. On a whim I tried the "public" folder and had sharing of the public folder over the network enabled - yep, didn't work (and I certainly didn't expect it to). I would be trying some more advanced CLI stuff, setting up an ssh server or something, but the computer-challenged people who have to access these files just want to be able to click something and have it work.For the operational requirements of this setup, a file synchronisation system would work (although highly inefficient since it would mean gigabytes sent over the network).
