Problem accessing smb share since change to Windows 8

Hy,
I have a smb share folder on my router (I connect a pen and is shared in the network), with no password.
I am able to access from Windows 7 and Linux, but not from Windows 8.
The reported error is:
The device or resource (SERVER) is not set up to accept connections on port "The File and printer sharing (SMB)".
Which is obviously wrong, since I can access it from other OS.
How can I solve this or get more information on the underlying issue.
I've read several threads in here about similar problems, but nothing worked in my case (services are running, smb-cifs is active and there's no error about IPRStackSize and I turned off firewall and antivirus).
Thanks in advance

is your network public or private? in order to access shares you need to be on a private network in windows 8.
Change Network Status Using Settings Charm
1. Press Windows Key + I combination on the keyboard to reveal the
Settings charm. Now in the bottom, click on the Network icon there. Alternatively, you can click on the
Network icon in the notification area on the
taskbar.
2. Now in the Networks section, right-click over the network whose status you’re looking for to change, select
Turn sharing on or off.
3. Finally, you have the options to select between Private and
Public status for your network. If you select Yes, turn on sharing or connect to devices, the network will be switched to Private status.
<ins class="adsbygoogle" data-ad-client="ca-pub-5950002284129980" data-ad-slot="6708462760" style="width:336px;height:280px;display:inline-block;"></ins>

Similar Messages

Hp photosmart plus 210. Since changing to windows 8, I no longer have the options of "no scaling".

since changing to windows 8, I no longer get the options of "no scaling", my paper patterns are printing too small. they printed great before computer change and change to windows 8. no longer have the option of "no scaling". Where can I go to choose that option

Hi AbbyZiva
I understand since updating to Win8 you don't have the "no scaling" option available.
Did you uninstall and reinstall the printer after doing the Windows upgrade?
Here is a url for the drivers for the Photosmart Plus 200.
http://www8.hp.com/us/en/support-search.html?tab=2#/qryterm=photosmart%20plus%20210&searchtype=s-001
If you need more assistance just let me know.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Gemini02
I work on behalf of HP

Trying to access SMB share, can read but not write, I use the domain account to autenticate and domain account has access to the share. its a samba domain and im a Windows Admin by trade.

I have two I Mac's Intel i7 models.
I have some problems getting them to write files to SMB shares.
The domain user account I use when requested to enter when i first try to connect to the share seems to go though without a problem and it presents me with a list of mounts (shares) I select one and the folder opens, I can read files and copy them but I cant write to any of the folders.
I have also mounted the network locatiosn to a folder from the terminal while also specifying a user name and password to use but this also doesnt allow the specified user account to write data to the share.
I have confirmed the user account can write to the share by having the user do so from a windows box.
any help from any of you mac guys would be great!!!!
Im a windows fan boy / Windows Server based Network Administrator and am slowly becomming a fan of your macs (mainly due to the Unix terminal access letting me realise there is more control to be had than most haters would lead you to believe).
Peace Out

I should add that I originally formatted the problematic drive for FAT32 from the Mac, but then the WinXP computer couldn't see the drive when I plugged it in directly via USB. That's why I went with Seagate's utility to format it.

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.

Mac Pro accessing SMB shares on a windows server. After being left on all night, the MP gets "file unavailable" messages when opening files on the share.

Windows Server 2003 accessed by several PCs and Macs without previous incident. This one Mac Pro after it's been left on all night (running jobs, or just left idle), and a user tries to reconnect to an SMB share, can go to Finder, Go, Connect to Server, enter the Server info as normal, login as normal, view the directories and files as normal, but as soon as they try to open anything they are given one of the following messages:
"Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example, \ /). (<filename>)" - when opening a word document
"<filename> could not be found. Check the spelling of the file name and verify that the file location is correct. If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted." - when opening an excel spreadsheet
Note that these messages are popping up AFTER the user has double-clicked on them to open them. So the files are certainly there and correctly named (and contain only letters, numbers and underscores). After restarting the Mac Pro, the error messages are gone and the files can be accessed without problem. Would like it so that they can connect to the server without having to restart every day.

Windows Server 2003 accessed by several PCs and Macs without previous incident. This one Mac Pro after it's been left on all night (running jobs, or just left idle), and a user tries to reconnect to an SMB share, can go to Finder, Go, Connect to Server, enter the Server info as normal, login as normal, view the directories and files as normal, but as soon as they try to open anything they are given one of the following messages:
"Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example, \ /). (<filename>)" - when opening a word document
"<filename> could not be found. Check the spelling of the file name and verify that the file location is correct. If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted." - when opening an excel spreadsheet
Note that these messages are popping up AFTER the user has double-clicked on them to open them. So the files are certainly there and correctly named (and contain only letters, numbers and underscores). After restarting the Mac Pro, the error messages are gone and the files can be accessed without problem. Would like it so that they can connect to the server without having to restart every day.

Cannot access SMB shares from Windows boxes in AD domain

Hey folks
I've needed to tackel this for sometime, but Santa is bringing me a dual core G5 and the urgency just increased.
I have an Active Directory domain and all of my macs are successfully joined and get Kerberos tickets upon login. I can access any shares I need from OS X -> windows but NOT the other way around.
I did finally noticed that only local user accounts seem to appear in the accounts list in the sharing pref pane. So I have figured out that I can access any users folder with that one account- OUCH! What I need is access control based on the user.
For instance if I want to share ~jdoe and jdoe is a mobile account and an AD user then if I am logged into windows as [email protected] then I should be able to access the share on the mac. Conversly I should not be able to access ~jdoe with the mac's local admin account and pass.
Do I need to change my smb.conf to reflect AD and if so, where/what?
Also, do I need to map UIDs to anything? And, is that a security risk?
Thanks!
-N

Hi SpaceBass, have you looked into sharepoints or into Netinfo manager. I have been playing around with sharepoints and it does let me enter non local users into the sharing prefs- albeit manually. Only thing is , depending on the number of macs you have, it could be a long and tedious job entering it all by hand. Netinfo may have an easier way, I'll do some more digging and post back.
Cheers.

Windows computers can not access smb-shares in Lion

I have updated von SL to Lion Server. Now, I don't gave Access to my Windows shares from any Windows Computers. If I connect a Windows share u.e. froom Windows 7 Workstation I will see a window with username and password for the share. But the username und password from lion for this share will not work. It was no problem in SL. Any idea?

To get this to work on windows 7 I...:
Start > Computer
Disconnected my mapped netowrk drive that would not connect
Selected the Map network drive button in the toolbar at the top
Typed in the folder location manually (if you try the browse it will fail)
Selected Connect using different credentials
Selected Finish
On the credentials screen that pops up:
User name: <SERVER\username>I found that my server name had to be in capitals (/private/var/log/krb5kdc/kdc.log helps you know exactly what it is)
Password: <your password>
Select Remember my credentials
Select OK
After this i found no issues access any of the shares on the server and everything came back to life

WRT350N - V2.00.20: Write access problem to SMB share from Mac OS X 10.6.2

Hi everyone, i've got a problem trying to write a file on the SMB share of the wireless router WRT350N from a MAC OS X 10.6.2 Finder (but also from a Leopard).
I've got no problem neither reading from mac or writing from win.
I've tried to write by cp command from terminal without problem.
Sorry for my english and thanks everyone,
Mr Proc

Same issue on my WRT610N V2. I am using iMac Intel running 10.6.2. Error -36 prompted when copying files to the USB share disk from the Finder. Working fine when on PC running XP.
Another issue is DDNS can't report the router IP to DynDNS.com although it status that the update is successful and completed. After updated, the router's IP is still different to the IP shown on the DynDNS.com. I need to type the IP manually to the DynDNS.com
Hope the new firmware would fix these problems.
Thanks
Message Edited by rickysuper on 11-27-2009 12:00 AM

All of the sudden our Mac OS X 10.7.4 operating systems are very slow to access SMB shares on our MS2008 file server

Monday all of our OS X Lion Macs can access SMB file shares on our file server and we come in Tuesday morning and now they take at least 1 minute to pull up the file share and sometimes longer. Windows PC's are immediate when connecting to the same shares. I've seen where others with different versions of OS Xhave this issue but what gets me is it happend all at once to machines that were working perfectly the day before.
I've also looked into changes on our servers and as far as I can tell there have been none.
Does anyone have any ideas? Thanks....

