The most logical explanation I can think of is that the subnet mask on your
linux box is wrong - either that or the routing table. But that really
doesn't explain the DNS traffic passing.. but I would definately check it out.
Are you using the same IP address in both Windows and Linux? I'm just
wondering if your doing packet filtering on one of the routers which is
filtering traffic from the linux box?
This probably doesn't apply, but the masquerading router isn't an MS Proxy is
it? And the windows client isn't using Proxy Client? Just a thought from past
experience.
The only other thing I can think of, is that FTP and Telnet aren't working at
all on the linux box....
Best guess is still subnet mask or routing table..
Rob
On Fri, 30 Apr 1999, Claudiu Balciza wrote:
> I have a network (I really do).
>
> +----------+ +--------+ +------------+
> |a workstn.|<->|internal|<->|masquerading|<->Internet
> | | |router | |router |
> +----------+ +--------+ +------------+
>
> The workstation has the default gateway to the internal router.
> The internal router has the default gateway to the masquerading router.
> The masquerading router has the default gateway to the Internet.
> If the workstation runs windoze it is able to ping and ftp.
> If it runs linux, it cannot (DNS works in both cases).
> no error for ping, it just waits.
> ncftp cannot open the command channel.
>
> what am I missing ?
>
> Claudiu
