With "any" Win95 and WinNT system I have connected to it, I get the following:
When I do a traceroute to 203.24.16.1 I get:
Tracing route to esimene.cynet.net.au [203.24.16.1]
over a maximum of 30 hops:
1 * * * Request timed out.
2 143 ms 141 ms 140 ms esimene.cynet.net.au [203.24.16.1]
Trace complete.
Now, hop one should respond with 203.24.16.5, but it just gives an asterix.
I have a PM2E30 and a PM2ER30 and both behave like this.
The wierd bit? Both respond fine when a unix or OS/2 box traceroute's past
them.
I don't think the client machines are configured wrong as I have tried every
combination I can think of. Is this a Windows bug or a portmaster bug?
Does anyone else get this problem?