SMB Mount to Windows Server 2003- Can't connect

Find the command you typed into Terminal to force plaintext passwords, and post that here.
Then have a look at the 2003 server and:

The following options should be set in the Security Options section of the Local Policy.

The settings dealing with SMB and Secure Channel are of particular importance if Microsoft Networking and Resource Sharing are to be used.
Note: These policy settings just create and set registry keys (that is, they are just a pretty interface for the recommended registry keys settings).
Digitally Sign Client Communication (Always) Disabled
Digitally Sign Client Communication (When Possible) Enabled
Digitally Sign Server Communication (Always) Disabled
Digitally Sign Server Communication (When Possible)

Domain Security Policy is reached at:
Control Panel>Admnistrative Tools>DomainSecurityPolicy.
Pop open Local Policies>Security Options
Your settings will be in MicrosoftNetworkClient,
and
DomainMember, and the settings I discussed above are either enabled or not. Try enabling the 'when possible's, and 'notconfiguring' the "always".

These are settings from SmallBusinessServer 2003. Your settings may be slightly different.
You should then undo the nsmb file you created on the mac, and see how things go.
You "shouldn't" have to restart server to make those changes take effect, but it may not happen immediately. Not sure how long it takes for Server to make that change 'stick'.

Hi Matthew. Is this the first time you've seen the "Alias" error? If that's what you've been getting all this time, you should have mentioned it. We could have saved you a few days worth of troubleshooting. Read on.

I think you should try connecting using the Finder menu. Leave the Alias alone for a bit.
GoMenu>ConnectToServer...
in connect text box,
enter:
SMB://[servername or_IP]/Shared_Folder_onServer {connect}

You'll probably get a prompt to pick a folder, and to enter your Domain/UserName/Password

There may be a renegade keychain in your KeychainAccess...but if you're binding to the Domain...should work.

Sigh,

I've Googled and read countless posts here and have utterly failed to get my iBook Tiger 10.4.3 system to mount a PC shared directory. Neither have I been able to get the PC to mount my iBook shared directory. The PC is running W2K.

I get a variety of error messages, depending upon what I am doing and on which machine, all of which have been mentioned here.

