How do i get my ISA to booth/ looging in faster

Hello Guys
I have a Box A(ISA SERVER 2006) The issue with this Box is that it takes a whole while to complete boothing.It also take much longer to authenticate a user  that is logging into the server.

It can take between 5-10 minutes in case of logging in

Please can i get a possible cause and solution to this challenges
Thanks and hope to hear from you guys soon

Hi,

Well, Check ISA event log and also Windows event log and let us know what do you fine there?

Also, make sure that your clients and ISA server DNS setting is fine! ISA server internal NIC should be pointing to your local DNS which is hodling your DC records, because authentication comes from there!.

It would be better if you post ipconfig /all results at ISA machine.

Regards,
Faraz H. Khan

You could use a solid-state-disk as harddisk:

http://en.wikipedia.org/wiki/Solid-state_drive

- Faster start-up because no spin-up is required.
- Fast random access because there is no read/write head[13] Low read latency times for RAM drives.[14] In applications where hard -disk seeks are the limiting factor, this results in faster boot and application launch times (see Amdahl's law).[15]
- Consistent read performance because physical location of data is irrelevant for SSDs.[16]
- File fragmentation has negligible effect.

See this comparison:
http://www.notebookreview.com/default.asp?newsID=4258

Hi, Farazhkhan.
Here are some of the findings from the events log;

Warning: (21138) The connectivity verifier "Internet verifier 1" reported a slow connectivity response threshold was 5000 msec and the monitor response time was 6454msec.

Warning: (15105) ISA Server detected an all port scan attack from internet protocol (IP) address 192168.0.99

Error: (14065) One or more of the actions associated with alart No connectivity has failed, due to configuration settings. The mail server may be down, or the specified command may not exist. Check for related errors and fix them accordingly.

Error: (21137) The connectivity verifier "internet Verifier 2" reported an error when trying to connect to http://enlconsortium.com.
Reason: The request has timed out.

Error: (21138) The connectivity verifier "internet Verifier 1" reported an error when trying to connect to http://cnn.com 
Reason: The request has timed out.