Neil:

You were right. It was a faulty, $3,000, switch!!!! grrrrrrrr

Thanks for all your help.

Mal

>Hi,
>No having the DNS/DHCP on the server is the best. I was referring to having the DNS/DHCP in an ADSL gateway router.
>We can cross that one off the list.
>
>Next things to check, is the server NIC faulty, is the switch faulty, try plugging the server fly lead into another switch port, the port may be faulty.
>
>>Neil:
>>
>>Hmmmm ... DNS requests ... wouldn't have even gone there.
>>My DNS sevre is also my DOMAIN/FILE/ACTIVE DIRECTORY server ... all in one high powered machine. Bad? Could this becausing the timed shut down?
>>
>>Mal
>>
>>>Hi,
>>>Also check the CMOS in the machines for any power related settings.
>>>Also I am assuming that you have power filtering on all machines and the switch, and there is no electrically induced injection into the LAN cabling or faulty cabling.
>>>Could the switch be experiencing a load related buffer overflow, swap it out and see what happens.
>>>
>>>IMPORTANT:-What device is servicing the DNS & DHCP requests. If it is the gateway router, it is the easiest way of shooting yourself in the foot. i.e. gives very erratic behaviour.
>>>
>>>>Neil:
>>>>
>>>>Yes, I had already tried hibernating and the power settings. I turned everything off.
>>>>Now, WOL, that's something I didn't know about and sounds very much like what's happening.
>>>>I'll look into it and let you know what of the result.
>>>>
>>>>Mal
>>>>
>>>>>Hi,
>>>>>Some things to check on the workstations and server.
>>>>>1. Check the power settings in screen properties, may be hibernating.
>>>>>2. Some NIC's have power saving functions, check the properties in Control panel/Networking and check the adaptor settings.
>>>>>3. Also check WOL settings (Wake on LAN), may be going to sleep.
>>>>>
>>>>>>Neil:
>>>>>>
>>>>>>Thanks for not giving up.
>>>>>>
>>>>>>No, no COM or KeepAlive.
>>>>>>
>>>>>>I did check the server event log and found the following:
>>>>>>
>>>>>>o WinHTTP Web Proxy Auto-Discovery Service has been idle for 15 minutes, it will shut down.
>>>>>>o WinHTTP Web Proxy Auto-Discovery Service suspended operation.
>>>>>>o WinHTTP Web Proxy Auto-Discovery Service enter the stop state.
>>>>>>
>>>>>>These entries are about the time the workstations went down.
>>>>>>
>>>>>>Not sure what WinHTTP Web Proxy Auto-Discovery Service is but will look it up.
>>>>>>In the mean time, do you have any ideas on this?
>>>>>>
>>>>>>TIA
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Hi,
>>>>>>>Are you using COM ? KeepAlive ?
>>>>>>>
>>>>>>>Are there any entries in the Event logs of the Server or Workstations.
>>>>>>>
>>>>>>>>Hi Neil:
>>>>>>>>
>>>>>>>>Thanks for you reply.
>>>>>>>>I tried diabling autodisconnect (ran the command and it said "done").
>>>>>>>>
>>>>>>>>It still happened all the workstations, except 5, got disconnected from the network at once.
>>>>>>>>5 stayed connected. Strange ...?
>>>>>>>>
>>>>>>>>Thanks for your time though :o)
>>>>>>>>
>>>>>>>>Mal
>>>>>>>>
>>>>>>>>>Hi,
>>>>>>>>>Disable autodisconnect http://support.microsoft.com/default.aspx?scid=kb;en-us;297684&Product=win2000
>>>>>>>>>
>>>>>>>>>>HI:
>>>>>>>>>>
>>>>>>>>>>I have 20 workstations connected to my Windows Server 2003 server.
>>>>>>>>>>
>>>>>>>>>>If I leave a workstation connected buy idle for ... 1 hour, the workstation geta disconnected from the network. I would have to reboot the workstation in order to use the workstation on the LAN.
>>>>>>>>>>
>>>>>>>>>>The other problem I'm having is: At about 11:00 PM every night, all of the workstations gets cut off from the network. Again, I'd have to reboot all of the workstations to connect into the LAN.
>>>>>>>>>>
>>>>>>>>>>I do not have any restrcitions as "hours of use" on any of the workstations.
>>>>>>>>>>
>>>>>>>>>>I there some where in Server 2003 that I can check to see if the server is logging any of the workstations off?
>>>>>>>>>>
>>>>>>>>>>TIA
>>>>>>>>>>
>>>>>>>>>>Mal