Heck, I can't even FIND smb on the Tiger system! I've tried the manual mounts (from a console it can't even find smb and from the finder it just fails with an error suggesting the PC's Directory Services aren't enabled (they are.)

So much for PC interconnectedness that everyone talks about. I'm a UNIX hack from way back but the PC/Mac connection stuff has me licked.

Is there a troubleshooting chain that is well known that I can follow?

thanks all,
DLC

Heck, I can't even FIND smb on the Tiger system!

What are you trying find ? Samba binaries ? Try
$man smbclient
$man mount_smbfs

So much for PC interconnectedness that everyone talks
about. I'm a UNIX hack from way back but the PC/Mac
connection stuff has me licked.

Is there a troubleshooting chain that is well known
that I can follow?

If you can't make it work on your own, I would suggest starting a new thread, and be specific about your network setup, about what you have tried, specific about the errors you have received, etc.

No 'all encompassing' guides that I am aware of. Since Apple uses a tweaked version of samba, almost any troubleshooting guide/document on connecting linux to windows shares using samba is fairly useful.

Unfortunately, when it doesn't 'just work' out of the box, it helps to have a working knowledge of how samba and of windows CIFS/SMB work and talk to each other.

Hello,

I need help big time. I changed my settings using Terminal by creating the same nsmb.conf file as mentioned above:
Open the Terminal (/Applications/Utilities/).
At the prompt, type: sudo pico /etc/nsmb.conf
Press Return.
Enter your password when prompted, then press Return again.
You should see an empty file and a "New File" notice at the bottom of the pico window. If you do not see the "New File" notice, this file already exists.
Enter the following into the file so that it appears as follows:

[default]
minauth=none

Save the file (press Control-O), press Return, then exit pico (Control-X).
Type: sudo chmod a+r /etc/nsmb.conf
Press Return.
Restart your computer.

I don't have access to the Windows server, and I want to undo sending passwords in the clear. Can I just open the nsmb.conf file in pico and delete the contents ([default] minauth=none)?

I'm getting the following message in my console log:
mount_smbfs: session setup phase failed: syserr = RPC struct is bad

I upgraded to 10.4 and now cannot connect to my company's smb servers. THIS IS A VERY BAD THING. I just recently converted from OS9, and I have no ability to go hacking around in Unix-land to customize my system. I need help immediately. Whoever in Apple decided to put this update out is one supreme @#$#$!. It's hard enough to get a Windows based company to spring for a Mac, and now I'm off the network.

Any help at all would be greatly appreciated!!!!

Regards,

Zoar

Hmm sorry if I was a bit testy there. Apparently there's no editing or deleting of posted messages. Mia culpa!

My NT password was reset twice by our IS tech, and now I can see the network. I don't know if that is what really fixed the problem, so I'd like to find out anything more about this error. As it stands, I could come in tomorrow and have the same problem when trying to access our corporate Windows servers.

-Zoar

Mac Dual G5 Mac OS X (10.4.3)

Hmm sorry if I was a bit testy there. Apparently
there's no editing or deleting of posted messages.
Mia culpa!

My NT password was reset twice by our IS tech, and
now I can see the network. I don't know if that is
what really fixed the problem,

Yes, it is.

so I'd like to find
out anything more about this error.

If you simply googled for it, you would have found the same info I found, that the error indicates you recieved a message like "your password has expired, please change it" that your machine didn't understand.

You fixed your password, and now everything is happy.

Instead of complaining about apple, complain to MS and ask them to open up thier documentation for SMB/CIFS so the rest of the world doesn't have to resort to reverse engineering to talk to MS via SMB.

And , BTW, you can edit your messages.

Hello,

I did Google the error, and I wasn't getting a message about an expired password. I was getting the same error that Matthew Smith got, and I followed the same instructions that he did. That did not fix my problem either. My password did not expire, so I have no idea what the heck happened to prevent me from getting on the company network.

I've used Macs for over 20 years, and I'm new to OSX. I don't see the big whoop about the OS. It's much less intuitive to find anything in. I never had any of the instability problems people claimed with the older OS. The only postive is that it's faster, and I've noticed some slowing already when I run some Applescripts. The reason most get a Mac is not to have to fuss with things like terminal mode. Next we'll be having to set BIOS (maybe when they move to Intel). I'm a big Apple fan, and I'm constantly defending them against many Windows users. I'm the only one using a Mac in a large department, but when I can't connect to the network, it doesn't look good. Also, Apple touted the seamless integration of Tiger with the Windows networking environment and after dealing with Thursby's Dave to connect, I was expecting better.

On the editing deleting issue, I actually meant to say there wasn't any way to delete a post. I've been on other boards where you could go back and delete a post.

Widgets are cool though.

Ciao!

Hello,

I did Google the error, and I wasn't getting a
message about an expired password. I was getting the
same error that Matthew Smith got, and I followed the
same instructions that he did.

But you also mentioned the error in your logs, which is what I was referring to, not the -36 error.

http://www.google.com/search?q=%22syserr%3D+RPC+struct+isbad%22

That did not fix my
problem either. My password did not expire, so I have
no idea what the heck happened to prevent me from
getting on the company network.

I supposed that you were getting a message like your password is about to expire, or a similar message that samba was not expecting, based on similar errors I saw while googling. The fact that your password was reset and now you can connect lends evidence to support that, no ?

Anyway, if you are connecting successfully to your windows network now, I imagine that's the most important part 🙂

After our IT dept had updated the server software from W2K to Windows 2003 Server I wasn't able to connect via SMB to that server anymore (Err -36, no problem before with the old W2K server and no problem with AFP).
Interestingly, I had a file left in the "last documents" part of the file menue in MS Word that had been saved on the server while it was still W2K. When I click on that file (from within Word) Word opens it and afterwards the SMB connection to the server is established. Magic - or is there some easy explanation to it?