Unable to access samba share.

I'm setting up a ubuntu file server with samba shares and security = user.
These shares are able to be accessed and work correctly for both linux and windows clients. When I attempt to connect to the shares in OSX I get the usual username/password dialog box, however it doesn't accept the correct credentials.
I've googled for help for a few hours now, but cannot find anything that helps. I'm guessing its a security setting somewhere in OSX, but I'm not able to find out what.
Any ideas?

turns out that I was connecting to it incorrectly.
correct method is smb:\\workgroup;user@server\share

Similar Messages

Nemo and Nautilus crashing on accessing Samba shares

Hi,
I've made a clean install on a new laptop, and I've installed the cinnamon desktop environment. I've installed the following versions of these packages in order to get samba to work with nautilus:
Name : smbclient
Version : 3.6.12-1o
Name : gvfs-smb
Version : 1.14.2-3
Name : nautilus
Version : 3.6.3-1
Name : gnome-vfs
Version : 2.24.4-6
However, I get a segmentation fault every time I try to access any samba share or just by simply typing smb:// into the address bar.
Using the gnome-control-center printer setup also causes a segfault. Here is the dmesg output:
[ 748.193864] nautilus[3051]: segfault at 0 ip 00000000004c 1a89 sp 00007fff15bf8440 error 4 in nautilus[400000+14c000]
Can anyone help?
I'm unable to find any specific help on the forum for this particular problem
Thanks!
Last edited by shawntan (2013-02-01 09:12:44)

I've been trying to isolate the problem, and I think it has to do with gvfs-smb.
I am able to access shares via smbclient, and I even tried installing KDE's dolphin, which worked flawlessly as well.
I'll see what happens if I use an older version of gvfs-smb.

App freeze on accessing Samba shares

