- Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
- Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Reply to: WIndows 2000 Server problem.
Collapse
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
- You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
- You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
- If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "WIndows 2000 Server problem."
Collapse
-
I thought it might be - during the boot process the server will always look for another DC to communicate with which is why the long boot time. Although you say removing the last 5 updates resolves this?Originally posted by wc2 View PostThanks Guys.
I ended up removing the last 5 updates via safe mode.
Got the server up
Turned off automatic updates
Kirk, It is a domain controller (Single)
Leave a comment:
-
Thanks Guys.
I ended up removing the last 5 updates via safe mode.
Got the server up
Turned off automatic updates
Kirk, It is a domain controller (Single)
Leave a comment:
-
-
I'd always check two basic things here...Originally posted by wc2 View PostI've got a windows 2000 server that gets to "preparing network connections" and simply does not move on.
The server is up as I can see its shares (Very slow)
It happened once before (I got the thing up in safe mode and reapplied SP4) and that seemed to work so I am thinking it's an Update issue.
Anyone had similar?
1) Check the name servers the windoze box is pointing at are up (and reachable). Use nslookup to verify this. Windoze hates having no name servers if its in a domain.
2) Check in the task manager (processes tab) that something is not burning the CPU time, sort the column by utilisation by clicking on it. The system idle loop process should be at the top of the list.
Have a quick look at those.
Leave a comment:
-
WIndows 2000 Server problem.
I've got a windows 2000 server that gets to "preparing network connections" and simply does not move on.
The server is up as I can see its shares (Very slow)
It happened once before (I got the thing up in safe mode and reapplied SP4) and that seemed to work so I am thinking it's an Update issue.
Anyone had similar?Tags: None
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers

Leave a comment: