Connecting to SMB server

Hi, Im running 10.4.8 trying to connect to a server using the Go>connect to server thing. Ive typed in the server nname and protocol correctly which is smb:\\192.xxx.xxx.xxx and the machine tries to connect. Except it THEN puts AFP:\\ in front of what Ive typed in so you get AFP:\\SMB:\\192. etc which is not going to work obviously.
How do I stop it doing this. I can connect just using AFP no problem, but I am then restricted to short file names etc.

I can connect to a local server using SMB, but I am not sure why! Two things to try:
use / instead of \
make sure the SMB port (TCP 445) is open
AK

Similar Messages

Unable to connect to smb server

I'm not a very technical person, so please bear with me.
I have a mac in a windows enviroment. I used to connect to smb server where I had my "private" hard disk space. Or a user interface if you wish. It's the same "place" that I can connect to via Remote Desktop Connection. Path looked like this:
smb://xx.xx.xx.xx/user$/username
It worked fine until I upgraded to OS Lion. Now I get "You do not have permission to access this server".
Now I *think* the problem might be that the password to my username has been changed, but I am unable to enter new password for my username. I tried deleting keychain, but I don't get username/password prompt. Just the error msg.
Another possibility is that its a "lion" problem..
Please help.. Ive googled and asked around, but no one knows.

Yes it used to work fine both ways.
I can ping the Windows XP Home box from the mac. I can access the mac files across the network fine from the Windows box. I just can't connect to the Windows box using smb://ipaddress
All I can think of that has changed was the upgrade to 10.4.8, and I am not sure if the problem started then or before, because I didn't need to share files with Windows for a while...
Interestingly enough, I can also print to a shared printer on the Windows box...
So again, about all I cannot seem to do is connect from the mac using smb

Can't connect to SMB server

