smb shares on servers inaccessible after mountain lion upgrade?

This is what I got using your syntax. 192.168.6.241 is Win2008-R2 server

smb://192.168.6.241:Administrator

That does produce the same result as smb://192.168.6.241

The following string smb://Administrator@192.168.6.241

got this. The username box is already filled with Administrator

If I also type the password smb://Administrator:secretpassword@192.168.6.241

I get this

and... smb://Administrator:secretpassword@192.168.6.241/Share

I'm connecting to the remote Win2008 server through a VPN

set right system time on mac and windows server!

I also have a very weird issue. I am new to OSX and have ML running now. Everything is fine except ONE thing.

I can access my SMB shares, access other computers, cross-platform, File Browser iPad, I tested whatever I was able to find.

However, there is one thing that I can't get to work, no matter what I do!

I own a QNAP NMP-1000P multimedia player on my TV, and this thing works great with Windows. I can access all my shares, and as with any Samba, I just need an IP, path, login and password.

However, when the same paths are shared on Mac, my Qnap can't access them.

I tried everything I could think of, including creating an alternative user with sharing rights and sharing only those folders.

Keep in mind, all shared shares, with any kind, work from other windows notebook and Apple device, but when it comes to accessing those same shares under the OSX, it fails, miserably and consistently.

Anything I can do to make it work?????????

I guess you already updated QNAP firmware.

Maybe the problem is related to the new OS X SMBX that superseded SAMBA since OS X Lion appearance.

The QNAP user guide reports that you can also use NFS as a protocol to access remote sharing.

NFS Manager is a graphical front end to manage NFS share on OS X.

Indeed, the firmware is latest.

SMBX - possibly, however weird that W7 machines *can* access it.

However, in the meantime, as you noted, I used NFS Manager, and that worked out! (I wasn't aware of NFS existing under OSX until yesterday evening, I didn't even know what it is, I'm very new on this "UNIX" market, but learning fast!)

Also alternatively, I can use SMBUp to create shares that are also accessible.

Weird enough, both solutions work flawlessly, only the built-in one fails.

A single question pertaining to NFS:

If I assign for example /Volumes/Data HD/Movies to the NFS, I can read it with the QNAP, however I don't like the "unfriendly" name. Is it possible to map it to like /Movies or something? Similar to Samba, where I share a folder, and it is later accessible via xx.xx.xx.xx/Movies?

Kosta88 wrote:

SMBX - possibly, however weird that W7 machines *can* access it.

SMBX is Apple's implementation of SMB protocol and is not SAMBA.

SMBX only support SMB2 while dropping support to SMB1.

A single question pertaining to NFS:

If I assign for example /Volumes/Data HD/Movies to the NFS, I can read it with the QNAP, however I don't like the "unfriendly" name. Is it possible to map it to like /Movies or something? Similar to Samba, where I share a folder, and it is later accessible via xx.xx.xx.xx/Movies?

I never used NFS so I cannot answer to this question. It's not clear what do you mean with "unfrendly name", but I suppose that's the way NFS announces share points.

Alright, so it's Apple again who f*cks us, lol.

Is there a reason to drop a support for SMB1? I don't know much about it, but a simple quesiton if there was a reason?

Well, imagine wanting to map a share on a device (Qnap) which doesn't have a keyboard, but only mobile-phone-alike keypad for typing in the name. Takes a while for each share, and I have about 5-6 of them. Once set up, OK, it's done, but looks terrible on the screen too. With Samba it would simply look like this:

xx.xx.xx.xx/Movies-NAS

xx.xx.xx.xx/Movies-Disk

xx.xx.xx.xx/Photos

xx.xx.xx.xx/Music-Router

xx.xx.xx.xx/Music-Disk

etc.

Now with NFS, it would look somewhat like this:

xx.xx.xx.xx/Users/xxxxxxx/Photos

or

xx.xx.xx.xx/Volumes/DataHD/Photos

etc.

It would be nice if I could map xx.xx.xx.xx/Users/xxxxxxx/Photos => /Photos.

So it would again look like Samba eg:

xx.xx.xx.xx/Photos

I hope now it's a bit more understandable.

Kosta88 wrote:

Alright, so it's Apple again who f*cks us, lol.

That's incorrect. Apple moved away from SAMBA because Samba 3 was released under GPLv3 licence which prevent Apple from bundle it in a commercial product.

Is there a reason to drop a support for SMB1? I don't know much about it, but a simple quesiton if there was a reason?

Also the latest Microsoft Windows 8 and Windows 2012 do not support SMB1 anymore. I gave a link in my previous post which explains the technicalities.

...

Now with NFS, it would look somewhat like this:

xx.xx.xx.xx/Users/xxxxxxx/Photos

or

xx.xx.xx.xx/Volumes/DataHD/Photos

etc.

It would be nice if I could map xx.xx.xx.xx/Users/xxxxxxx/Photos => /Photos.

So it would again look like Samba eg:

xx.xx.xx.xx/Photos

I hope now it's a bit more understandable.

Yes. I got the point 🙂, but as I told you I never used NFS and I do not know the working details.

Ah alright, I get it. Didn't know all those things, nice to learn more about it. So shortly said, if I had W8, I wouldn't be able to connect to my windows share from the QNAP, since it doesn't support SMB1?

About the explanation, sorry, I misunderstood 🙂

I will see on another forums maybe I can get an answer to that. Meanwhile, SMBUp is working fine, I can access everything.

Kosta88 wrote:

So shortly said, if I had W8, I wouldn't be able to connect to my windows share from the QNAP, since it doesn't support SMB1?

Right.

Samba supports smb v2 since version 3.5. Recent QNAP installations are running Samba version 3.6.3. This cannot be the reason for the non-working smb shares.

Nevertheless dsavi, the shares are working via SMBUp, they work with windows 7, they are *not* working with OSX native. I am now using NFS, via NFS manager as both are native to OSX and QNAP. Working well, except that it won't resume the movie when stopped, like it usually does with Samba. NFS is however much faster.

Samba 3.5 was released on March 1st, 2010 and contained an experimental implementation of SMB2.

QNAP NMP-1000P is approximately a mid 2010 product. I doubt QNAP was an early adopter of the new Samba version, and usually, updates for older products don't get major system enhancements during their lifetime.

I'm actually also quite happy to be away from Samba. It's quite slower and less responsive than NFS, for example start/stopping/fw/rew on MKVs on the Gigabit network is via NFS way faster than it's with Samba, even on the lowly device like DNS-323. The difference from the computer, be that windows or OSX, is like 3x faster when loading the movie...

Dear Alberto

I'm running a QNAP TS-112 here. This model constantly gets updates. So i can't tell about the NMP-1000P but my TS-112 shows the same problem with smb with samba version 3.6.3 running.

Today I've found the solution for my case. I've had the problem that the service stopped working after updating the QNAP firmware. Only SAMBA was running on the device, no netatalk (AFP) or NFS service.

In QNAP's admin panel, there is a directory in the navigation pane called "network services". In that directory the last entry is "network service discovery". I'm translating these entries from german, so maybe they are called somewhat different in proper english. However, under "network service discovery" you'll find a tab called "bonjour". Make sure, that the entry for SMB is checked, while the entry for AFP is unchecked. The service names given here are those you will see in the Finder. This solved the problem in my case.

I'll attach the settings page below.