Damn ping

[ngrayson]

Guys,

Most of the problems I was experiencing have gone with the final release of 6.0 with the exception of not being able to ping the internet.

I have some screen shots of various things which I could send but here is a summary.

If I try to ping www.demon.net, the following happens.

We dial out correctly and the DNS lookup is sucessfull and returns the IP address but I get failures.

3 similtanious time stamped events occur in wingate.

The history windows shows a nat translation to/from that IP address.
The sytem window shows an authentication failure on that NAT for that user.
The firewall log shows a rejection with a source address of the demon webs site and a destination address of my ISP account (i.e. not the end computer but the shared IP address).

My take on this is that its blocking the imbound response.

My port restrictions are internet to wingate PC 1-65535 deny for UDP and TCP.

None of the config has changed so why has it suddenly stopped working. It did work OK in RC1.

Regards
Neil

Whats going on chaps ??

[Pascal]

My take on this is that its blocking the imbound response.

That sounds like the problem. There has been some changes in the port security actions, etc. Can you verify that your adapters are set correctly (Internal vs External), make sure that all the related config is allright. Also double check that the pings are allowed on the firewall section of the ENS Configuration.

[ngrayson]

Hi Pascal,

Thanks for the quick response, I was not expecing one until Monday.

Etherent adapter is set as internal trusted and the ISDN is set as external untrusted.

The firewall is set up to allow local pings but reject internet pings. I dont see that as the problem though as this is a ping response and not a request and its always been this way. Clearly, the outbound echo request has been sent because the inbound packet is triggering the firewall event.

Other configs look OK, DMZ firewall stuff has no entries as I dont use it.

Gut feel tells me that in one of the new features you have a new and uninitialised variable or key which is the problem.

I dont know where to go from because to me it all looks OK. The frustrating part is that I know that if I go back to 5.2.3 or 6.0 RC1 it will work without chnageing anything.

I'm prepared to send you the full config, registry the lot if it helps but will only do that direct and not from the forum.