Event log error "Windows cannot access the file gpt.ini" on SBS Server 2003

A few days ago I rebooted a server and upon booting back up, it hung at "Preparing Network Connections" for hours. Today, I looked in the APPLICATION event log and see about 1000 errors that read the following:

EVENT ID: 1058

Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=SHCC,DC=local. The file must be present at the location <\\SHCC.local\sysvol\SHCC.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (The semaphore timeout period has expired. ). Group Policy processing aborted.

I am also gettings EVENT ID: 1030

Please throw some suggestions my way
jfilmore3Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hardeep_SalujaCommented:
Hi.. Run rsop.msc and you should be getting yellow exclamation on user or computer configuration.
Right click on it>go to properties to see the error information.

Also, when you take out network cable, does server starts quicker?

Most likely in these cases, issues is with network card.. you can try to replace it or also try to change speed from auto to 100 Full Duplex in device manager> network card properties>advanced tab

this should resolve your issue for sure..
Please let me know
Hardeep Saluja
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ChiefITCommented:
Check your FRS event logs for errors in the 13000's

It sounds like you are having problems with DNS. This will cause problems with replication and can put you in journal Wrap. That will cause 1030 and 1058 event errors. So, we will need to fix DNS prior to fixing Journal Wrap issues. But, let's see if you are in Journal Wrap, first.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.