Home Forums OS X Server and Client Discussion Active Directory Panther trying to connect to Win2003 server file share

  • This topic has 3 replies, 2 voices, and was last updated 20 years ago by Anonymous.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #359449
    RogueWinAdmin
    Participant

    Hello All,

    I’m trying to connect to a shared file on one of our Win2003 Server but get different errors depending on how I attempt to connect.
    When I go to:
    GO – Connect to server – Browse – select the server name click on connect, I get prompted for name and password (I used the AD admin credentials here) click “ok”
    I get this error
    ” The alias “servername” could not be opened because the original item cannot be found”

    When I go to:
    GO – Connect to server – and enter the smb/cifs path I get promted for authentication credentials again, I click “ok”
    and I get the following error:
    “Could not connect to the server because the name or password is not correct”

    I kinda confused by the different error msgs

    I don’t think this is a DNS issue b/c I can ping the server from the mac terminal and it sees the server with the IP address AND the AD fully qualified Domain Name.

    On another note this same Mac terminal CAN connect to other windows shares on a Win2000 Server and other Macs can connect to this Win2003 server share.
    Just to clarify here. the MAc that canNOT connect is running 10.3.5 and the Macs that CAN connect are running 10.2.8

    any / all help is appreciated…

    Thanks
    Brian

    #359461
    RogueWinAdmin
    Participant

    Thanks for the reply, I already disabled that on the Win server and it didn’t fix the issue. That seems like it would be a consistent issue regardless of what mac os version though. What is different between 10.2.8 and 10.3.5 that would cause this issue?

    #361225
    Anonymous
    Guest

    You need to turn off SMB signing on your win2k3 server. This can be found in either the local policy or GPO.

    This is in the Windows Settings/Security Settings/Local Policies/Security Options:
    Domain member: Digitally encrypt or sign secure channel data (always) = NO
    Microsoft network client: Digitally sign communications (always) = NO

    This should fix your problem

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Comments are closed