This solution worked for me!
I had a MobileMe account with iDisk configured on my MBP even though I never actually used it. The night they officially shutdown MobileMe the next morning I could no longer connect to my work's SMB file shares (Windows server shares). I found a work around based on some other support threads. If in the "Connect to Server" address field in Finder I specified my crendentials (i.e. smb://username:password@server/) then it worked perfectly fine. This told me it was a crendential issue. Simply deleting the saved server crendentials in KeyChain Access did not resolve the issue. No matter what I would did it would not prompt for login crendentials. Since my Mac login is different than my work domain login I was dead in the water without manually specifiying (not a permenant solution).
After finding this thread I did the following steps and it resolved the issue 100%.
1. Open Terminal
2. cd ~/Library/Preferences
3. ls .GlobalPreferences.plist to verify file exists in that directory
4. rm .GlobalPreferences.plist to delete file
5. ls .GlobalPreferences.plist to verify file no longer exists
4. Go to Force quit to relaunch Finder
5. Lauch "Connect to Server" within Finder and all was good, server connects perfectly
Thank you very much DavidRSewell!!!!

Problem with SMB share

Hi!
I have a problem when connecting to a SMB file share on a Windows 2003 R2 server (also acting as a Domain Controller for the Active Directory domain) using OS X 10.5.2.
I've just reinstalled Leopard to rule out any problems with messy configuration on the client, but the problem persists. The newly installed Leopard client is not a member of the AD domain at the moment.
When connecting to the server share (with cmd+K in Finder), I have to login using a AD account. The share is after successful login accessible through Finder and I could traverse the folders and read / copy all the files on the share. I could also save smaller files (less than 16 KB) to the server.
However, if I try to save a larger file (more than 16 KB) the files gets created on the server share, but stays a 0 KB. The access to the server share freezes during 60 seconds and the "Copy" window just tells me it has copied 0 KB of the file so far. No data seems to be written to the file at all.
After Finder gives up, the "Copy" windows tells me that "The operation cannot be completed because you do not have sufficient privileges for some of the items".
From time to time Finder has also disconnected the share during problems, and OS X has crashed on me in kernel panic four times when testing. I haven't been able to track down the action triggering these errors yet.
The shares on the server works just fine when using the same username/password from a Windows XP client machine.
I don't see this problem when mounting a share from a Windows XP client in Leopard.
What could be wrong here? Is there some setting on the Windows server that has to be done to work with Leopard? (I've read about the SMB signing, but Leopard shouldn't need the signing to be turned off, should it?)
At the moment I'm having a hard time using the shiny new MBP at work, so any help on this would be highly appreciated!
Best regards, Jonas Mixter

