Cant ping

[ngrayson]

GUys,

I had an issue ages ago which never got resolved and which I just let go as it did not bother me.

Running 6.0.3, 3-4 clients, DHCP by Mac Address, assummed user by IP. All outbound ports Lan-Internet set to allow. Extended networking set to block ping from internet but allow workstations to Ping Wingate server.

None of the clients can ping any thing on the internet. Prior to 6.0.3, and even some of the rev 6 Beta's allowed this and I have not changed the config.

It did not really bother me but the company now has us use Check Point Secure Client VPN software and this works but seems to time out. I put Ethereal on my laptop the other day and in monitoring the virtual adapter created by Secure client and it uses Pings as stay alives so now its important.

Any known issues regarding Pings??

Secondly, the proxy does not seem to see this as the connection times out and drops so its not seening traffic even when I'm using the session continiously, any comment?

Cheers,
Neil

[Pascal]

I don't see any problems from this side, pinging through a 6.0.4 gateway. I assume your workstations are going out using NAT?

Do you see anything in the firewall when you are attempting a ping?

[ngrayson]

Sorry for the delay, work got a bit hectic.

This is not as simple as I though as some can and some cant.

Dont yet fully understand it but will investigate further.

regards
Neil

[jamesc]

sorry for the silly question... but you have said some can and some cant and have also mentioed proxies..

if the people who cant, are unable to ping www.google.com

Can they ping 66.102.7.147 ?? (googles ip address)

Maybe some clients do not have DNS or Gateway set correctly?

[ngrayson]

James,

Manny thanks for the suggestion but in all cases DNS resolution is not an issue. Besides, I'm God of the network and set the machines up.

I'm suspicious of something else at the moment. I actually use two ISP's (for cost reasons) one during the day and another for evenings and weekends. Its the daytime one which seems to fail.

What I can do (and did yesterday) is dial into the ISP which I use evenings and weekends, during the day, I can do that, I just pay more, hence the normal use of a daytime one. Strangely, I could ping through this ISP to any of the sites I could not previously get to.

The daytime ISP fails every time but more importantly, the "network not reachable" message comes not from any local address, nor the destination address so I'm wondering if the daytime ISP (who I ping) has a lobby router and the failure is because its used an ICMP redirect to this router.

Its also significant that the SMTP server I use is not contactable during the day.

So, I put it down to one of two things, the first is the daytime ISP or the second is wingate cannot play nicely with the two ISP's although it did used to work fine even with some of the rev 6 Beta's.

Normal proxied web access works fine through either.

I've written to the ISP to try to eliminate them from the equation. If they answer in the negative I'll pen (? should that be finger) another response here.

regards
Neil