Re: Help, MS tech support is useless

After reading thru these posts, I would say that you have a couple of issues
that are causing the problem.

I would first disable your policy that renames your admin account. I would
not want to try and troubleshoot a problem without knowing that it's not an
authenication problem.

Secondly, I would say that you have a DNS issue. You probably could get by
with shutting down the DNS server service and testing before you uninstall.
If you have another server available you could introduce that one as your
DNS server (keep your existing DNS structure) until you have yours back
online. A simple uninstall, reboot and installation will probably cure your
woes. One last thing, is make sure that your hardware firewall has not
changed it's pointer for DNS. I've had this happen to me before on some low
end firewalls.

A


"Nathan Weldon" <nweldon@xxxxxxxxxxxxxxxxx> wrote in message
news:evZ2UKvtFHA.2792@xxxxxxxxxxxxxxxxxxxxxxx
> By that I meant my hardware firewall. I do not run a software firewall on
> the server as of yet. It is my intention to do so eventually, but I'd like
> to get it to run sp1 first & foremost.
> "Robert Moir" <robspamtrap+msnews@xxxxxxxxx> wrote in message
> news:OPZlPhltFHA.256@xxxxxxxxxxxxxxxxxxxxxxx
>> Nathan Weldon wrote:
>>> 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.
>>
>> Could it be the "third party" firewall.
>>
>
>


.

Relevant Pages

  • Re: For Microsoft Partners and Customers Who Cant Download or Access
    ... to reconfigure the firewall, but to use a static IP on your client ... and to make sure that the DNS server entries on the client are ... Microsoft for msdn2.microsoft.com. ... use a static IP and set the DNS server addresses to the DNS ...
    (microsoft.public.dotnet.general)
  • Re: loss of SOME connectivity
    ... I "think" it is DNS. ... Yes, I can ping the router, AND the ISP DNS. ... I cannot connect the inet cable directly to the server because the inet is ... MS firewall not started. ...
    (microsoft.public.windows.server.sbs)
  • Re: E-Mail Address Cant Receive E-Mail from *Some* External Organizations
    ... The fact that _some_ messages are delivered is because they are sent from different IPs, so double-check your firewall settings. ... So, that looks right to me, anyway; both resolve to the proper IP address of the external interface for our firewall, and the only difference is that for "company.org" our ISP's mail server acts as a backup server in case our internal mail server is down. ... However, if I send a message to "me@xxxxxxxxxxxxxxxx" from my Yahoo e-mail account, I get an NDR returned to my Yahoo account. ... I have checked with our ISP who handles our DNS settings, and they indicate that all appears to be in order with our DNS and MX records. ...
    (microsoft.public.exchange.admin)
  • RE: Firewall Rule Set not allowing access to DNS servers?
    ... I changed the DNS rules as you suggested, and the firewall works perfectly - ... > # Allow out access to my ISP's Domain name server. ... > so your udp packets never match this rule and default to ...
    (freebsd-questions)
  • Re: Server inaccessible
    ... Any possibility firewall settings ... I also updated the Intel 1000 CT network driver on the server. ... I reenabled the Default Domain Controllers Policy and the Default ... Firewall policy (since the client PCs was prevented from disabling the ...
    (microsoft.public.windows.server.sbs)