Windows 7 can't connect to SMB share

Hello, my windows gaming PC won't connect to my shares on my mini server, the server is clean installed just 2 days ago and it worked at first but now it won't even ask for username password it just gives a message that it can't reach the IP address.
I have tried hostname, FQDN and IP and nothing works. but my 2 MacBook Pros have no problem at all, and is maxing the bandwidth of the LAN when transferring files.
I can post a wireshark log if that helps??

Have you tried turning on and off the Filesharing services?
I know sometimes the SMBX portion of OS X Server might crash... so you would have to retart services..

Similar Messages

Can't connect to SMB share on Windows server from only ONE mac

I have over 20 macs on my network. All are running the same version of the OS. (10.4.9) Almost all of the macs can connect, using SMB, to our Windows 2000 file servers...but only ONE of them can not. When I try from that mac, I get the following error:
"The finder cannot complete the operation because some data in "smb://myservername" could not be read or written. (Error code -36)"
This same mac that has this issue can connect to any of our other Win2K file servers and all my other macs can connect to the server that this mac can't...which is very confusing for me because that tells me that the mac is fine and the Win2K server is fine as well...
Any ideas?

-36 is a bit generic, but usually means the Windows® machine is denying because of bad Password. Have you tried deleting that particular reference/share in Keychain Access and redoing it?

Can't connect to SMB share after upgrade

Just upgraded to 10.9 Mavericks and can no longer connect to our SMB file share on the network. Several of us have tried connecting to it on this machine and all we get is
There was a problem connecting to the server "xxxxxxx.domain.com".
You do not have permission to access this server.
Anyone else having this problem?

I have been searching high and low since yesterday afternoon for an answer to this. My problem is not connecting to an SMB share (well, it was, as the old Cmd+K to connect to the SMB share would close quickly) but instead of the old Mac way of using Cmd+K and the IP address, I simply clicked on the available NAS SMB share under Shared and it is a massively fast connection. The old SMB connection would take minutes to open the next folder. So, connecting as you would under Windows helped fix that problem, BUT...
1. The NAS SMB share times out regularly and you have to eject & reconnect. Annoying.
2. Worse than this is I can not open any documents on the share, only navigate it. I have to copy paste the documents to my local ssd, manipulate, copy back. Any new file I copy on, or edit and copy on, the NAS SMB share I can navigate to and open. But if I try to click a pre-Mavericks existing file, I get "Can not open 'excel/word/acrobat.app' with the -36" error. Total BS.
3. Even more weird, if I click spacebar on ANY file on the SMB Share it will pop up in preview. Double click to open and error message.
4. If I copy a document attached to an email (Outlook 2011) to the server it is corrupt. If I copy the file to local ssd, then to the NAS SMB, the same file works perfectly fine.
This is completely ridiculous and needs a fix immediately. I'm going to try using Reinfire's link right now and see if that helps.
My NAS is a Netgear ReadyNAS 516 (linux/unix OS) I use in my office. Computer is MBPr March 2013.

Can only connect to smb share from Windows as "nobody"

I'm trying to share some folders on my Mac using samba. When I connect from Windows, I do not get asked for a username and password, and I get connected as a guest user (nobody). What do I do to get connected as a real user? I've tried playing with /etc/smb.conf, but I'm not sure what to change.

when you enable smb in haring system preferences on your mac, did you check the box to enable smb on a specific account?
if you did, when you initiate smb from windows try entering
smb://[email protected]
instead of
smb://mac.ip.address

Macs can't connect to SMB shares on Win 2008 Server

My office Macs are running MacOS 10.5.x
The Domain Controller was recently replaced - went from 2000 to 2008
The File Servers are running 2000 and 2003
The Macs were connecting fine when the DC was 2000 but after the change to 2008 when the Macs attempt to connect to either file server via SMB the connection times out. PCs are all fine.
The Macs are using the domain controller as the their time server. Binding to the domain seems to work fine.
Console logs show errors such as "Timed Out waiting on Response"
Help? What else can I check?
- C. Thomas

-36 is a bit generic, but usually means the Windows® machine is denying because of bad Password. Have you tried deleting that particular reference/share in Keychain Access and redoing it?

Active Directory, Windows 2003 SP2 Server and SMB shares

