It's not a performance issue at all. This lag most likely results from your server trying to do a reverse lookup on the IP address (searching for your machine's hostname), since your internal server probably has no DNS handling the other hosts on the network, it keeps looking for a few seconds, fails, and then gives up and just uses the IP address.
Now on your Linux server, you must have given it a hostname and a domain, even if its not a fully qualified external domain name.
If you look for a file named 'hosts.sam' on your Win98 machine, and open it up in a text editor, you will see something like:
Code:
# Copyright (c) 1998 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP stack for Windows98
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
Just add another line to this, with your internal server's IP address and hostname. For example, if the hostname is 'myserver', and the internal IP is 10.1.1.50, then you would add
This means that to surf your local server, you can now just enter '
in the browser window.
On your Linux server, you would just do the reverse in the /etc/hosts file and add an entry for the other local machines on the network. This way, you can refer to all machines by their hostnames, without even worrying about IP addresses or a domain. Since you are just talking about a couple of machines here, this is easier than setting up an internal DNS server. Your system will now seem to respond instantaneously.
HTH