Unable to PING Default Gateway 2

[DotNetNewbie]

Hi,

I'm reviewing the current setup of a network that I now have to manage and i've come across a strange anomoly.

Every server has the Default Gateway set to an IP address that it cannot PING. On inspection the IP address is of the Checkpoint Server.

Does anyone know if this is right or wrong?

I'm concerned that if the servers cannot ping the default gateway this may in part be the reason they are having nextwork issues.

Thanks in advance

D.

 

[porkchopexpress]

Have a good weekend.

 

[DotNetNewbie]

And you, many thanks for your assistance so far.

D.

 

[Seaspray0]

Wow! * to porkchop for persistence! lol. BTW, 2k will set up fine without .net patches as I've set up a 2k domain prior to 2k sp1 (original and before .net).


Start, Help. You'll be surprised what's there. A+/MCP/MCSE/MCDBA

 

[porkchopexpress]

I hate giving up on a problem

 

[DotNetNewbie]

Hello,

This problem seems to have resolved itself over the weekend. The only thing I changed was to increase was:

Admin Tools -> Domain Security Policy -> Security Settings -> Account Policies-> Kerberos Policies ->Maximum Tolerance

Since doing that the problem has disappeared.

Many thanks for everyone advice, time and help, very much appreciated.

 

[porkchopexpress]

Was it set to the default 5 minutes before?

 

[porkchopexpress]

Longer times allow for the Net Logon service to perform authentication over slow networks, but can leave your network open to replay attacks.

 

[DotNetNewbie]

Hello again,

Yes it was set to 5 mins. I increased it to 60 initially and left it over the weekend. Yesterday I reduced this to 30 mins and today ive reduced it to 15 mins. So far so good. I plan to continue to reduce the time until a) it works normally or b) the time is as low as possible.

It maybe part of an issue with have with the ajoined NT4 domain, which is being phased out. Perhaps once this has gone then the issue will resolve itself.

Again, thanks for your advice.

D.

 

[porkchopexpress]

See how it goes i don't think it will be anything to do with the NT4 domain though, i've never known it on any AD/NT4 trust domains i've worked on.

Good luck.