Hi,
I really didn't want to have to make a topic on this, as I've searched all over the place and I'm beginning to wonder if I'm the only one with this problem (unless I've somehow missed something).
Basically I have some Samba shares set up like this in my fstab:
# Share Mounts
//<address>/share1 /home/eldersnake/Shares/share1 cifs noauto,x-systemd.automount,users,uid=eldersnake,gid=users,password= 0 0
//<address>/share2 /home/eldersnake/Shares/share2 cifs noauto,x-systemd.automount,users,uid=eldersnake,gid=users,credentials=<credentials location> 0 0
The problem is periodically, trying to access/mount these shares through let's say, Dolphin (but it happens in any file manager I try) causes the program to simply hang. It will stay there, hung and cannot be killed, even with the "kill -9" command. Only rebooting gets rid of the process.
And looking at the process list with KDE's system monitor lists the affected program status as "disk sleep". Again, it cannot be killed. I've seen this happen with my file manager, Clementine (when I tried to open up a file, therefore it opened up the file dialog and I clicked on a share mount) and even in my terminal...
Even running
sudo mount /home/eldersnake/Shares/share1
for example, nothing happens. The terminal is simply hung and never completes.
I say this happens periodically because sometimes it seems to work just fine. Then some days, it does the above consistently. I'm really unable to pin it down.
Anyway I removed the x-systemd.automount option from fstab and so far I have not been able to reproduce this problem. I'd file a bug report but I can't help but wonder if I've missed something obvious and I'm unsure how to provide evidence that it's systemd specifically causing the problem. Thanks for any help.
EDIT: I should add this occasionally also happens on a separate machine, my netbook. Again, only after adding the systemd automount line to the fstab file.
Also manually mounting the share with
sudo mount -t cifs <share> <directory>
always works fine. It's simply when using the fstab entry combined with systemd automount.
EDIT: Took systemd-automount out of the title as I am not sure its the cause anymore.
Last edited by ElderSnake (2012-11-24 00:02:24)

Okay, still happening. Often I reboot and everything works fine but sometime later, can be 10 mins...could be 10 hours, this problem re-emerges.
I did however manage to catch this in dmesg
[ 4448.046038] kernel BUG at fs/dcache.c:2138!
[ 4448.046041] invalid opcode: 0000 [#1] PREEMPT SMP
[ 4448.046046] Modules linked in: fuse msr des_generic ecb md4 md5 hmac nls_utf8 cifs fscache usb_storage uas joydev hid_generic snd_usb_audio snd_usbmidi_lib snd_rawmidi usbhid snd_seq_device hid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer nvidia(PO) snd r8169 soundcore iTCO_wdt psmouse serio_raw acpi_cpufreq mperf coretemp mii evdev microcode firewire_ohci firewire_core crc_itu_t gpio_ich intel_agp i2c_i801 iTCO_vendor_support intel_gtt i2c_core lpc_ich processor pcspkr button vboxdrv(O) ext4 crc16 jbd2 mbcache sd_mod sr_mod cdrom ata_generic uhci_hcd pata_acpi pata_jmicron ata_piix libata scsi_mod ehci_hcd usbcore usb_common
[ 4448.046115] CPU 1
[ 4448.046120] Pid: 3062, comm: pool Tainted: P O 3.6.6-1-ARCH #1 Gigabyte Technology Co., Ltd. EP45-DS3/EP45-DS3
[ 4448.046123] RIP: 0010:[<ffffffff81195843>] [<ffffffff81195843>] __d_rehash+0x83/0xf0
[ 4448.046133] RSP: 0018:ffff88009c627b88 EFLAGS: 00010286
[ 4448.046136] RAX: 00000000000176bd RBX: ffff880040ff7ddc RCX: 0000000000000013
[ 4448.046138] RDX: ffffc90000002000 RSI: ffffc900000bd5e8 RDI: ffff880040ff7d80
[ 4448.046141] RBP: ffff88009c627ba8 R08: 0000000000010000 R09: ffff88009c627fd8
[ 4448.046143] R10: ffff8800a751a4a0 R11: 0000000000000000 R12: ffff880040ff7d80
[ 4448.046146] R13: 0000000000000000 R14: 00000000fffffffe R15: 000000000000010f
[ 4448.046149] FS: 00007fb76933c700(0000) GS:ffff8800bfc80000(0000) knlGS:0000000000000000
[ 4448.046152] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 4448.046154] CR2: 00007fb74c0010b8 CR3: 000000003cb77000 CR4: 00000000000007e0
[ 4448.046157] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 4448.046160] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 4448.046163] Process pool (pid: 3062, threadinfo ffff88009c626000, task ffff8800638fa850)
[ 4448.046164] Stack:
[ 4448.046166] ffff8800a4af7e00 0000000000000000 ffff880040ff7ddc ffff880040ff7d80
[ 4448.046172] ffff88009c627bb8 ffffffff811958e6 ffff88009c627bd8 ffffffff8119591c
[ 4448.046176] 0000000000000000 ffff8800a4914480 ffff88009c627c38 ffffffffa0e6c973
[ 4448.046181] Call Trace:
[ 4448.046187] [<ffffffff811958e6>] _d_rehash+0x36/0x40
[ 4448.046191] [<ffffffff8119591c>] d_rehash+0x2c/0x40
[ 4448.046201] [<ffffffffa0e6c973>] cifs_lookup+0x263/0x360 [cifs]
[ 4448.046210] [<ffffffffa0e6cab2>] cifs_atomic_open+0x42/0x230 [cifs]
[ 4448.046214] [<ffffffff81197fa5>] ? d_lookup+0x35/0x60
[ 4448.046218] [<ffffffff8118eadf>] do_last+0x56f/0xea0
[ 4448.046223] [<ffffffff8118f4ca>] path_openat+0xba/0x520
[ 4448.046227] [<ffffffff8118fc91>] do_filp_open+0x41/0xa0
[ 4448.046232] [<ffffffff8119c766>] ? alloc_fd+0xd6/0x120
[ 4448.046237] [<ffffffff8117e9d6>] do_sys_open+0xf6/0x1e0
[ 4448.046241] [<ffffffff8117eae1>] sys_open+0x21/0x30
[ 4448.046246] [<ffffffff81499f2d>] system_call_fastpath+0x1a/0x1f
[ 4448.046248] Code: 48 89 16 0f ba 36 00 65 48 8b 04 25 f0 c6 00 00 83 a8 44 e0 ff ff 01 48 8b 80 38 e0 ff ff a8 08 75 0b 48 83 c4 10 5b 41 5c 5d c3 <0f> 0b e8 96 c2 2f 00 eb ee 49 89 c4 48 89 c3 41 83 ac 24 44 e0
[ 4448.046295] RIP [<ffffffff81195843>] __d_rehash+0x83/0xf0
[ 4448.046300] RSP <ffff88009c627b88>
[ 4448.046322] ---[ end trace 822cd52e99a52b51 ]---
[ 4448.046327] note: pool[3062] exited with preempt_count 1
[ 4448.055386] ------------[ cut here ]------------
[ 4448.055393] kernel BUG at fs/dcache.c:2138!
[ 4448.055396] invalid opcode: 0000 [#2] PREEMPT SMP
[ 4448.055401] Modules linked in: fuse msr des_generic ecb md4 md5 hmac nls_utf8 cifs fscache usb_storage uas joydev hid_generic snd_usb_audio snd_usbmidi_lib snd_rawmidi usbhid snd_seq_device hid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer nvidia(PO) snd r8169 soundcore iTCO_wdt psmouse serio_raw acpi_cpufreq mperf coretemp mii evdev microcode firewire_ohci firewire_core crc_itu_t gpio_ich intel_agp i2c_i801 iTCO_vendor_support intel_gtt i2c_core lpc_ich processor pcspkr button vboxdrv(O) ext4 crc16 jbd2 mbcache sd_mod sr_mod cdrom ata_generic uhci_hcd pata_acpi pata_jmicron ata_piix libata scsi_mod ehci_hcd usbcore usb_common
[ 4448.055471] CPU 1
[ 4448.055476] Pid: 3063, comm: pool Tainted: P D O 3.6.6-1-ARCH #1 Gigabyte Technology Co., Ltd. EP45-DS3/EP45-DS3
[ 4448.055479] RIP: 0010:[<ffffffff81195843>] [<ffffffff81195843>] __d_rehash+0x83/0xf0
[ 4448.055488] RSP: 0000:ffff88003a059b88 EFLAGS: 00010286
[ 4448.055491] RAX: 000000000004ad5b RBX: ffff880040ff7a1c RCX: 0000000000000013
[ 4448.055494] RDX: ffffc90000002000 RSI: ffffc90000258ad8 RDI: ffff880040ff79c0
[ 4448.055496] RBP: ffff88003a059ba8 R08: 000000000001b2c0 R09: ffff8800bfc9b2c0
[ 4448.055499] R10: ffff8800a751ae60 R11: 0000000000000000 R12: ffff880040ff79c0
[ 4448.055501] R13: 0000000000000000 R14: 00000000fffffffe R15: 0000000000000110
[ 4448.055505] FS: 00007fb768b3b700(0000) GS:ffff8800bfc80000(0000) knlGS:0000000000000000
[ 4448.055507] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 4448.055510] CR2: 00007f8507000000 CR3: 000000003cb77000 CR4: 00000000000007e0
[ 4448.055513] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 4448.055515] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 4448.055518] Process pool (pid: 3063, threadinfo ffff88003a058000, task ffff8800638fc890)
[ 4448.055520] Stack:
[ 4448.055522] ffff8800ae280200 0000000000000000 ffff880040ff7a1c ffff880040ff79c0
[ 4448.055527] ffff88003a059bb8 ffffffff811958e6 ffff88003a059bd8 ffffffff8119591c
[ 4448.055531] 0000000000000000 ffff8800956d5cc0 ffff88003a059c38 ffffffffa0e6c973
[ 4448.055536] Call Trace:
[ 4448.055542] [<ffffffff811958e6>] _d_rehash+0x36/0x40
[ 4448.055546] [<ffffffff8119591c>] d_rehash+0x2c/0x40
[ 4448.055556] [<ffffffffa0e6c973>] cifs_lookup+0x263/0x360 [cifs]
[ 4448.055564] [<ffffffffa0e6cab2>] cifs_atomic_open+0x42/0x230 [cifs]
[ 4448.055568] [<ffffffff81197fa5>] ? d_lookup+0x35/0x60
[ 4448.055572] [<ffffffff8118eadf>] do_last+0x56f/0xea0
[ 4448.055577] [<ffffffff8118f4ca>] path_openat+0xba/0x520
[ 4448.055582] [<ffffffff8118fc91>] do_filp_open+0x41/0xa0
[ 4448.055586] [<ffffffff8119c766>] ? alloc_fd+0xd6/0x120
[ 4448.055591] [<ffffffff8117e9d6>] do_sys_open+0xf6/0x1e0
[ 4448.055595] [<ffffffff8117eae1>] sys_open+0x21/0x30
[ 4448.055600] [<ffffffff81499f2d>] system_call_fastpath+0x1a/0x1f
[ 4448.055602] Code: 48 89 16 0f ba 36 00 65 48 8b 04 25 f0 c6 00 00 83 a8 44 e0 ff ff 01 48 8b 80 38 e0 ff ff a8 08 75 0b 48 83 c4 10 5b 41 5c 5d c3 <0f> 0b e8 96 c2 2f 00 eb ee 49 89 c4 48 89 c3 41 83 ac 24 44 e0
[ 4448.055649] RIP [<ffffffff81195843>] __d_rehash+0x83/0xf0
[ 4448.055653] RSP <ffff88003a059b88>
[ 4448.055666] ---[ end trace 822cd52e99a52b52 ]---
[ 4448.055670] note: pool[3063] exited with preempt_count 1
Not sure what to make of it though other than it's something CIFS related, but whether CIFS itself is the problem I'm unsure. I just installed the samba daemon as suggested above though and will see how we go.
EDIT: The pid it's referring to in the stacktrace is a process which I noticed appears as a zombie after the problem occurs. The process is "gvfs-udisks2-vo".
Last edited by ElderSnake (2012-11-23 23:41:44)

