Thanks to those who replied to this problem. The two proposed solution
were not correct, but were helpful because they provided a clue as to what
the problem really was.
The problem was that the Exchange NT server was named differently in our
Domain Name Server (DNS) and in the NT WINS. In DNS it was named MSG01 and
in WINS it was named PSUHMC_MSG01. The Exchange client on our Macintosh
could get connected to the server using the DNS name (MSG01) for the
purpose of checking the mailbox name; however, it then stores the NT WINS
Exchange server name (PSUHMC_MSG01) in the "Microsoft Exchange Server"
properties within the client. It seems to later use this WINS name (rather
than the DNS name, MSG01, that we entered into the properties initially) to
locate the Exchange server. Since the Macintosh Open Transport uses
standard DNS name resolution and not the non-standard WINS, it could not
find the Exchange server and could not open the mailbox.
The (temporary) solution was to add the following record to the DNS to
provide an alias:
PSUHMC_MSG01 CNAME MSG01.HMC.PSU.EDU
Thanks again for your replies. I always appreciate the helpfulness of
USENET and other news readers.
>We installed the Microsoft Exchange Client for Macintosh application v. 4.0 on
>a Power Macintosh running under System 7.5.5 and Open Transport 1.1.2 using
>TCP/IP protocol (not AppleTalk). However, we can't get it to read mail from
>the Exchange server (SP2) running on Windows NT 4.0.
>We can ping the server IP address OK. In the Microsoft Exchange Server
>properties, we can enter the server name and the user mailbox name and push
>"Check Name" button, and it seems to find the mailbox just fine, because it
>changes the server and mailbox names from the aliases to the full names and
>underlines them. This same user mailbox works just fine from a Windows 95
>However, when we start the client application, a dialog box error is displayed
> "Your Microsoft Exchange Server is unavailable.
> "You can retry connecting to the server using the network, or work
> offline and connect using dial-up networking.
> "Network problems are preventing connection to the Microsoft
> Exchange Server computer. Contact your system administrator if this
> condition persists."
>The client then continues and gets other dialog error messages indicating that
>the server mail folders are not accessible.
>Any ideas on what is wrong?
>Norman Turrill, Advanced Project Engineer
>snailmail: Information Technology Dept.
>Penn State Hershey Medical Center; PO Box 850; Hershey PA 17033
Norman Turrill, Advanced Project Engineer
snailmail: Information Technology Dept.
Penn State Hershey Medical Center; PO Box 850; Hershey PA 17033