RE: Mac OS/9.2.2 connection problem to a Windows 2000 SBC Server

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Mike (Mike_at_discussions.microsoft.com)
Date: 06/24/04

  • Next message: MSEXCHANGENOVICE: "can't connect to Windows 2000 Server shares using OS 9. ONLY ON 10"
    Date: Wed, 23 Jun 2004 20:13:01 -0700
    
    

    Chris,

    Did you resolve this yet?

    I have the same exact issue,

    Any help would be appreciated

    Thanks
    Mike

    "Chris Cline" wrote:

    > I appolagize if this turns out to be a double post.
    >
    > I have a 2 windows 2000 servers.
    > A is a Windows 2000 SBC Server and the PDCand it has Exchange running.
    > B is a Windows 2000 Member Server.
    >
    > Both servers have all the latest software updates I could download.
    > Both have SFM running and I have checked that the service is running
    > on both. Both have AppleTalk up and running. Both computers showup in
    > my Macs OS 9 Chooser when I click on the AppleShare icon.
    >
    > My Mac computer is a Mac G3 running a fresh new install of OS 9.1 and
    > has been updated to 9.2.2.
    >
    > Here is the problem with the order of events
    > 1. On the mac I click on the chooser, appleshare, then server a. I
    > then click the Ok button. I am prompted with the default clear
    > password logon dialog asking me to enter the username/password or to
    > use guest. Guest is enabled.
    >
    > 2. I select the option to logon as guest and click "connect"
    >
    > 3. the Mac sits there for about 10mins with the hour glass until I get
    > the following message: The connection to this server has been
    > unexpectedly broken.
    >
    > 4. I have tried to use a valid windows domain user account and still
    > get the same behaviour as above. I have even tried to include the
    > domain along with the user name.
    >
    > Now, the funny thing is if I perform the same steps above but select
    > server "b" from the chooser, I get connected to the server and I am
    > promted to select what MS UAM volume I want to mount.
    >
    > I just dont understand why I can get connected to server B but not A
    > nor do I know what is causeing the error with server A.
    >
    > Any ideas?
    >


  • Next message: MSEXCHANGENOVICE: "can't connect to Windows 2000 Server shares using OS 9. ONLY ON 10"
  • Quantcast