When start System Over 30 Min , Server Can not access to network.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

All MY 2000 SP4 Server in My all 2000 server cannot browse Network (but can
sent & receive Ping). When MY server over 30 min. Before 30 min ,Server is no
Problem.

I try to Check Virus But Not Found virus in my system (Mcafee & Trendmicro)

Patch problem or My lisence is full or something lost ?

Thank you
 
Sounds like DNS issues but not enough info to know. From a command prompt;

ipconfig /all

before and after. Comparing the results may reveal something.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| All MY 2000 SP4 Server in My all 2000 server cannot browse Network (but
can
| sent & receive Ping). When MY server over 30 min. Before 30 min ,Server is
no
| Problem.
|
| I try to Check Virus But Not Found virus in my system (Mcafee &
Trendmicro)
|
| Patch problem or My lisence is full or something lost ?
|
| Thank you
| --
| Solutions Zone Co.,Ltd.
 
Thank you for your information.
Dns Server (Widows 2003 is OK)

I run CMD @ W2K
type Nslookup after and before IT can solve Correct IP and I can Ping With
Domain name.
In browes I can't Browse To any server (with IP and Domain name)
It show Error Box
//andromeda is not accessible. (andromeda is Other File server)
The specified server cannot perform the requested operation.

Best Regards

Watcharakorn Pattanaratcharoen
 
Watcharakorn said:
All MY 2000 SP4 Server in My all 2000 server cannot browse Network (but
can sent & receive Ping). When MY server over 30 min. Before 30 min
,Server is no Problem.

I try to Check Virus But Not Found virus in my system (Mcafee &
Trendmicro)

Patch problem or My lisence is full or something lost ?

Thank you
Click to expand...

We've had a similar issue after some updates have been applied

"As you may have noticed there were some issues with our domain controller here in xxxxxx and also in xxx (earlier as well in xxxxx). The problem occurs after a reboot - it looks like server does not have a network connection and some of the services fail to start.
This problem was fixed by rebooting the server to safe mode and modifying "Local Computer Policy" - the groups that need to be re-added are here:"





Administrators and Service should be here..
 
Steve said:
We've had a similar issue after some updates have been applied

"As you may have noticed there were some issues with our domain
controller here in xxxxxx and also in xxx (earlier as well in xxxxx). The
problem occurs after a reboot - it looks like server does not have a
network connection and some of the services fail to start.
This problem was fixed by rebooting the server to safe mode and modifying
"Local Computer Policy" - the groups that need to be re-added are here:"





Administrators and Service should be here..
Click to expand...

Open the local policy editor
navigate to
Computer Configuration
Windows Settings
Security Settings
Local Policies
User Rights Assignments
<right hand side,open >
Impersonate a client after authentication

ensure
Administrators and Service are there
 
Back
Top