F
Fred
Hello -
Hoping for '2 for 2' here - last request answered with a
good fix!
My W2KPro server runs Wingate 'proxy' software so other
nodes on the LAN can access the Inet thru this server
(dialup connection to ISP). Works fine, lasts a long time!
I can *telnet* directly to the server from any local LAN
node, and immediately get the 'WinGate>' prompt.
(Normally don't do that other than just for diagnostics).
BUT, I cannot 'ping' or 'tracert' to this server from any
local LAN node - just get timeouts. Heck, it's usually
the other way around!
I have not (knowingly anyway) restricted ICMP traffic, and
stopping the WinGate engine makes no difference (other
than causing a few squeals in the background about 'I
can't get to the Internet!' Ah, they'll get over it).
What can I check to try to fix this? Not critical, but it
oughta work (quick diags).
Thx in advance for any ideas.
Fred
Hoping for '2 for 2' here - last request answered with a
good fix!
My W2KPro server runs Wingate 'proxy' software so other
nodes on the LAN can access the Inet thru this server
(dialup connection to ISP). Works fine, lasts a long time!
I can *telnet* directly to the server from any local LAN
node, and immediately get the 'WinGate>' prompt.
(Normally don't do that other than just for diagnostics).
BUT, I cannot 'ping' or 'tracert' to this server from any
local LAN node - just get timeouts. Heck, it's usually
the other way around!
I have not (knowingly anyway) restricted ICMP traffic, and
stopping the WinGate engine makes no difference (other
than causing a few squeals in the background about 'I
can't get to the Internet!' Ah, they'll get over it).
What can I check to try to fix this? Not critical, but it
oughta work (quick diags).
Thx in advance for any ideas.
Fred