Scott Benoot wrote:
>
> I have two Mac clients with OS 8.0 that are unable to log in to Exchange
> Server 5.0 SP1 running on NT SP3. They could log in fine when the server
> was on the same network as the Macs, but we have had to move the server to
> another network. The Macs now have to go through a router. The Macs can
> resolve the name of the server just fine when setting up the profile, but
> will not log in. I am using TCP/IP to connect to the server. Can anybody
> help?
>
> Thanks,
>
> Scott
Thanks
Scott
Greg Askew <gr...@NoSpam-bitusa.com> wrote in article
<34353DBA...@NoSpam-bitusa.com>...
"Local Hosts file support
------------------------
Open Transport TCP/IP supports a Hosts file that may be used to
supplement and/or customize the Domain Name Resolver's initial cache
of information. The Hosts file is normally stored in the Preferences
folder in the active System Folder. When Open Transport TCP/IP is
initialized, it reads the Hosts file (if any). As in MacTCP, the
supported Hosts file features follow a subset of the Domain Name
System Master File Format (RFC 1035).
Open Transport TCP/IP is more stringent regarding the content and
format of the Hosts file than was MacTCP, which permitted violation
of the FQDN requirement for <domain-name>. For instance, the format:
charlie A 128.1.1.1
which was acceptable to the MacTCP DNR, is no longer permitted because
of the use of domain search lists in Open Transport/TCP ("charlie"
could potentially exist in any or all of the configured domains). To
accomplish the same effect, use this format instead:
charlie CNAME myhost.mydomain.edu
myhost.mydomain.edu A 128.1.1.1
This associates the local alias charlie with the fully qualified
domain name myhost.mydomain.edu, and resolves it to the address
128.1.1.1. Use of local aliases is limited to CNAME entries; NS
and A entries must use fully qualified domain names.
You can create a Hosts file with any text editor or word processor
(the Hosts file must be stored in text format). If you use a Hosts
file, keep it as short as possible, and include only entries that will
be accessed frequently. This reduces the memory required to cache
the DNS information and minimizes the need to maintain and update
Hosts files as system information changes.
Open Transport TCP/IP automatically uses a Hosts file stored the
Preferences folder of the active System Folder. If no Hosts file is
found in the Preferences folder, Open Transport TCP/IP searches the
active System Folder for a Hosts file. You can specify a particular
Hosts file to use with a specific configuration. For example, one
Hosts file might be set up for a user connecting via Ethernet, and
another set up for when that user connects via modem."
Also, make sure your Mac has TCPIP active at all times, not just
when needed.
--
Greg Askew
Business Information Technologies, Inc.
Scott Benoot wrote:
>
> Yes, I have put the 2 Macs in a HOSTS file, and the server can ping each of
> them by IP address and by name. Exchange goes so far as to even ask for
> the NT login, but will not login after the correct password is given. It
> just says that the server is unavailable, but my 20 WIN 95 clients have no
> problems.
>
> Thanks
>
> Scott
>
> Greg Askew <gr...@NoSpam-bitusa.com> wrote in article
> <34353DBA...@NoSpam-bitusa.com>...
> > Are you using a HOSTS file?
> > --
> > Greg Askew
> > Business Information Technologies, Inc.
> >
> >
> > Scott Benoot wrote:
> > >