You could try installing tmdns (It's a lightweight dns for tiny LANs.)and
point your windows dns to 127.0.0.1. The question is what point dns on a
192.168 lan?
Most of the windows network configs I've seen are a jumble of netbios,
netbeui, QoS, netware and every other service and protocol ppl throw at the
system. Just use TCP/IP and nothing else. Windows is stupid enough as it is
without complicating it with bolt-ons that confound it ad infinitum.
Bernard wrote:
> Hi all
>
> How can I systematically analyse what is wrong with my LAN between Red
> Hat 9 Linux 2.4.20-8 and Win98?
>
> I am getting 50kb/s over a direct LAN cable with proftpd-1.2.9-1.9 on
> xinetd.
>
> My Linux networking knowledge is limited, and I have probably made a
> mistake in the setup.
>
> Many thanks!
>
> Bernard
>
>
>
> In my proftpd.conf I have added:
>
> UseReverseDNS off
> IdentLookups off
>
> but this did not improve speed.
>
> /etc/resolv/conf:
>
> search localhost
> nameserver 203.96.16.35
> nameserver 203.96.16.36
>
> These nameservers are on the internet but not accessible because
> currently the computer is not connected. If I connect via modem then
> there is no improvement.
>
>
> /etc/sysconfig/network-scripts/ifcfg-eth0:
> DEVICE=eth0
> BOOTPROTO=static
> BROADCAST=192.168.0.255
> IPADDR=192.168.0.4
> NETMASK=255.255.255.0
> NETWORK=192.168.0.0
> ONBOOT=yes
--
Regards,
Peter.
http://www.pelicom.net.nz