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

Question

Level 1

0 points

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.

iMac4,1 (Intel Core Duo), Mac OS X (10.4.11)

Posted on Oct 6, 2008 6:44 AM

Reply

Answer 1

BDAqua

Level 10

250,259 points

Oct 6, 2008 12:22 PM in response to killtheclock

Hi,

Try it in Terminal to connect...

http://docs.huihoo.com/darwin/opendarwin/articles/osx_smb/ar01s02.html

You can also try "escaping" that dash character...

http://www.macdevcenter.com/pub/a/mac/2002/07/02/terminal_5.html

Reply

Answer 2

killtheclock Author

Level 1

0 points

Oct 8, 2008 8:01 AM in response to BDAqua

Hi BDaqua,

I've been nearly sure that I tried this before, but it was some time ago, so I tried again.
Just using mount_smbfs, escaping the the "-" using a backlash, avoiding the name a all using the ip address. All methods yield the same result: I'm asked for the password, and once entered, I get the message "mount_smbfs: tree connect phase failed: syserr = Permission denied". And I'm sure that username and password are correct, both working very well when using it from my windows laptop, or even inside the terminal server window (of an MS-Windows server) that I've open on my Mac. Username and Password do not have special characters (just for information).

Cheers,
Kurt.

Reply

Answer 3

Oct 8, 2008 6:23 PM in response to killtheclock

Kurt--

If it's the name of the server that has the dash in it, (and not the share that's being exported), try using the IP address of the server.

charlie

Reply

Answer 4

killtheclock Author

Level 1

0 points

Oct 9, 2008 12:39 AM in response to Charles Minow

Hi Charlie,

yes, it is the Servername with the dash in it. Maybe my recent post was not clear enough.
I tried this variants in terminal using mount_smbfs:

smb://workgroup;username@netbiosname/share
smb://workgroup;username:password@netbiosname/share
smb://workgroup;username@ip-address/share
smb://workgroup;username:password@ip-address/share

Similar in Finder - Connect to Server. Same result everytime: "Permission denied"

Regards,
Kurt.

Reply

Answer 5

Oct 9, 2008 8:22 PM in response to killtheclock

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

Reply

Answer 6

killtheclock Author

Level 1

0 points

Oct 10, 2008 12:03 PM in response to Charles Minow

I just re-opened this issue, it was 1/2 a year ago when I last investigated. At that time I found information about the problem with the dash; but now I cannot find it again. Anyway, your question made me reconsidering wether I jumped to conclusion. So I read the threads you've provided and they made me looking into the log files. Sure enough, the error message is different:
"iMac kernel[0]: smb smbnegotiate: server configuration requires packet signing, which we dont support"

Windows Server 2003 defaults to packet signing. I'll have to ask my sys-admin to switch it off, maybe he will if it is not a requirement for him. I could not find anything about a workaround from the client side.

Thanks for your help,
Kurt.

Reply

Answer 7

BDAqua

Level 10

250,259 points

Oct 10, 2008 12:30 PM in response to killtheclock

If IT doesn't/can't, then look into ADmitMac...

http://www.thursby.com/products/admitmac-eval.html

Reply