You'll have a real mess on your hands if you keep fooling with the service
dependencies like that. Sooner or later it *will* blow up in your face and
you may end up reloading all effected machines from scratch.
Contact Orinoco and explain the situation to them. It is probably something
they have gotten calls about on a regular basis. They are the ones who
designed thier products and will be the best ones to create a viable
solution.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"barb" <barb@rainshadowcchs> wrote in message
news:1d26801c453d1$e0746050$(E-Mail Removed)...
> Hello,
>
> I am a network admin (newbie) for a small charter school.
> I am running Windows Server 2003, and all xp pro
> workstations on an Orinoco wireless network.
>
> Here's the problem. I am getting an Event ID 5719 in the
> event viewer - no DC available. What's happening is that
> the Netlogon service is looking for the DC before the the
> wireless network has time to get going. I have verified
> this by hardwiring a computer into the network (and my
> workstation is also wired and works fine) and it logs on
> fine.
>
> I have tried making Netlogon dependant on tcpip, but it
> still tries to find the dc first. I even made netlogon
> dependant on the CD burner service which fires up way
> late in the process, but it still looks for the dc
> earlier! The upshot is that it logs the user on with
> cached credentials (yes, I know I can turn that off, but
> that doesn't really fix the problem) and group policies
> are not applied.
>
> I found a regedit script for delaying netlogon for dial
> up connections, but for the life of me cannot find one to
> just delay the start of netlogon period. I have looked
> and looked for a solution to this problem, but can't find
> one. Of course, I'm really new at all this, so there may
> be something simple I have overlooked. I sure hope so!
>
> Thanks for helping,
> Barb
> Rainshadow Community Charter High School