[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Anyway, what I'm asking now, is does anyone know any way that I could
> isolate this problem and see if it is server or client side?
Your problem is one of route tables or arp tables, I bet.
When your Windows client is having its problem, try the "route print"
command, as well as the "arp -a" command. You might want to run
"route -n" and "arp -an" on the masq box, too. Then do your pings that
fix things, and run the same four commands again, to see what changed in
the tables.
Take good notes. :)
--
[EMAIL PROTECTED] (Fuzzy Fox) || "Nothing takes the taste out of peanut
sometimes known as David DeSimone || butter quite like unrequited love."
http://www.dallas.net/~fox/ || -- Charlie Brown
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
