network booting windows server 2003

March 8, 2012 at 08:06:56
Specs: Windows 7
I have a windows server 2003 and several clients that boot up on the network so the drives r all located on the server.

My problem is that often when booting up the clients they freeze on the boot process, they get their ip and stops at the TFT... then tries several times with timeouts before giving up.

Then the only solution I can do is either restart the "NT Wrapper" service, works mostly, or simply reboot the server.

No bluescreen or connection issues...

Any advice or suggestions to solve this problem?


See More: network booting windows server 2003

Report •

#1
March 8, 2012 at 10:10:48
server providing the ip address via dhcp?
workstation pointed to the server for dns?
what is TFT?
when you say it gives up what is the specific error?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
March 9, 2012 at 00:04:46
Server is providing IP via dhcp yes.

Clients are pointed to the dns.

little spelling error there... not TFT but TFTP.

When it happens it's loading the TFTP, then timeouts several times before it gives up and say disk error press enter.


Report •

#3
March 9, 2012 at 07:00:32
Appears you are using remote boot services

http://msdn.microsoft.com/en-us/lib...

Your server is having issues. Any recent changes like newly installed software or updates?
Do you have backups to before this issue began?
Doesn't appear you set this up. Ability to contact who did?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Related Solutions

#4
March 9, 2012 at 08:28:54
It's a system set up long before my time and I've been told it's always been a problem, but never been done anything about it so backups aint worth it, therefor no recent soft- or hardware changes could had been the cause. If so it would had been back at the setup of the system.

Whoever did the whole setup isn't available anymore and I only have limited knowledge of how it works.

I've tried checking on the server for events that could be connected to this issue, but haven't been able to see anything that relate to this.


Report •

#5
March 9, 2012 at 15:15:59
Review the link I gave you which will give you clues to the proper setup you can review.

run chkdsk /f on all volumes
run disk cleanup
run defrag on all volumes

check dns and network setups

This server is the Titanic and its headed straight for the iceburg.
Start planning NOW

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Ask Question