Unable to access DFS shares when server 1 goes down

Hello all,
I have a test domain I am building in order to prepare for a new domain we are going to create. We currently have an SBS 2003 that is reaching the end of its' life. We are going to start fresh. I have setup domain-based DFS along with DFS folder replication
for each of the folders. So far, all is working ok, up to this point.
Replication is occurring as it should and my Hyper-V test machines can connect to the mapped drives via the DFS namespace.
\\domain\namespace\target folder
However, once I shut down the primary server (SRV01) I am no longer able to access the shares. The namespace servers tab on the center window of the namespace MMC, has both SRV01 and 02 listed. I receive no errors except "Unable to connect to \\domain\namespace\target
folder because it is unavailable". It is not "failing over" to the secondary available server.
Once I power SRV01 back up, connectivity is then restored to the folders and mapped drives. Is there something I should check for, or am missing?
Any and all insight is appreciated.
Dario Garcia

Hi,
1. Run DFSUTIL /pktinfo to see if the referral target is still the primary server when it is actually down.
If so, run DFSUTIL /pktflush to flush the cached information and try to access the namespace again.
2. If 1 cannot help, whether DNS is also configged on primary server? If so, as it is down,
\\domain may not be recognized.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

Network Media Player (Noontec V9-T) unable to access network shares on WIN8 Pro

