View previous topic :: View next topic |
Author |
Message |
BHarvey
Joined: 27 Oct 2002 Posts: 33
|
Posted: Fri Mar 14, 2003 3:56 pm Post subject: |
|
|
Installed on XP Pro, SP1, as a service. On boot, it appears to block connectivity to the network (ping from command prompt fails) for about 2 minutes. It has nothing to do with the "wait X minutes before starting", and is directly related to running as a service at boot. If I set the service to manual and reboot, ping works immediately. If I start the service, ping works immediately; it is only when rebooting that the system cannot connect to the network for the ~ 2 minutes.
Thanks,
Brad |
|
Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002 Posts: 12806 Location: USA
|
Posted: Fri Mar 14, 2003 4:10 pm Post subject: |
|
|
Probably you have many tests those use TCP protocol. ICMP (ping) packets has lower priority and when network traffic is high system/routers can drop ping packets. May be Windows or/and other services send some TCP packets at startup and increase traffic...
Anyway if you start service when system loaded and everything works fine, use "wait X minutes before starting" and HostMonitor will not perform any operations until system will be ready
Regards
Alex |
|
Back to top |
|
|
Marcus
Joined: 18 Nov 2002 Posts: 367
|
Posted: Sat Mar 15, 2003 5:02 am Post subject: |
|
|
>it is only when rebooting that the system cannot connect to the network for the ~ 2 minutes
I think you use DHCP for your ip configuration. If so, use a fixed IP (or just don't reboot ) |
|
Back to top |
|
|
BHarvey
Joined: 27 Oct 2002 Posts: 33
|
Posted: Tue Mar 18, 2003 4:05 pm Post subject: |
|
|
I already use a fixed IP. Found out finally (after a system rebuild) that there is an apparent conflict between the NetScreen Remote VPN client and the HM service.
Thanks again.
|
|
Back to top |
|
|
|