I have an issue with OSX Leopard (10.5.2) , where by I can't write to NTFS shares on W2K3 servers with SMB signing turned on and IPV6 disabled for the interface.
To recreate the issue:
Create a folder named test that contains two files one named ._test.txt and test.txt on OSX and copy to an SMB share on W2k3.
This results in spurious errors about permissions and locked files.
Copying a file larger than 4k results in the error:
"The operation cannot be completed because you do not have sufficient privileges or some of the items."
Using mount_smbfs from a shell on OSX results in the error: "Permission denied"
host:~ user$ mount_smbfs //user@server/share /Volumes/test-smbmount/
Password:
host:~ user$ cp test.docx /Volumes/test-smbmount/
cp: /Volumes/test-smbmount/test.docx: Permission denied
Using smbclient from a shell on OSX results in SUCCESS!!!
host:~ user$ smbclient \\\\server\\\share -U user
Password:
Domain=DOMAIN OS=Windows Server 2003 3790 Service Pack 2 Server=http://Windows Server 2003 5.2
smb: \> put test.docx
putting file test.docx as \test.docx (784.7 kb/s) (average 784.7 kb/s)
smb: \>
There is an alternative solution if you do need to drag and drop in your gui world, it'll cost you $120
link: http://www.thursby.com/products/dave-eval.html
I have mailed the developer as he has obviously identified the root problem of the issue and I urged him to share his patch/resolution with Apple in the interests of the user community and a darn nice thing to do.I had a response form the developer to my request. I sent my workaround solution to the developer and stated that in my opinion the pricing for the software seems unnecessarily high based on the functionality it provides and way above what I would be willing to pay to resolve one small issue.
<developers response>
Pricing is a difficult topic to discuss -- but if you have no use for the product, any price is too much. As for reporting bugs to Apple, they'll listen to customers much sooner than they'll listen to developers. And they have some of the brightest engineers I know. If you report the bug to them, they'll likely have it fixed in the next update.
</developers response>
I couldn't find away to report the bug myself so I had a friend do it for me. The response I had back from Apple was less than satisfactory.
They believe that the issue is to do with NTFS streams and that a file containing ".com.apple.smb.streams.on" needs to be created and placed into the root of shared volumes. This is not a fix!
If you want to prevent writing the "Apple Double" files to a remote share, enter the following into a terminal:
$ defaults write com.apple.desktopservices DSDontWriteNetworkStores true
Problem still exists.
ref: http://docs.info.apple.com/article.html?artnum=301711
<apple double description>
ref: fhttp://docs.info.apple.com/article.html?artnum=106510
Before Mac OS X, the Mac OS used 'forked' files, which have two components: a data fork and a resource fork. The Mac OS Standard (HFS) and Mac OS Extended (HFS Plus) disk formats support forked files. When you move these types of files to other disk formats, the resource fork can be lost.
With Mac OS X, there is a mechanism called "Apple Double" that allows the system to work with disk formats that do not have a forked file feature, such as remote NFS, SMB, WebDAV directories, or local UFS volumes. Apple Double does this by converting the file into two separate files. The first new file keeps the original name and contains the data fork of the original file. The second new file has the name of the original file prefixed by a "._ " and contains the resource fork of the original file. If you see both files, the ._ file can be safely ignored. Sometimes when deleting a file, the ._ component will not be deleted. If this occurs you can safely delete the ._ file.
</apple double description>
I am not the only one this issue. A quick peruse on http://macwindows.com/ will show that numerous people are suffering and numerous workarounds have been suggested. Sadly none of which work for me. Each work around is stranger than the previous. Such as disabling IPV6 and updating Daylight Savings Time.
The issue lies with the samba integration. I am primarily a Gentoo Linux user and this kind of bug would have been resolved almost instantly if present in open source software.

Can't access smb shares after 10.9.5 upgrade