I have just upgraded from Windows 7 home premium 64 bit to Windows 8 Pro 64 bit. After the upgrade, I made sure my video library was shared (both with the homegroup and my username) and that network discovery was enabled file sharing enabled etc etc.
On the Noontec Media centre I can see the workgoup called WORKGROUP. When I click on it I can see the name of my PC. But when I click on the pc name to log in to access the shares within it comes up with a username/pass box comes up. I then put in my username/pass
on the windows 8 pro machine, to which the Noontec receives an error message stating cannot login.
Previously I had enabled sharing with everyone (read only) on windows 7 home and this username/pass dialog box never appeared. Just said successful logon. So i tried sharing video library with "everyone" in windows 8 pro, the unit still can't log on.
I believe this noontec uses Samba. The last updated samba file was named "samba_3.0.23c_mipsel.ipk" when I updated the media players samba about 9 months-a year ago. i have checked the manufacturers website, there has been no further updates released.
Is there a way for me to access network shares from this media centre by maybe installing a new samba server on the windows 8 machine that is compatible with older samba clients? I am not savy with samba clients/servers at all, I just loved the way XP network
shares always seemed to work across multiple platforms... and win7/8 doesn't. Help anyone?

A lot of these media players will not work correctly. If your Video files are stored as .avi, MKV, MP4 etc.. pretty much anything excpet for .ISO, the best way is to use Plex media server on the windows 8 PC. It's free and should allow you to organise files
and libraries as you want.In fact, it's my preferred access method now, as most, smart TVs also support plex and support it well....allowing me to play the files directly in my smart TV, without using the Media players.
In addition if you have an Android tablet or phone, you can (if you want) access your media files from Plex using Media Monkey (free) and simply play them direct to the TV, Media Monkey simply hands the data stream over to the smart TV.
I have a similar set of media players and exactly the same problem with windows 8,8.1, previous shares on versions 7, vist etc..work perfectly. I use a free application on my android phone to remote start my media server/s (via the network card).
Shutter Light - Free monitoring activity and network data, to prevent unwanted sleep during Videos and to ensure the PC goes into sleep mode (disabling windows power management)
Plex simplifies everything and acts as a great central server for all types of devices and can bring media files together from different Directories/Disks, in to one set of Libraries.

