Ahhh!
Thank you for your responses everyone.
Since I have been milling over this problem and pestering all of you with
it I thought I'd let you all know that I found the problem and sort of
corrected it.
By paying close attention to my ROUTE and ARP tables I was able to find
that on the Win95 client the IP address of the linux server was bound to
an incorrect hardware net address in it's ARP table. I believe the DHCP
server or one of our other server type machines was broadcasting that the
IP of the linux box was associated to someo ther card. I believe this is
because normally our network uses DHCP and dynamically assignes IPs,
except the linux box is on a static ip, problem is, the DHCP doesn't know
about it... so it's getting confused. Ultimately I believe I need to
change something on the DHCP server to make it clear that the linxu box
is in fact the specific IP that it is. As of now I havn't done that but
have more or less fixed things by just having the Win95 client by
dynamically assigned it's IP, and then by running a short script,
manually definin gth default route to the linx box, and statically
assigning the entry in the arp table.
Thanks for your help.
If there's anything Iv'e described that just doens't make sense, or is a
silly way to do things, please mention it. :) Thanks again.
-Josh
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
