Re: Help, MS tech support is useless

Just a thought, I have a policy in effect that renames the administrator
account. Could that prevent the system from being able to start services
when it boots?
"WILDPACKET" <WILDPACKET@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B5E8AAF3-01E7-4037-B90C-09A51F23C0BA@xxxxxxxxxxxxxxxx
> Nathan:
>
> Shut down all the unwanted services and set them to manual and restart
> your
> box.
>
> You need to troubleshoot now and as you go along turn on the services one
> by
> one.
> Hopefully this will lead you some where.
>
> WP
> *********************************************************
>
>
> "Nathan Weldon" wrote:
>
>> It is a DNS server as well. The network service is not starting.
>> Basically
>> the machine cannot communicate with anything. Can't even run rsop to
>> check
>> policy settings, get access denied. I can ping it for about two minutes
>> after rebooting, but as soon as windows gets about half loaded, no dice
>> anymore. So I was thinking driver issues, but I have the latest drivers
>> from
>> HP so I don't know what else it could possibly be. I've got another
>> server
>> at the other location that installed the sp just fine, but it isn't a DC.
>> Basically any DC that I install the sp on, craps out once it is rebooted.
>> Am
>> using HP proliant servers, the one I'm working on is brand new, just got
>> it
>> last week.
>> "mark" <mark)lt@xxxxxxxxxxx> wrote in message
>> news:%230J5PujtFHA.460@xxxxxxxxxxxxxxxxxxxxxxx
>> > almost certainly going to be your dns settings, maybe they are pointing
>> > to
>> > a non existent IP, or maybe a public DNS ?
>> >
>> > "Nathan Weldon" <nweldon@xxxxxxxxxxxxxxxxx> wrote in message
>> > news:Oke7dCjtFHA.996@xxxxxxxxxxxxxxxxxxxxxxx
>> >>I just installed sp1 for server 2k3 on a DC, the only DC at a satelite
>> >>office. I installed AD before sp1 so maybe that is my downfall but too
>> >>late to do anything about it now. AFter rebooting the server takes
>> >>forever
>> >>and a day to start up, displays "Setting up your network connections"
>> >>for
>> >>a good 20 minutes. After I'm finally able to log in, none of my network
>> >>connections function. My initial thought was windows firewall, but I
>> >>have
>> >>a policy in effect that disables it becuase it caused nothing but
>> >>trouble
>> >>and I use a 3rd party one anyway. I think it has something to do with
>> >>the
>> >>security configuration wizard which is supposed to run after rebooting,
>> >>but it doesn't, and I can't even find it in the control panel. This
>> >>happened my other location on my DC/Exchange Server, after 6 hours on
>> >>the
>> >>phone with MS I gave up and uninstalled the service pack.
>> >>
>> >
>> >
>>
>>
>>


.

Relevant Pages

  • RE: SBS 2003 R2 - Please Help
    ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading of 2003 domain to 2008 domain, checklist, questions?
    ... Personally i always use the way of fresh install where possible. ... Exchange 2007 will work in the 2008 domain on a 2003 server. ... On the old server open DNS management console and check that you are running ... you can check the version with "schupgr" in a command prompt. ...
    (microsoft.public.windows.server.setup)
  • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
    ... dynamic updates and create PTR records in DNS. ... tracking is easier from the server. ... I don't install dhcp on the servers, ... I couldn't get the client to ...
    (microsoft.public.windows.server.sbs)
  • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
    ... tracking is easier from the server. ... The only time I have seen the connectcomputer error you mentioned about DNS ... I don't install dhcp on the servers, ... I couldn't get the client to ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading of 2003 domain to 2008 domain, checklist, questions?
    ... Personally i always use the way of fresh install where possible. ... Exchange 2007 will work in the 2008 domain on a 2003 server. ... On the old server open DNS management console and check that you are running ... and "netshell dhcp restore" command ...
    (microsoft.public.windows.server.setup)