User unable to umount samba share

Here is the lines in my /etc/fstab related to samba shares.
# Some Windows/SAMBA shares
//BAO-QNAP500GB/USB\040Disk\0401 /mnt/eBooks smbfs workgroup=BAO-HOME,username=xxxxxx,ip=192.168.2.4,password=xxxxxx,noauto,noatime,user,rw 0 0
I am able to mount samba share as a user (not root) after
chmod u+s /usr/bin/smbmnt
chmod u+s /usr/bin/smbumount
by
mount /mnt/eBooks
However, I am unable to umount as a user:
[ning@HP-m8100y ~]$ umount /mnt/eBooks
umount: /mnt/eBooks mount disagrees with the fstab
On the other hand, this could work:
smbumount /mnt/eBooks
Can somone tell me what I did wrong?

Looks like its something to do with fstab though I don't know what never having mounted shares though fstab myself. I would try removing the fstab entry and just using smbmount to mount shares, thats the way I've always done it and never have problems with mounting/unmounting.
smbmount //IP Address/source folder /destination folder

WRT54GL unable to access wired shares or printer on PC from wireless iMac

The subject line applies to a new router on which I can access the internet ok both from the wired PC and the wireless iMac.
The problem is this router is unable to access the PC shares or printer from the iMac. Pls note, "this router"!
I have an identical WRT54GL v1.1, same firmware, setup is identical on both, one works with no problem, but the new one has the above problem..
I have spent a day on it and its in line for return on Monday, but I still hope for a miracle tip which may sort it out :-)
On the good one 'Port scan' of the PC from iMac gives me:
Port Scan has started ...
Port Scanning host: 192.168.1.100
Open TCP Port: 139
Open TCP Port: 445
while the faulty one gives me:
Port Scan has started ...
Port Scanning host: 192.168.1.100
..and thats it! No contact.
Yes, the router is set up for 'Lan & Wireless' (no way to change that setting to 'WAN only' it seems, it bounces back to 'Lan & Wireless')
I have btw done a Factory Reset on it (twice) with no joy.
Any ideas anyone?
Mvh

My first guess for this kind of problem would be a software firewall on the computer. The firewall will detect where it is connected and configures the settings depending on the location. Two routers are two different "locations". Try turning off the firewall or even better deinstall it as often some parts of those software firewalls are still active when turned off.
The only option that does affect access of wireless clients to the LAN is the "AP Isolation" option on the "Advanced Wireless Settings". That should be off.
Another thing you could try if you like: do a configuration backup on the working router and restore it to the faulty one. Maybe there are some settings that don't match and that you cannot configure through the web interface. Have you ever used a 3rd party firmware on either of the routers?

Window 8.1 system unable to access network shares via VPN connection

Is there something inherent to Windows 8.1 that prevents it from accessing shares on a domain?
I know that it cannot join a domain, but does that also mean that it cannot access shares which are on a domain?
My problem is that I have several user that are running windows 8.1 that are connecting to our network via a VPN.
The users have domain accounts but their computers as windows 8.1 cannot joined to the domain.
So to access network shares they have to use their domain credentials to create a VPN connection.
Once connected the user can RDP to systems on the domain using their domain accounts, so I know that their user names/passwords and permissions are correct. They can access these systems using the computer name, so I don't feel that I have a DNS issue.
They can see the shares on our file server, but when they try to access their departments shared file, they receive an access denied message. There are a few shares that are completely wide open, shared to all users and all departments but they cannot access
those shares either.
You can ping the file server, from the the client when they are connected to the VPN but you just cannot access any of the shares.
So...
I am thinking that it has something to do with windows 8.1 and not being able to join a domain, but I cannot find anything to explicitly support this thought.
Other users running a variety different OS (windows 7, OSX, Linux) can all access the shares without any problems via the VPN, so I am a little stumped.