Hi! I have trouble with connection to my smb server on debian. When I try to connect from "connect to server" menu, I get this error: URLs with the type "smb:" are not supported". Now I can connect only with bash command. But few days ago all worked from GUI.
In system.log I got this (I try connect from PathFinder & Finder):
Feb 25 00:30:37 macbook Path Finder[44402]: An error occurred while trying to mount "smb://sofico"., err: Error: -36
Feb 25 00:30:41 macbook NetAuthAgent[72818]: inErrorInfo = { AuthType = Server; ErrorNumber = 45; ErrorType = 4; Scheme = smb;

Fix this by reinstalling OS X

Can no longer connect to SMB server after upgrading to Lion

We have a MacBook Pro that was running 10.6.8. The user upgraded to Lion, and can no longer connect to a Windows 2008 file server. (We have two offices connected through a hardware tunnel, but i do not think this is the issue.)
We have tried to connect in the Finder (smb://[email protected]/). It asks for usr / pass, and then just hangs on "Connecting to server"
We can ping, have tested these credentials on other computers, and tried other credentials on this computer, to no avail. Furthermore, we installed a fresh copy of Lion on another computer, and successfully connected, so I don't think the issue is with Lion itself.
There must be something from the previous install that did not "upgrade" properly, but I don't know which file / setting it could be. It is system-wide setting, as we have also tried another user account on this same Mac.
We've also run Onyx to fix permissions, clean out all caches, etc.
Any idea what file i can change, modify, or delete?
Your thoughts would be much appreciated.
Thanks.

Yes, but the issue is not with Lion directly; there seems to be something with the upgraded system, perhaps a legacy setting or pref... I've scoured the system to no avail. I'm actually about to reinstall 10.6 - wasted too much time on this issue.
Thanks for your help.
D

Cannot connect to SMB server if the name contains a dash (-)

Hi,
maybe someone has a workaround this: When the name of a server contains a dash "-" then one cannot connect to the share, even by using the IP address instead of the name.
I would like to access the file system in the company I'm working for from home. The company uses MS-Win. The server names are like "xyz-asd". The easy way (for me) would be that my company changes the naming convention for the servers. But the IT guru rightly says that he is standard conform and don't see a reason to change for the personal needs of one user. By searching the Internet I could confirm that it is a bug in the Mac implementation, but could not find anything about to fix it or work around it.
Anybody here has a clue?
Cheers,
Kurt.

killtheclock wrote:
yes, it is the Servername with the dash in it. Maybe my recent post was not clear enough.
Oops, I missed that part of your post but I see it now...
Why are you sure it's the dash character in the name? Can you post the link that made you think that? There was a problem when Tiger first came out that was something like this, but it was related to password encryption.
I did a search with your log error and found a thread here at the Apple Discussions that might help. MacNN's forums have another thread with possible help.
Sorry I wasn't more help. But maybe something in one of those threads will help.
charlie

When connecting to file server via smb shows no space available! Help!

We are running an XSERVE with Mac OS X 10.5.5 and have multiple clients that connect to it (mac and windows).
For some reason yesterday one of the clients (10.4.11) when connects to the file share using the smb protocol shows up with 0kb available and he is not able to copy any files. Every other computer shows 4TB available. When I connect to the share on his machine using my credentials I get the same problem. However, when I connect using his credentials on my machine it shows up correctly with 4TB free. Also, when he connects via AFP it shows the full 4TB. Any idea what could be causing this?
(the reason he connects via smb is because for some reason the people on 10.4.11 experience very slow AFP transfers sometimes. If anybody knows whats causing this that would help too hehe) Thanks in advance to anyone that takes the time to help me.

If it is an identical machine, put the machine that works fine into target disk mode and boot the machine that is having issues from the other machines drive. That will eliminate most hardware issues.
My guess is it is a system file or a settings file in the users library. I have fixed several issues like this on computers that were running 10.4 I believe and think they were upgraded from 10.3 by someone else. The issue had something to do with permissions and files.
Try some of the following:
- create a new user on the computer and see if that user works. if so, it's something in the user folder (most likely User/username/Library/). If not, then it is something outside the user folder.
Try
- running a combo Update on the machine
- run disk utility file and permissions on the drive
- Backup the user folder and clone the drive that works onto this drive, and move the user folder over. (assuming you know how to do that, it is easy)
REGARDING Slow AFP - having the same issue with 10.4.11 Server. Most clients are Leopard. Intermittent, so hard to diagnose. Tried several solutions on this wait and see issue.

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?

When I connect to our server using smb:// can't copy files or edit names on server?

When I connect to our server using smb:// can't copy files or edit names on server?

Why not? What happens?
Do you get an error message? What does it say?

Users cannot connect over SMB 10.10.1 server.app 4.0 and 4.0.3

Hello,
I have an issue where users cannot connect to a server for files sharing over SMB.
Info:
All users on 10.10.1
2 Servers on 10.10.1
Server.app 4.0.3 but issue was also present using 4.0
SMB connection works when connecting to the OD Master
SMB does not work when connecting to the OD Replica ServerBut AFP works fine when connecting to the OD Replica Server.
I have destroyed and re-added the OD replica but that did not seem to help
This is what I see in the logs each time I try to connect(logs have been cleaned to remove client details:
Jan 9 14:37:12 server.pretendco.com digest-service[9961]: label: default
Jan 9 14:37:12 server.pretendco.com digest-service[9961]: dbname: od:/Local/Default
Jan 9 14:37:12 server.pretendco.com digest-service[9961]: mkey_file: /var/db/krb5kdc/m-key
Jan 9 14:37:12 server.pretendco.com digest-service[9961]: acl_file: /var/db/krb5kdc/kadmind.acl
Jan 9 14:37:12 server.pretendco.com digest-service[9961]: digest-request: uid=0
Jan 9 14:37:12 server.pretendco.com digest-service[9961]: digest-request: netr probe 0
Jan 9 14:37:12 server.pretendco.com digest-service[9961]: digest-request: init request
Jan 9 14:37:12 server.pretendco.com digest-service[9961]: digest-request: init return domain: SERVER2 server: SERVER2 indomain was: <NULL>
Jan 9 14:37:13 server.pretendco.com digest-service[9961]: digest-request: uid=0
Jan 9 14:37:13 server.pretendco.com digest-service[9961]: digest-request: init request
Jan 9 14:37:13 server.pretendco.com digest-service[9961]: digest-request: init return domain: SERVER2 server: SERVER2 indomain was: <NULL>
Jan 9 14:37:13 server.pretendco.com kdc[4802]: Got a canonicalize request for a LKDC realm from local-ipc
Jan 9 14:37:13 server.pretendco.com kdc[4802]: Asked for LKDC, but there is none
Jan 9 14:37:13 server.pretendco.com sandboxd[395] ([4802]): kdc(4802) deny file-read-data /private/etc/krb5.conf
Jan 9 14:37:22 server.pretendco.com kdc[4802]: Got a canonicalize request for a LKDC realm from local-ipc
Jan 9 14:37:22 server.pretendco.com kdc[4802]: Asked for LKDC, but there is none
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: uid=0
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: init request
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: init return domain: SERVER2 server: SERVER2 indomain was: <NULL>
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: uid=0
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: init request
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: init return domain: SERVER2 server: SERVER2 indomain was: <NULL>
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: uid=0
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: od failed with 2 proto=ntlmv2
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: user=SERVER2\\username
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: kdc failed with 36150275 proto=unknown
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: guest failed with -1561745590 proto=ntlmv2
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: uid=0
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: init request
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: init return domain: SERVER2 server: SERVER2 indomain was: <NULL>
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: uid=0
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: init request
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: init return domain: SERVER2 server: SERVER2 indomain was: <NULL>
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: uid=0
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: od failed with 2 proto=ntlmv2
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: user=SERVER2\\codywood
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: kdc failed with 36150275 proto=unknown
Jan 9 14:37:23 server.pretendco.com digest-service[9961]: digest-request: guest failed with -1561745590 proto=ntlmv2
I suspect the problem is to do with Kerberos and in relation to this server being an OD Replica.
I would really appreciate anyone's insight into this.
Thanks
Morgs

I have the same problem although I upgraded from Lion Server to Mountain Lion Server. The error appears to go hand in hand with this error.
userInit: CFPreferences: user home directory for user kCFPreferencesCurrentUser at /Network/Servers/fullyqualifieddomainname/Users/user is unavailable. User domains will be volatile.
I've read a number of things to try. A lot of people point to DNS being a problem, but I'm confident this is correct in my environment.

Folder looks locked when connecting through SMB on SL server

Hi,
After finding a workaround to another issue I'm having with AFP, I've decided to connect my clients through SMB. Being the guinea pig, I'm testing this on my mac first which is running SL 10.6.3, the Server is running 10.6.2. When I connect through SMB, the Share points doesn't show as a remote server, but as a folder, is that normal? Second, it has a locked sign on it has well as on most of it's content, which I can browse, even it it says it's locked or rather that I don't have the permissions to access its content. So how do I fix this so that I can see a regular mounted sharepoint, and that see the correct folder icon, or how do I fix the permission in SMB? I'm using ACL with the workgroup default for my main group in SL serveur.
TIA
Jeff

Just an update on this, I just figured out that you had to change the POSIX permission, or at least I that was the problem since it fixed it. Now though, the folder permission gets a bit more tricky. I can create a folder from computer A, save a document to that folder from computer B, open, edit and save from computer A that same document. But If I create a document on computer A, in a folder created also on computer A, I can't drag and drop that document in the finder to a folder created by computer B. Weird huh?
Any help would be great on this!
TIA
Jeff

SMB connection attempt switches to WebDAV unexpectedly when connecting to OSX server

With Windows 8.1, I can connect to my OSX 10.9.5 Server share point by opening File Explorer, typing: \\<fqdn> and hitting return. I will be prompted for server credentials and when I enter them, I will see the share point.
With Window 10, if I do the same thing, instead of seeing the shareppoint, I see a blank Windows Explorer screen with "This folder is empty".
I contacted Apple with a tcpdump from this and they said that Windows 10 is attempting to connect over HTTP instead of SMB:
ACTION: Windows is handling the connection incorrectly by attempting to use Webdav instead of SMB.
STATUS: As with any other 3rd party integration cases, we attempt to identify an issue as either an issue to a 3rd party product, or to identify and isolate the issue in
the Apple product.
In packet 64 the client sends an SMB 1 negotiate request (expected).  In packet 66 the server responds in SMB 2 with the SMB 2 features it supports
(expected).  In packet 67 the client sends the SMB 2 negotiation request (expected).  In packet 69 the server responds with the SMB2 negotiation response (expected).
Normally at this point the client will send an authentication attempt in SMB 2 using one of the authentication types provided by the server in packets 66 or 69.  Instead
the Windows client sends a tcp connection reset in packet 70 (unexpected).  In packet 74 the windows client initiates a connection over HTTP (extremely unexpected).
The above pattern repeats several times in the tcpdump.
The mac server never presented any HTTP information in the SMB packets.  This appears to be a purely Windows 10 issue.
If I connect to the server by typing: \\<fqdn>\sharepoint -- then I do connect, but the OSX server does not indicate this is an SMB connection, so it must be a WebDav connection (which would be incredibly wrong...)
If this is a settings issue in Windows 10 that is forcing an HTTP connection over an SMB attempt -- can somebody point me where to look?

On Thu, 20 Nov 2014 17:04:11 +0000, steve maser wrote:
According to Apple, it appears that if the SMB server (in this case Mac OS X 10.10.1) has port 443 open, Windows 10 attempts to connect over that instead of over the SMB port.
Anybody looking at this one?
If you want someone to look at this you need to file it using the Feedback
tool, if you haven't already done so.
Paul Adare - FIM CM MVP
Actually, we have scientifically determined that Heisenberg did indeed
sleep exactly here. However, we have no idea whatsoever just how fast
asleep he was. -- Dave Aronson

SMB and VPN connected to Windows Server 2003

I have search the web for an answer on this problem, I've only found peoble with same problem, but still no solution :o/
I wan't to connect to my office (windows2003) from my OSX 10.4.2 at home. I've set up an VPN connection and can PING the server (and others) on the network. Works fine.
When I connect to the server via SMB://server/ I get a list with all different folders (or servers) I can connect to but I get rejected with the answer Bad name or password. Now to the funny part; I can connect in the Terminal using smbclient with the same user and pwd just rejected in Finder!!!
I've read about this problem on http://www.macwindows.com/tiger.html#052305a but I can't find a solution. Someone mentioned a bug with apple number #4108992 - Can anyone tell me where I can read about that? Or better - Where I can find a solution. (I've tried to erase keychain)
Rgds
/Johan

My school sets up our network disk space with access via FTP. I don't know if that is an option through your company. While I have to download files to work with them and then upload them again to the network space to access them at work, it does allow me to look at the directory structure. I use an FTP client (not the one built into OS X). This might be an option for you to check on with your IT department. (This also eliminates my need to use VPN.)
Hope this helps.
PB G4 15" Mac OS X (10.4.3)

Can connect via SMB but not AFP....

Hi Guys,
Firstly, please let me apologise in case im being really stupid (highly likely! )
I have a mixed environment in which i have some iMacs (running Mavericks) and some Mac Pros (Running Mountain Lion 10.8.5). When connencting to the XServe using AFP, some get an error. I will go throught the steps i follow.
- From Finder, Go>Connect to Server..>afp://10.***.**.**>Connect
- I enter the login credentials and select Connect
- It gives me the option to select which volume to mount. I select Volume 1 and select OK
- Error - There was a problem connecting to the server "10.---.--.--". You do not have permission to access this server
When trying to access the server suing SMB instead of AFP (using the same credentials) it connects fine.
The issue with SMB is that for some reason, some of the folders wont show through SMB (no idea why)
The problem is affecting one imac on Mavericks and two Mac Pros on Mountain Lion. If i attempt to login using SMB on any machines which work fine with AFP, they will connect but after that, they wont revertback to AFP. They get the same error as above.
Any idea whats causing this?If any of the above causes confusion, feel free to shout at me and i will try to clear anything up.
Really appreciaste the help guys!
Pami

You'll need to connect your modem to your AEBS WAN port, configure your AEBS with the Airport Admin Utility, setting up the PPOE to properly log into your modem connection.
You should set up your mac to us DHCP (not PPOE).
THis should allow you to use either the ethernet port or wireless from your AEBS.
I hope this helps!

How to auto-connect to external server upon startup?

Is there a way that a user could by-pass "Connect to Server" and have the workstation auto-connect to an external, but in-house server each time the work-station is booted up? Also, is there a way to have it connect to this server without having to enter a password each time? Thanks in advance.

Is there a way that a user could by-pass "Connect to
Server" and have the workstation auto-connect to an
external, but in-house server each time the
work-station is booted up?
after you mount the share, drag the icon to sys pref -> accoutns -> login items
Also, is there a way to
have it connect to this server without having to
enter a password each time? Thanks in advance.
use apple+k to connect to the share, enter the share name as:
smb://your-user-name@server/share
keychain should remember the password for you.

There was a problem connecting to the server ... OS 10.8.4 + WD NAS

Dear all,
first my configuration:
iMac from mid 2012, MacOS X Mountain Lion, 10.8.4, iPhoto 09 v. 8.1.2 - all software updates done and up-to-date
MacBook Pro late 2011, MacOS X Mountain Lion, 10.8.4
NAS WD My Book World Edition II (white light), 2 x 1TB (configured RAID : 1TB mirrored), original firmware (01.02.14 with MioNet built on Thu Feb 9 14:11:48 CST 2012 ) NFS, AFP enabled
a win 7 laptop and plenty of other devices
everything on a LAN with GB router + WiFi
I have my iPhoto library on my iMac, but the photos (the originals) stored on the NAS. I have the option "copy photos to library when importing" disabled. So I guess iPhoto has a reference / link in the library to the original files.
Everything used to work fine until some weeks ago. Not sure what happened but suddenly I got the error message "There was a problem connecting to the server ... Check the server name or IP address, and then try again. ..." when I tried to import photos stored on my WD NAS. When I want to display any photo stored on the NAS - same thing.
Now I guess I have a bunch of gray hairs more while trying to get this fixed.
I tried so many of the tips posted everywhere including booting in save mode, deleting the .plist files (first I actually tried to clean them using Xcode first before deleting them), etc. I cleared out KeyChain. I removed all recent entries (folders) and recent servers from the "history". I tried to connect as guest or named user. There are also no "logIn items" pointing to the NAS. I even tried to disable / enable AFP + NFS on the NAS, not to mention countless restarts of all the machines
One other thing I noticed: Before that problem occured I was able to select the NAS in Finder and it would show me all the shares. When I selected one of them it was mounted automatically. When I select it now I get "connecting" for a loooong time and then "Connection Failed". Most of the time (not always!) however I am able to get in via "Go -> Connect To Server - smb://<nas server name>). And suddently after that also selecting the NAS in Finder shows me all the shares! Hoever even this not in 100% of all cases. I can replicate this from the iMac and the MacBook.
I do use an external HD for TimeMachine to back up my data (directly connected via USB). No issues there.
Not I really don't know what to do any more
Do you have any ideas? Did anyone ever get a response from Apple with a useful solution that really hit the core of the issue?
Thank you!

SOLVED!! and I want to share the solution which worked for me with everybody here. Ultimately I had to install nettalk 2.2 on my NAS as described here: http://mybookworld.wikidot.com/netatalk2-2-on-whitelight . A nice description on how to do that can be found here: http://forums.macrumors.com/showthread.php?t=1102423 .
One last remark: When asked about the "DHX2 login process", I opted to install the original version, so I can confirm this one works too.

Connecting to SMB server

Similar Messages

Maybe you are looking for