Cannot connect to smb share on Windows server

[Norman S. Bard]

I have a Windows 2003 server which I am unable to connect to from any Mac in
the district. I can connect to any other server in the district, just not
this one. The error message I get is:
"Could not connect to the server because the name or password is not
correct"

Any help would be appreciated.
Norman

 

[Jim Seifert [MSFT]]

A couple possibilities: the server may be configured to only allow digitally
signed communications or you may not have rights to connect to this server.
Both will required investigation by a server administrator.

Here it is a related KB
http://support.microsoft.com/default.aspx?scid=kb;en-us;823659 (see #5) and
original thread and post from William.

Hi Larry!

This sounds like a common problem introduced with Windows 2003 servers.

Check out Item 5 on this page on Microsoft's website
<http://support.microsoft.com/default.aspx?scid=kb;en-us;823659>, which
refers to a domain and/or server policy you can change to "disabled"
from "enabled" to allow clients with older SMB software, such as Macs,
to connect.

Hope this helps! bill

--
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi,

I've gto a network with:
WIN SBS 2003 SERVER
Some PC's (Win 98)
1 Apple OS 9
1 Apple OS X (Panther 10.3.5)

The pc's and mac-OS 9 can connect fine.

When trying to connect with Panther
GO -> CONNECT TO SERVER -> afp://x.x.x.x/

I get a message like:
'Can't connect to server because name or password are wrong'

BUT... i didn't enter a password...?


When trying to connect with Panther
GO -> CONNECT TO SERVER -> smb://x.x.x.x/

I do get a login-window, but when i fill in name and pswd i get the same
message.

So i'v created a new account on the same Apple (running Panther)
Now i can connect using AFP, but SMB is still the same.


What's wrong here, and why cant i enter a name+pswd at my first account??

Robert

 

[Norman S. Bard]

That worked. I changed the setting on the Windows server which was set to
1, changed it to 0 and all is good.
Thanks much,
Norman