Windows 2003 Share & Macintosh G3 OS X version 10.2.8 Access

I am having problems sharing a folder (& contained files) on a Windows 2003
Standard Edition Server so that a Mac can access using the "Connect to
Server" feature. The Mac can get all the way to "seeing" the domain and
server, but cannot authenticate (failure errors are 5000 and 5023). Here is
additional info:
1. I am able to browse using the Connect to Server to "smb//192.168.3.3".
This is my Windows 2003 server.
2. When I click "Connect", I get a nice logon prompt that asks for three
items:
a. Workgroup/Domain (it is already filled in with my netBIOS
domain)
b. Username
c. Password
I have tried entering username and password in many forms, but it fails
every time with the above error codes. One of my Mac friends says that this
should work with Windows 2000 Server, but he has heard there are more issues
with Windows 2003.
My AD domain is "sonompins.corp".

Any help would be appreciated.

--
Thank you,
Mike

On 2004-10-19 17:25:08 -0400, "=?Utf-8?B?TWlrZSBMUA==?="
<(E-Mail Removed)> said:

> I am having problems sharing a folder (& contained files) on a Windows
> 2003 Standard Edition Server so that a Mac can access using the
> "Connect to Server" feature. The Mac can get all the way to "seeing"
> the domain and server, but cannot authenticate (failure errors are 5000
> and 5023). Here is additional info:
> 1. I am able to browse using the Connect to Server to
> "smb//192.168.3.3". This is my Windows 2003 server.
> 2. When I click "Connect", I get a nice logon prompt that asks for
> three items:
> a. Workgroup/Domain (it is already filled in with my netBIOS domain)
> b. Username
> c. Password
> I have tried entering username and password in many forms, but it fails
> every time with the above error codes. One of my Mac friends says that
> this should work with Windows 2000 Server, but he has heard there are
> more issues with Windows 2003.
> My AD domain is "sonompins.corp".
>
> Any help would be appreciated.

The most common issue I have seen with Mac OS X connecting to Win2K3 is
that Win2K3 has SMB signing turned on by default. Unless it is being
enforced via Group Policy, you can turn this off using the Local
Security Policy console (look for "Microsoft Network server: Digitally
sign communications (always)" under Local Settings > Security Options).

I've also found that OS X's built in firewall, ipfw, can cause problems
with SMB connections as well, even when all the appropriate ports (137,
138, 139, and 445) have been opened.

HTH.

--
Scott Lowe

Scott,
I'll give this a try the first chance I get. Thanks for responding. I put
this out on the General newsgroup a few days ago and thought there was no one
out there.
Mike

"Scott Lowe" wrote:

> On 2004-10-19 17:25:08 -0400, "=?Utf-8?B?TWlrZSBMUA==?="
> <(E-Mail Removed)> said:
>
> > I am having problems sharing a folder (& contained files) on a Windows
> > 2003 Standard Edition Server so that a Mac can access using the
> > "Connect to Server" feature. The Mac can get all the way to "seeing"
> > the domain and server, but cannot authenticate (failure errors are 5000
> > and 5023). Here is additional info:
> > 1. I am able to browse using the Connect to Server to
> > "smb//192.168.3.3". This is my Windows 2003 server.
> > 2. When I click "Connect", I get a nice logon prompt that asks for
> > three items:
> > a. Workgroup/Domain (it is already filled in with my netBIOS domain)
> > b. Username
> > c. Password
> > I have tried entering username and password in many forms, but it fails
> > every time with the above error codes. One of my Mac friends says that
> > this should work with Windows 2000 Server, but he has heard there are
> > more issues with Windows 2003.
> > My AD domain is "sonompins.corp".
> >
> > Any help would be appreciated.
>
> The most common issue I have seen with Mac OS X connecting to Win2K3 is
> that Win2K3 has SMB signing turned on by default. Unless it is being
> enforced via Group Policy, you can turn this off using the Local
> Security Policy console (look for "Microsoft Network server: Digitally
> sign communications (always)" under Local Settings > Security Options).
>
> I've also found that OS X's built in firewall, ipfw, can cause problems
> with SMB connections as well, even when all the appropriate ports (137,
> 138, 139, and 445) have been opened.
>
> HTH.
>
> --
> Scott Lowe
>
>