I have 10 new iMacs that will be returned and exchanged for 10 HP wintels if I can't resolve an issue with SMB shares in Mac OS X 10.4.9.
We had an old win 2000 server, and all the macs could mount their smb shares without problems.
Recently we upgraded to two new 2003 sp2 servers, one of them the domain controller, and we can't mount their SMB shares. I followed this http://weblog.bignerdranch.com/?p=6&page=3 and/or this http://allinthehead.com/retro/218/accessing-a-windows-2003-share-from-os-x to allow AD authentication, but still, I can't mount the 2003 shares (but can with the 2000 ones!!!).
If I enable SFM (services for macintosh) then I can mount the shares, but:
1) the network is slower (I supouse is due to appletalk implementation)
2) and worse, names with more than 32 characters or with some special characters are not allowed. This renders 30% of our archives unavailable with the AFP solution.
I also used all the authentication methods (Plain text apple, plain text windows, etc.) but no one works.
I have now 10 days to find a solution, or all "my" macs will dissapear forever.
Please, some advice or point to documentation.
G4, G5, iMac Intel, Mac Book Pro, etc Mac OS X (10.4.9)

Do you just want to mount arbitrary share from the win servers or do you want the macs to be bound to AD?
The first requires the steps from your second link (allinthehead.com) but the latter (bind to AD) requires things like proper use of DNS, time synchronisation for kerberos to work and proper configuration as described in your first link (bignerdranch.com).
Here are some more links for the latter (AD intergration):
http://www.bombich.com/mactips/activedir.html
http://www.afp548.com/article.php?story=20051202151540574&query=ad-od
HTH
-Ralph

Can't connect to DFS shares from machines not part of the domain

I'm not sure if this is by design, but we can't connect to DFS shares from machines that are not joined to the domain. We can't even map a drive using credentials of a domain account.
Is that how DFS is supposed to work?

Hi RJO22,
I did some research on this topic, and got a conclusion:
Clients that belong to a workgroup can only access the DFS namespace if the name resolution mechanism that is in place can locally resolve the domain name
https://social.technet.microsoft.com/Forums/windowsserver/en-US/c3214a4c-8088-446c-ba4d-643d5baf87cc/how-to-access-dfs-namespace-from-a-standalone-windows-2003-server
Regards,
Alex Zhao
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Lion can not connect to smb if use root login

I found if use root account login lion, that can't connect to smb but use other account ok.who can help me take a look?

This might help. I have a Seagate Dockstar (Pogoplug w/samba) with attached drives connected to my network that was easily discoverable with Bonjour in Snow.
From my experience -
I got the SMB share working (sort of) in Lion 10.7
While the network hub and connected drive(s) won't automatically appear as a Connected Server, or Bonjour Computer I was able to find the Dockstar by going to -
Go/Connect to Server and then enter it's specific info - smb://fabx2d09fe (my device's actual number was different than this).
The dialog pops up for name and password - or connect as Guest. I couldn't remember if I had set these so tried Guest and was able to access/mount the drive on the desktop and sucessfully read/write to/from it.
I may have to always connect to recent servers to get the thing to mount so it's not as automatic as Bonjour in the sidebar - but it does work!
This mostly solved the issue for my needs....maybe it would work for yours?

Does Lion support connecting to SMB shares?

Hi there,
Has anyone else had issues connecting to SMB shares since upgrading to Lion?
I am unable to connect to any previously accessible shares hosted on local Linux or Windows servers.
Thanks,
Bob

