Sygate blocking pings and need registry tweak for nag (win98)

[denodave]

The thing is I am setting up a couple of cisco routers in a lab network, and as I have been checking connectivity I have discovered that Sygate is mostly blocking (sometimes not) the pings even though this is an internal network. My addressing scheme is experimental and not set up on private IP, could that have something to do with it? The routers are 1602R's 56k serial back-to-back, ethernet ports running to hubs which connect to pc's.

Also, I am running Sygate's personal firewall ver.5(excellent product) and I want to turn off the nag screen for updating to a newer version. The newer version is a 30-day trial which I of course don't want. Why would I "upgrade" to a trial version when this version works perfectly?

Anyone with sygate tweaking experience out there?

p.s. this string may be on other forums!! Email me! denodave@yahoo.com
Real men pray...especially techies!

 

[jgercken]

Why are you running a firewall on an internal, lab network? This forum is for questions on Cisco Routers. You may have better luck finding someone with Sygate's personal firewall ver.5 experience elsewhere.
-Jeff ----------------------------------------
Wasabi Pop Tarts! Write Kellogs today!

 

[denodave]

As i said i am trying to setup a lab network USING Cisco routers. The machines on the network are still used for outside access, thus the firewall. Besides, this is exactly the kind of problem a pre-CCNA like me needs to learn to solve (you know, real world junk). That's why the question is here!

While I am back on the subject, let me mention that pinging problems did not happen on one out of four workstations running the firewall. All were fine once I shut down the wall, but why would one machine respond to the pings and not the others? Connectivity between routers is 100%.

Any ideas, jgercken, on WHERE I will find help with Sygate? Email me! denodave@yahoo.com
Real men pray...especially techies!