RE: Remote Connections
Posted in 1999
Topics: Server Administration, Networking & sqlhosts Configuration
The hosts file at both sites are in lower case.
Questions:
Server1 is connecting to Server2 using "dbaccess db1@server2".
1) When the connection is made, was the IP of server1 sent, or the hostname
that is listed in the sqlhosts file on Server1.
2) When server1 is connecting to server2, does the hosts file on server2
get read first to resolve who is connecting? And is the sqlhosts file at
server2 ever read?
On server2, I have server1 listed in the hosts file in lowercase. DNS has
been turned off on server2. When server1 connects, I receive an error that
it is not trusted (user@SERVER1), where server1 is all caps. Again in both
hosts file (server1 and server2), all hosts are in lowercase.
:-%
-----Original Message-----
From: Robert Griffin [mailto:rgriffin@farmerstel.com]
Sent: Wednesday, March 17, 1999 7:48 PM
To: Lori.Cardwell@CEN.AMEDD.ARMY.MIL
Subject: Re: Remote Connections
Take a look at the hosts file on the computer trying to make the connection
--
Robert
> For some reason, when I connect the hostname is in all caps, and
therefore
> does not get resolved because they are listed in the rhost files as lower
> case.
Where is it getting the upper case from? I am not using
> DNS.
>
>
>
Cardwell Lori B wrote:
>
> The hosts file at both sites are in lower case.
>
> Questions:
>
> Server1 is connecting to Server2 using "dbaccess db1@server2".
>
> 1) When the connection is made, was the IP of server1 sent, or the hostname
> that is listed in the sqlhosts file on Server1.
>
> 2) When server1 is connecting to server2, does the hosts file on server2
> get read first to resolve who is connecting? And is the sqlhosts file at
> server2 ever read?
>
> On server2, I have server1 listed in the hosts file in lowercase. DNS has
> been turned off on server2. When server1 connects, I receive an error that
> it is not trusted (user@SERVER1), where server1 is all caps. Again in both
> hosts file (server1 and server2), all hosts are in lowercase.
Perhaps the hostname is being upshifted by the shell on server1, is it
a WinNT/Win95 host? If UNIX try connecting directly to the remote
server (using database@server notation on the commandline will make
the connection by connecting to the local server and asking it to make
the connection to the remote) by setting the INFORMIXSERVER environment
variable to "server2" then dbaccess will bypass the local engine and
connect directly to the remote server. On UNIX in ksh or bash you can
do this on the commandline:
INFORMIXSERVER=server2 dbaccess db1
The dbaccess status line WILL show "db1@server2" when it starts up so
you can verify from which server the database is connected.
Art S. Kagel