I have done some more testing and oddly enough I can map a drive if I use the IPaddress, but not the computer name, when checking the check box "connect using different credentials"and providing they users domain credentials.
This seems to point to a DNS issue, one would think, but I can hit the file share server by name \\fileserver.dev.lan
I can see all the shares, so dns seems to be fine right?
So I don't understand why I can map a drive using do the IPaddress and not the machine name, but yet I can see and ping the server by name?
When I try to create a mapped drive by machine name I receive the following message:
Windows cannot access \\fileserver.dev.lan\all
You do not have permissions to access \\fileserver.dev.lan. contact your network administrator to request access.
But if I use the \\x.x.x.x\all using the very same user and password I get connected with no problem.
This only seems to happen on windows 8.1, which leads me to think that has something to do with OS.
I am thinking about upgrading to windows 8.1 pro, but I don't want to go though the hassle and expanse is the OS is not the problem.

Unable to access CIFS shares using SSL Web portal

Hello,
i have deployed Cisco Clientless Web VPN on my ASA5515.
I'm having an issue when I try to browse a file server (access CIFS shares) from the WEB VPN portal. I am prompted for login, and after logging in I get the "Error contacting host" immediately. it's seem like a bug on ASA ? i saw that on Cisco Web site : bug CSCsl94183
I already DONE those things :
1- reload the ASA
2- upgrade to the latest software release
3- test different web browser ( Firefox, IE, Chrome)
1- ASA Platform is 5515 running latest software release (9.1.4)
2- File server running Windows 2008 R2
3- Clients is using Firefox.
4- When I establish SSL VPN connection using Cisco AnyConnect I have no problems accessing files or folders on the same server.
NOTE : I have 2 other CIFS server running Window 2003 and there is no issue. the issue is happening ONLY with the server running Window 2008 R2

I've also seen this exact problem. We have several Windows 2008 R2 servers, one of our Domain controllers has been migrated to 2008 R2. I can access shares on the Windows 2008 R2 domain controller, but not a deicated (member) file share server.

Unable to access a share - beachball...

Colleague has raised an issue - he is unable to access a shared folder on our server.
He does Command K, enters ip number of server, clicks connect,
enters name and password
Gets a window offering volumes to mount - as soon as he clicks on one gets 'beachball of death'...
I can login from another site using his name and password and sail through to volumes OK...
He can Ping the server's ip number successfully...
Any thoughts on reason?
Any solutions...
Thanks - he's on 10.4.6 (probably should upgrade to 10.4.11), server is 10.4 os x server