For those of you trying to access SMB shares, I found a free and easy solution.
Since a lot of people report they are able to access their NAS using apps other than the Finder itself, I decided to look for a free Lion-compatible File Manager to use instead of Finder.
I have found muCommander ( http://www.mucommander.com/ ) and indeed it works fine. All I did was click on the button highlighted bellow, go to "bonjour services" and select my NAS. It prompted me for my username and password and voilá, it works fine.
I keep Finder for everyday use and just load muCommander when I want to access the NAS. At least now I don't have to start my WinXP VM anymore just to access it.
Hope it helps you all.

Windows can't connect to shares on Lion Server

I can't connect any windows machines (XP, Vist, or 7) to a Mac Pro running Lion Server. When attempting to connect, the windows user is prompted for credentials, and nothing entered in this box works even the server admin account info, once entering account credentials, it comes back with NAMEOFWINDOWSCOMPUTER\USER as if it's trying to sign into a domain, which we don't have domains.
I can't seem to find anything relevent when searching...

There are a couple things you can try:
1.\ go to the apple server, sys prefs, sharing, selct file sharing and then select option. from there make sure the both check boxes are selected. then select done.
2.\ while you are there, in the shared folders section, selct the folder you would like to share (or add if its not) and make sure the user is in the users pane that you want to share the folder with.
3.\ restart your windows machine to make sure it forgets any passwords you may have put in.
4.\ if it still doesnt ask for a user account go to map network drive. and select the option to put another username and password in. for the user name user SERVERNAME\username - ensure the servername is in CAPITAL letter...
hope this helps...

Can't connect to Samba shares after upgrading

Hi,
I recently upgraded to Samba 3.6.0-8 (among other things, including a new kernel 3.0-ARCH), and all my shares have become unavailable from Windows 7. I can't connect to any, nor can I see the shares list. My Arch box has essentially become invisible as far as CIFS shares go. I can still ping it normally, and access it through SSH, so it doesn't seem to be a major network issue, this is specifically with Samba.
I have since tried changing my workgroup in Samba, downgrading to 3.6.0-{1,4}, disabling firewalls, changing Win7's security settings, and restarting several times, to no avail. Nothing has changed with my Windows box, I only performed a major upgrade to Arch (it is currently up-to-date).
I don't see any relevant errors in the Samba logs, and I can browse the shares just fine locally in Arch, I just can't see them from Windows.
Anyone have a clue?
Thanks,
IM

Is your arch server configured to allow samba traffic? With the recent removal of hosts.allow and hosts.deny, I wonder if this could be the issue? Do you have ufw or iptables? I know you said you disabled the firewall, but it wasn't clear if that was on the client or server.
Scott
edit: here's the ufw rule I use (/etc/ufw/applications.d/samba):
[Samba]
title=Windows file and printer server for Unix
description=Tools to access a server's filespace and printers via SMB
ports=137,138/udp|139,445/tcp
Last edited by firecat53 (2011-09-21 18:18:59)

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.

[solved] Can't connect to samba shares

This is probably my fault, but for the life of me I can't figure this out. I started out trying to get usershares to work by following the wiki at https://wiki.archlinux.org/index.php/samba, and I am unable to connect to the resulting shares either from the local host or from my netbook. It tells me permission denied. I then tried creating a public share with guest access, because I couldn't get the usershares to work. I am unable to get that working either. I have
chmod 777 -R
the folder I am sharing, as well as the
/var/lib/samba/usershare
folder. Please help. Here is my smb.conf:
#======================= Global Settings =====================================
[global]
workgroup = OSHANNON
server string = MDSHANNJARO
hosts allow = 192.168.1. 127.
log file = /var/log/samba/%m.log
max log size = 50
security = user
map to guest = Bad User
guest account = nobody
dns proxy = no
usershare path = /var/lib/samba/usershare
usershare max shares = 100
usershare allow guests = Yes
usershare owner only = False
#============================ Share Definitions ==============================
[Bleach]
path = /mnt/Data/Bleach
read only = no
guest ok = yes
I tried adding the nobody user since there was no users listed when running
pdbedit -L
using
pdbedit -a -u nobody
and just pressed enter for the password field. This did not help.
testparm says
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[Bleach]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
[global]
workgroup = OSHANNON
server string = MDSHANNJARO
map to guest = Bad User
log file = /var/log/samba/%m.log
max log size = 50
dns proxy = No
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = No
usershare path = /var/lib/samba/usershare
idmap config * : backend = tdb
hosts allow = 192.168.1., 127.
[Bleach]
path = /mnt/Data/Bleach
read only = No
guest ok = Yes
Last edited by mdshann (2014-03-04 06:01:04)

uninstalled samba, reinstalled it. deleted old config file. created new config with just the contents that the wiki states is necessary for usershares to work. the current smb.conf looks like
[global]
usershare path = /var/lib/samba/usershare
usershare max shares = 100
usershare allow guests = yes
usershare owner only = False
added my user to samba using
pdbedit -a -u mdshann
started smbd and nmbd and enabled both. tried to share a folder, caja says samba is not installed. use yaourt to search for caja and find package mate-file-manager-share. installed said package, killed and restarted caja. shared folder and told it to add permissions automatically. checked the boxes to allow guest and to allow users to change files. still I cannot connect. just for reference, I have used the wiki article sections from the beginning of the article through adding a user. I did not use the creating a share section as I want usershares to work through MATE and CAJA. It creates the share and it is visible on the network, I just can't connect to it.
Pretty much the same as what I tired before, with the same result. Only difference is I haven't tried manually creating the share through smb.conf, but that didn't work before either. No reason to think it will work now, the problem was the same whether I used the gui usershares option or adding the share to smb.conf.
I was able to get samba working with a very similar config file as in my first post, on arch based manjaro on my server at work. I did not enable or use usershares at work, but creating the shares in smb.conf worked just fine. Why will the same procedure not work on arch? Same packages for the most part, manjaro just adds a few. In fact, when I set up samba on manjaro, I used the arch wiki article, as Manjaro's wiki is sparse. Main reason we used manjaro at work was the speed of installation was much quicker, and we needed the machine back up quickly so we could start backing up our customers data. (I own a PC repair shop.)
On a side note, this community has served me well in the past the few times I have have issues since I started using arch 5 years ago. Why my post has gone so long without a reply other than being chastised for trying to call attention to a 3 day old unanswered thread is beyond me, but I am not thrilled by it. It has now been a full 2 weeks since my original post. I have never had this issue before, and if I can't bump or somehow call attention to my thread I am unsure of how to get help. Am I supposed to keep posting new threads on the same issue? I would think those would get closed rather quickly if I had. Should I post nonsense on this thread, I mean anything other than the word bump. A discussion of cat videos maybe?

Can't Connect to PC share Error -41

Untill recently I have been able to connect to PC shares (Mac & PC running XP connected to a router) but it has stopped working. PC to Mac is still ok but I'd rather sit at the Mac than the PC...
My method (which has worked for at least 2 years):
In finder Go-Connect to server - enter server address (in my case) smb://192.168.0.2 then click connect. A window pops up "SMB/CIFS File system authentication", click OK, another window pops up "Select the SMB/CIFS shared volume you want to connect to", select the PC share (I have several) & click OK [all ok so far]
Then a window pops up: "Sorry,the operation could not be completed because an unexpected error occurred (Error code -41)."
Can anyone help with what is wron & a fix? What is error -41?
Any help is much appreciated.
Thanks
John

With some further research I have found an answer in a post from a year ago:
http://discussions.apple.com/thread.jspa?messageID=3005537&#3005537
The problem is at the PC end (surprise anyone?) - probably related to Norton Internet Securuty.
The following registry hack fixed the problem:
http://www.michna.com/kb/WxNotEnoughServerStorage.htm
I had to increase the IRPStackSize value to 20.
Hope this helps someone.
Cheers
John

Can't connect to samba share via VPN

Hello all,
I am looking for an answer for few days now and still can't manage to fix it. I found two workarounds in the meantime, but it's not what I want!
My case:
Cisco vpn on one side and Mac vpn client (native). I can connect alright, can't only mount samba share. Via console I got invalid argument error, but when I go to finder > go to server it's just processing (no error). Left it for few mintes and nothing happened. I have a windows on virtual machine and I can mount samba alright. One more thing. I created a new user, logged in and it works! ****.
Can anyone say where should I look? What can be the problem on my old account? Don't want to switch and change all the things now, there must be a way to fix it...
Hope someone can help
Thanks in advance,
Regards,
Jake

Hi Richard,
Thanks for interest. It's a windows share 2003 smb. It's a company network. As I said its not the case of VPN itself.
About the new user, that's a yes, it's same username as my samba share name, but even tho it's the same it needs my authentication. For the more, when I am with my mac at work and connect via cable I can access everything alright from my old account.
How can VPN block me when I can access it from my windows virtual (which is not the same as my work username). I can access it from new user, I would say its not the case of VPN blocking me there, I guess it's something I have changed over the years with my previous VPN settings.
I have direct access to VPN and I know firewall is off right now as we are testing it, so its for sure my mac settings...
Question is where do I find it:)

Windows 7 can't connect to SMB share

Similar Messages

Maybe you are looking for