Migrated to New Exchange server - now MAC's cant access

[SaleenWRX]

Hello All
First let me say this forum has been a great source of info for me in migrating my Exchange server. Thank you so much!!

Ok now I have migrated my Exchange 5.5 from a Windows NT box to a Windows 2000 Pro

All my 2000/Nt users and Web access users are perfect

But my 3 Mac users can no longer access their mail.

The Macs are running Outlook for Mac.
I have configured them to use TCPIP with the address of the exchange server - I check the name via the check name button and it Prompts for user name/password/Domain - once this is supplied the name is resolved.
But if you try and open outlook it states that the Exchange server is unavailable.

I tried everything I could think of to get this to work and havent been able to

So as a work around I installed AppleTalk protocol and File services for Mac on the exchange server.

Problem is that when I go to choose what ZONE under the protocol after checking the box for allow incoming on this adapter there are NO ZONES listed. And when I try and set up the MACs to use APPLETALK no Zones are listed.

The old NT exchange server was always listed in ZONE as *


ANy help??????????????

 

[SaleenWRX]

I found the solution -

I hope this will help someone else in the future

TIP: Getting the Macintosh Outlook (or Exchange) client to work. (Resolving the server IP address.)
fixing a problem that prevents Outlook for Mac from working:

The client requires that the Mac be able to resolve the IP address of the Exchange server, by using the host name of the Exchange server.
A very common problem occurs when there is not a proper entry for the Exchange server in the company DNS server (or perhaps there is no DNS server at all).

The solution is to create a Hosts file on the Macintosh client computer.

You need to know the "IP address" of the Exchange server. If you do not know this, try running the PING command from a DOS window in Windows:

You should get a response like so (using my server, "mail02", as an example; substitute your server name):

----------------------------------------------------------------------

C:\WINDOWS>ping mail02

Pinging mail02.company.com [123.456.789.123] with 32 bytes of data:

Reply from 123.456.789.123: bytes=32 time=2ms TTL=128
Reply from 123.456.789.123: bytes=32 time=2ms TTL=128
Reply from 123.456.789.123: bytes=32 time=1ms TTL=128
Reply from 123.456.789.123: bytes=32 time=2ms TTL=128
----------------------------------------------------------------------

Make sure you have set up the "search domain" of your company, in the Macintosh TCP/IP control panel.

In my case, this is "company.com". Then when I use "mail02" in the Hosts file, the computer knows to put it together like so: "mail02.company.com"

(That is called a FQDN, Fully Qualified Domain Name)

Also, keep everything in lowercase.

----------------------------------------------------------------------

Directions to make Hosts file on your Mac:

Make a Hosts file using SimpleText and save as "Hosts" into the System folder.
Then go to TCP/IP Control Panel and select the file via the "Select Hosts File" button (may have to change the user level).
The Hosts file is set up like this (one line):

mail02 A 123.456.789.123

This will resolve the name "mail02" to IP address 123.456.789.123

new details on configuring the Mac TCP/IP hosts file:

If you attempt to use the instructions given in the tip: TIP: Getting the Macintosh Outlook (or Exchange) client to work. (Resolving the server IP address.), and are getting an error message when the host file you created is selected. "Are you sure you want to use the host file? Line 1 has a bad domain name."
We discovered with TCP/IP version 2.0.1 the host name had to have a suffix ".com" or the domain name would not be valid. To work around this a conical name or alias is needed. Then point the alias to the IP address of the Exchange server.

The following lines were added to the host file:

Exchange CNAME bogusdomain.com
bogusdomain.com A "Exchange IP address"