If you can access the site through www.megaproxy.com/freesurf/ or a similiar web proxy service, then Verizon is giving you access. The Web Host probably has an out of date filter.
He can either add your subnet to his network, or you can simply turn off your modem for four hours (there is a lease time on the ip address that doesn't expire for 4 hours) and then turn it back on. I usually tell folks to do this at night when they go to bed. Basically just unplug the modem and don't plug it back in until the morning.
OR if you want it right away, you can try chat support or Call Verizon, and don't bother telling them your problem AT ALL. just ask for tech support and ask if they can release your IP Address, or break the dhcp lease.
you should have your modem powered off when they do that, and don't plug it back in for AT LEAST 3 to 5 minutes before plugging it back in.
If you plug it in immediately, then you run the risk of that IP address coming right back to you, but if you give it a few minutes, it will most likely go back into the dhcp pool and get assigned to someone else, and you will be in perfect shape to get a new ip address.

Unable to mount samba share file for xbox 360

I want to be able to stream music from a directory in my arch linux computer (xfce4) to my xbox using samba on a local network using ethernet cables and a router not connected to the internet. I've been able to get samba to startup and I see the folder "share" in my network tab in thunar, but I am currentlly unable to mount that folder. I haven't been able to get the xbox to recognize my arch computer or visa versa.
Here is the configuration I am running as of now:
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = XBOX
# server string is the equivalent of the NT Description field
server string = "Samba Server"
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = user
[share]
comment = music for xbox
path = /home/ricky/Music
browsable = yes
guest ok = yes
read only = yes
create mask = 0777
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
I did a chmod -r 777 on the ~/Music directory already and I still haven't been able to mount it. I have read in the wiki that creating a /mnt/xboxshare directory, for example, would actually mount the share directory and allow the xbox to share. However, I would rather just use the directory I specified instead of creating another directory. Has anyone else experienced this problem or have any advice for me?
Here is some additional information:
I do have to input a password when I issue this command
$ smbclient -L \\RG_ARCH
Enter password:
Domain=[XBOX] OS=[Unix] Server=[Samba 3.6.8]
Sharename Type Comment
share Disk music for xbox
IPC$ IPC IPC Service ("Samba Server")
rg Disk Home Directories
Domain=[XBOX] OS=[Unix] Server=[Samba 3.6.8]
Server Comment
RG_ARCH Samba Server
Workgroup Master
XBOX RG_ARCH

I was wondering whether it had anything to do with the network I was using. The router I am using can't access the internet and I am using the basic 192.168.1.X setup with 255.255.255.0 as the mask.
My computer has an ip of 192.168.1.2 and the xbox has an ip of 192.168.1.3. However, I am still unable to ping the xbox or even see it show up in the network. I did notice that whenever I am using another router that is connected to the internet, I can see other windows based computers in the network tab in thunar under "windows network"
Also, I do have a username and password associated with the samba setup.. so I assume maybe that has something do with it. I checked the permissions of the share folder and it was root:root with read and write permissions. I know samba is working fairly well.. but for whatever reason I can't get the xbox to connect even while it is on the same local network.

Windows machines unable to access smb shares

I know many people are having problems with smb on osx server, but my issues seems very basic, so I will try to ask for help here.
Basically, I have set up a single folder for sharing on a Mac Mini running OSX Mountain Lion Server. Directory services are provided by a WIndows 2003 server, and I have joined OSX Server to that, and am able to see all AD users and groups correctly. I have checked the boxes specifying I wish to share as afp, smb and webdav and also made shares accessible to guests.
Now, if I use a mac client, I can correctly browse the afp and smb shares, and the latter work via finder and smbutil as expected, including access via AD users, connection and file transfer.
If, instead, I use a windows client (I tried both Win7Pro and WinXP), while being able to ping the osx server machine, if I try to "explore" (entering \\hostname in explorer) the shares I get a "Network error: impossible to access ..." (approximate translation, sorry ). I tried both using the hostname and the ip address, always getting the same result.
If I try via prompt with "net view \\hostname" I get a System Error 53 (Unable to find network path).
Does anyone know if I am doing anything wrong?
Thanks
Christian

I have done some further testing, and I can report that occasionally, I am able to connect from a windows 7 professional machine by issuing the following command:
net use z:\\hostname\share /user:DOMAIN\username
mostly this command returns a 53 system error, but sometimes I am asked for the user's password and am then able to access the shared folder for a brief time.

Unable to access network shares

In our enterprise environment we have a home share with approx 20 folders viewable to all staff with different folder accessible to different departments. One of our users has an issue when switching from a wired to wireless network connection
on his laptop he is no longer able to view/access the folders from the home share and can only view/access one particular folder. This also happens when he is at home accessing via VPN.
TIA for any ideas as to what may cause this.
Hank Vare

In our enterprise environment we have a home share with approx 20 folders viewable to all staff with different folder accessible to different departments. One of our users has an issue when switching from a wired to wireless network connection
on his laptop he is no longer able to view/access the folders from the home share and can only view/access one particular folder. This also happens when he is at home accessing via VPN.
TIA for any ideas as to what may cause this.
Hank Vare
I assume the user has a clean install of Windows?
I rolled out 8.1 which has better sharing, I recall a few problems with 7 when out in the field
Corsair Carbide 300R with window
Corsair TX850V2 70A@12V
Asus M5A99FX PRO R2.0 CFX/SLI
AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
G.SKILL RipjawsX DDR3-2133 8 GB
EVGA GTX 6600 Ti FTW Signature 2(Gk104 Kepler)
Asus PA238QR IPS LED HDMI DP 1080p
ST2000DM001 & Windows 8.1 Enterprise x64
Microsoft Wireless Desktop 2000
Wacom Bamboo CHT470M
Place your rig specifics into your signature like I have, makes it 100x easier to understand!
Hardcore Games Legendary is the Only Way to Play!

[SOLVED] Suddenly unable to mount samba share using cifs

I have a home server running ArchLinux, hosting an SMB share. My client box is also ArchLinux, both are up to date, running Linux-ck 3.9.2-2-ck. Prior to rebooting both machines around twenty minutes ago, the share mounted fine for months.
Here is the extent of the "verbosity" I receive from mount:
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Here is my fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# UUID=71066ae2-40ec-4125-9db7-d04b6a04f712
UUID=71066ae2-40ec-4125-9db7-d04b6a04f712 / ext4 rw,relatime,data=ordered 0 2
# UUID=172faa6a-9cca-4d9e-a0b9-a5da3ea81922
UUID=172faa6a-9cca-4d9e-a0b9-a5da3ea81922 /boot ext2 rw,relatime 0 2
# UUID=65023815-33fc-4ebd-b245-65683201fbcf
UUID=65023815-33fc-4ebd-b245-65683201fbcf /home ext4 rw,relatime,data=ordered 0 2
UUID=1a23d461-fa2b-4ea4-8e58-e7efba3f3bed /media/Storage ext3 rw 0 2
//ARRAY/Array /media/Array cifs credentials=/home/xaero/.smbpasswd,iocharset=utf8,uid=1000,gid=1000,nounix,sec=ntlm 0 0
I have tried any number of different options on that final line defining this share now:
I have tried //array/array (which is what it was originally) and //ARRAY/Array (which is case-sensitive) as well as any combination of using my credentials file (which used to work) or user=,pass= as well changing my credentials file to use quotation marks around my password as it has special characters. I've also read of using sec=ntlm fixing mount issues, but in my case it did not. I'm kind of scratching my head here as passing --verbose to mount yields zero additional information... the uid and gid entries were necessary in the past to mount this share, however I have tried both with and without them, to no avail.
I rely on SMB in lieu of sshfs as there isn't a stable sshfs implementation for Windows users, which there are some on my network; I also find for whatever reason SMB happens to be faster.
Last edited by Xaero252 (2013-05-19 21:45:30)

I'm not exactly sure what fixed this... I looked at the configuration file to make sure I hadn't missed it being updated, and it was in the new format; everything setup correctly (I remember having to edit it not long ago to fix something, probably for the update which you mentioned) I reverted my fstab back to the way it was before (making backups is good) and restarted the smbd on the server numerous times... at some point it just started working again. I wish I had a more concrete answer for documentation sake, but I was literally just rebooting/restarting services in desperation with little to no config hacking between and suddenly things clicked. I'm also no longer running the sec=ntlm option..
Thanks for reminding me to check my config though, when I updated I had forgotten to enable user restriction (guest was enabled, and certain directories weren't user-specific)

WD MYBOOK LIVE - Unable to access "Public" share by browsing from Windows Explorer: A solution

My Problem: While trying to browse my Public share over the local network with windows explorer (the standard file browser) I was presented with a dialog box asking for a user name and password. None of the configured username and password combinations worked. My Solution: I found a tutorial at the following link, http://community.wd.com/t5/My-Book-Live/GUIDE-Fix-Dashboard-Errors-3xxxx/m-p/513954 which instructed on how to perform a factory restore without losing data. I was reluctant to try this because I was still afraid of being at risk of losing my data. Looking around, I found a script called setSharePublic.sh which allowed me to reset the status of my 'Public' share to public. I ran the script and it worked without a loss of data. I can now browse to my public share over the network with Windows Explorer. I followed the referenced tutorial all the way through step 4. The new step 5 is as follows: 5) Now at the MyBookLive:~# prompt you are going to type
/usr/local/sbin/setSharePublic.sh Public And I abondoned all further steps. I was able to browse on in without waiting or rebooting. It might be useful to note, though I am not sure if it is of any consequence, that my computer is on workgroup HOME and my WD MY BOOK LIVE is on the same workgroup.

Hello and welcome to the WD community.
Thanks for sharing this with the community hopefully this helps other users with similar problems solve it as well.

Unable to access samba share.

Similar Messages

Maybe you are looking for