Nevermind. Problem solved.
Through testing all the images, and using differenct computers, I never
changes the network port I was using.
Moved the network cable over 1 jack and everythiing starting humming along.
If anyone has any ideas on how I could successfully boot to RIS, select an
image, and the process gets past loading all the drivers and then a bad
connection affects the results (every time!) I would be glad to hear it.
Doesn't make any sense to me; but oh-well, problem solved!
"Matt" wrote:
> This past week, all my images I use in RIS create stop error 0xBB
> Network_Iniitialiation_Error during the texted based installation. Appears
> to consistently happen between "Starting Windows" and checking for the
> harddrive. I get this error from ALL images, including CD based, and I have
> tested this using 3 different machines.
>
> The only changes that I am aware of were:
> During the same week I was creating multiple images per day to tweak the
> installation options for a new IBM laptop. I would also cleanup all the
> un-needed images as I made progess. I made no changes to exisiting images.
>
> The last hot fix that was installed appears to be KB930178 on 4/11.
>
> Problem began on 4/19. I deployed 2 computers without any problems n the
> morning; afternoon I received my first stop error. Have not been working
> since.
>
> This server also runs IIS and WSUS 2 and DFS root/replication
> Build: Windows Server 2003 SP1
> RAM: 2 GB
> HDD: 5 GB Available on RIS partition
>
> No errors for RIS/BINLSVC services
> risetup -check does not report any problems
> WSUS does have a fault in the application pool approx 1 time per day
>
> I will put ris in debug accourding to KB236033 and will report any findings
> here.
>
> Any help would be greatly appriciated. I need to get this working again asap.
>
> Thanks
> Matt
|
Similar Threads
Linear Mode