After the upgrade to 10.9.5 (from 10.9.4) I can not anymore access my smb shares on a NAS server (Thecus N3200PRO) dispite the upgrade says that it "improves the reliability of accessing files located on an SMB server". It had the exact opposite effect with my system.
The NAS server is visible, but after I log in no files or folders are shown (finder window is empy). Also to disconnect the smb share it takes much longer than usual.
To access it with cifs protocol does not help, neither.
Also the workaround by Reinfire (Michael Larson in Can't connect to SMB share after upgrade, to use smb1 instead of the upgrade) does not help at all.
Any solution out there?
-- thanks

hi there,
just a wild guess, but have you tried to connect via Terminal?
/sbin/mount_smbfs //userid:password@ip-of-server/name-of-share
or
/sbin/mount_smbfs //userid:password@dns_name-of-server/name-of-share
You need to have administrative privileges on your Mac to execute said command successfully.
For additional information you can enter (while in Terminal):
man mount_smbfs
and
man nsmb.conf
Glad to hear the problem is solved

Issue accessing smb share on Imac os x 10.7

I am have some issues accessing our company smb share. The problem i am having is that when i click on a folder it does not show any content, but if i eject the network drive and reattach it it works.

try this:
(run this in Terminal.app, replace <YOUR_DROPBOX_FOLDER>)
rm <YOUR_DROPBOX_FOLDER>/.dropbox.cache/dropbox-upgrade-3.4.3.tar.bz2
curl -L -o /tmp/Dropbox-darwin-update-3.2.9.tar.bz2 'https://www.dropbox.com/download?plat=mac&meta=1&build=3.2.9'
mv /Applications/Dropbox.app /Applications/Dropbox_backup.app
mkdir -p /Applications/Dropbox.app/Contents
tar -C /Applications/Dropbox.app/Contents -xjf /tmp/Dropbox-darwin-update-3.2.9.tar.bz2
chflags -R uchg /Applications/Dropbox.app
rm -r ~/Library/Application Support/Dropbox/Dropbox.app
chflag uchg ~//Library/Application Support/Dropbox
sudo dot_clean /Library/DropboxHelperTools
(system password might be asked after last command. Type Your password and press Enter. Letters of the password won't be displayed while typing)
some explanation, and future changes when more problems arise:
https://gist.github.com/peter-kolenic/7718b6d75a13c17effd0

Smb shares on OSX to Windows not working after upgrade

After upgrading to Maverick and OSX server 3.0 SMB file sharing is broken. I connect from Windows 7 to OSX SMB shares. Some shares work others only work with some folders on the share. Most folders display an error when trying to access the folders from Windows.
I checked file and folder permissions on OSX (finder and ls -l) permissions are the same.

@thePod7, your suggestion on Setting the Lan Manger Authentical Level worked! Only thing missing is the instructions on how to Set the Lan Manager Authentication Level. So I've included it below. Hope this helps someone else having the issue!
On command line....
1. Enter “gpedit.msc” in the Start Search box.
2. Open “Computer Configuration”/Windows Settings/Security Settings/Local Policies/Security Settings.
3. In the right pane, enable the following policies:
Network access: Allow anonymous SID/name translation
Network access: Let Everyone permissions apply to anonymous users
Also please disable the following policies.
Network access: Restrict anonymous access to Named Pipes and Shares
Network access: Do not allow anonymous enumeration of SAM accounts
Network access: Do not allow anonymous enumeration of SAM accounts and shares
Change the following policy:
Network security: LAN Manager authentication level
Change the value to “Send LM & NTLM - use NTLMv2 session security if negotiated”.

Problems connect to vpn since upgrading to Windows 8.1

Since upgrading from Windows 8.0 to 8.1, although normal web access is OK, I can no longer connect to vpn services - receiving error 619. Using another laptop running Windows 7 SP1 on the same router I can connect without any problems. Please help. I have
limited technical knowledge with networking.

The instructions below are included on the site. These do not make sense in Windows 8.1. Right clicking on the 'vpn connection' does not give any additional pop up options (so no properties to change). I also cannot find any options to change the
'Security' settings as described. These instructions are for Windows 8.0, is 8.1 really that much different?
"........Click on the
monitor icon on the bottom right-hand corner;
Right–click on the “VPNForUK.COM” connection, and choose “Properties” from the menu.
Select “Security” tab and for “Type of VPN” select “Point to Point Tunneling Protocol (PPTP)”;
Click “OK”;
Click again on the monitor icon on the bottom right-hand corner, and click “Connect” to “VPNForUK.COM”;
In the
next fields type “vpnforuk” as VPN username and VPN password found from website and click “OK”;........"

Domain machine Can't access administrative shares c$ admin$ on windows 7 x64 network path was not found

Hello,
I'm unable to access admin shares on a windows 7 pro x64 domain machine, i've tried the following:
. Disable IPV6
. LocalAccountTokenPolicy (32 and 64 bits set to 1 or zero with restart)
. Disable UAC
. Disable firewall
. LmCompatibilityLevel set to 1
I can ping the machine, remote desktop and everything BUT access any shares on it, i've created additional shares for testing and still can't access it, by name or ip, even using the 127.0.0.1. Please help as this issue is driving me nuts.
PS: Windows 7 Enterprise doesn't have this problem

Believe it or not, it's UAC causing the blockage of accessing any hidden $ drive share in Windows 7. At least, for me.
For a new PC built here I tried everything I could find. Disable antivirus, firewall, defender... changing network share settings.. nothing worked.
Thing is, its been working on multiple old PCs so I tracked down network profile and other differences between new and old, only one I found was that I'd disabled UAC on the old PCs (all win7 pro). Disabled UAC on the new PC, rebooted as required to completely
turn it off, bam! can now access root drive shares via the hidden $ as always.
More advanced admins could probably track down the specific registry settings changed by UAC and isolate the one blocking LAN connecting to hidden drive $ shares. I'm not delving any deeper.
Oh, btw, turned firewall, antivirus etc back on and it still allows access over a LAN.
(UAC - User Account Control for those not familiar with the acronym)

Problem accessing smb share since change to Windows 8

Similar Messages

Maybe you are looking for