At 03:06 PM 11/07/2005 -0700, you wrote:

>Tried your suggestion....
>Replacing the "Database" name "C:/Program
>Files/AT60Test/CONSTITUENT.FDB" (which did work locally) in the MS ODBC
>manager with "DevBox_1:AT6Test" causes the MS ODBC manager to report the
>error:
>"Unable to complete network request to host "DevBox_1". Failed to
>locate host machine. The specified name was not found in the hosts file
>or Domain Name Services."

There's your answer. Your assumption that IP addresses are getting
assigned dynamically is wrong. The fact that you can't ping or Telnet the
server from the client machine reinforces this.

Back to the drawing board on configuring tcp/ip. Either get DHCP working,
or configure the server statically in the Hosts file on server and
clients. Either way, if it's configured properly, the client must be able
to Telnet or ping the host machine by either hostname or IP address.

Static configuration seems to be your best bet, given that DHCP isn't
behaving as you think it is. A static address will be bypassed by DHCP,
ensuring that it is always available and valid. Pick an address in the LAN
range and configure the host's NIC to this address. Make entries in the
server's and clients' hosts files to associate the hostname with that IP
address. Make sure that the host's and clients' NICs are configured with
the correct subnet mask (255.255.255.0). If you are relying on DHCP to
assign the clients' IP addresses then also make sure that it is using the
correct subnet mask.

Please trim your postings.

./heLen