Well, I have a feeling that it's my cable...it is a crossover cable, but
it's old.  I do get a link light on both machines, and when I ping from
Linux box, the actvitiy light blinks, but when pinging from the windows box,
the activity light doesn't blink.

Both machines can ping their own IP addresses, but running arp -a on the
Linux box only shows eth0, not eth1.  A ping from the Linux box to the
Winbox results in Destination host unreachable, ping from Winbox to Linux
box results in request timed out (and again, no activity).

Everything else looks good.

-Lucas

> Assuming that "eth1" is your inside interface, and "eth0" is your outside
> interface, the routing table looks good.  To troubleshoot this, I'd do
> the following:
>
>   - Check your cabling.  If you're using a direct connection, make sure
>     you're using a crossover cable.  If you're on a hub, make sure you're
>     using straight-through cables, and that you're not using the hub's
>     "uplink" port.  Either way make sure you have link lights on each
>     port in the path.
>
>   - Run "ifconfig -a" on the Linux box.  Check to make sure eth0 is in an
>     "UP" state, and that your netmask and broadcast address look good.
>
>   - On the Windows box run "ipconfig/all" and do the same.
>
>   - On the linux box scan the output of "dmesg" to make sure the
>     interfaces came up correctly.
>
>   - On each box run "arp -a".  If the other side doesn't show up in the
>     arp table, you most likely have a connectivity problem.
>
>   - Check the routing table on the Windows box.  Either "route print"
>     or "netstat -nr" should work.
>
> >
> >
> > Any ideas?
> >
> > -Lucas
> >
> >
> >
>
>
>
>