Brilliant! Win2k3 SP2 enables the firewall on a new install - hillarity ensues!

[SunnyD]

Aight, my server took a major hard drive dump last week, unrecoverable. The hard drive has been replaced, and unfortunately I had no backup - it was too young. So a fresh install of Win2k3 gets thrown on, updated, and wow, cool, SP2 is out!

I configure the domain, the dns, dhcp, IIS, etc... go to test everything out and NOTHING.

Everything "appears" to be configured correctly, but nothing. The server is there, ports on the router are forwarded, but nothing, not even from inside the network. My client PC's aren't even getting DHCP addresses or hit the server. W.T.F.?

So I figure something stupid happened to windows, and reinstall the whole shebang, but no, same thing happens. The server can see the outside world obviously, as it can download updated and patches and even SP2... wtf.!

Then on a whim, something clicked and I popped into the control panel, and looked at the security settings. "Hmm, let's turn off the firewall and see what happens..." Poof, my clients now have DHCP addresses, I can resolve DNS, and the server is all together there.

WOW. Just... WOW. This service pack is going to cause a few little headaches I would bet.

 

[BigPete]

Release Notes! Brilliant!

 

[IamDavid]

thanks for the heads up

 

[Robor]

Was the firewall service set to manual or disabled prior to installing SP2?

 

[John]

Originally posted by: SunnyD
WOW. Just... WOW. This service pack is going to cause a few little headaches I would bet.

The same thing happened when XP SP2 was rolled out.

 

[Robor]

Originally posted by: John

Originally posted by: SunnyD
WOW. Just... WOW. This service pack is going to cause a few little headaches I would bet.

The same thing happened when XP SP2 was rolled out.

Yes but XP SP2 introduced the firewall. Win2K3 server already has the firewall. I'm pretty sure I've seen the XP firewall get enabled during a Windows Update if it was set to 'manual' but never seen it enabled if it was set to 'disabled'.

 

[funkbass81]

Originally posted by: SunnyD
Aight, my server took a major hard drive dump last week, unrecoverable. The hard drive has been replaced, and unfortunately I had no backup - it was too young. So a fresh install of Win2k3 gets thrown on, updated, and wow, cool, SP2 is out!

I configure the domain, the dns, dhcp, IIS, etc... go to test everything out and NOTHING.

Everything "appears" to be configured correctly, but nothing. The server is there, ports on the router are forwarded, but nothing, not even from inside the network. My client PC's aren't even getting DHCP addresses or hit the server. W.T.F.?

So I figure something stupid happened to windows, and reinstall the whole shebang, but no, same thing happens. The server can see the outside world obviously, as it can download updated and patches and even SP2... wtf.!

Then on a whim, something clicked and I popped into the control panel, and looked at the security settings. "Hmm, let's turn off the firewall and see what happens..." Poof, my clients now have DHCP addresses, I can resolve DNS, and the server is all together there.

WOW. Just... WOW. This service pack is going to cause a few little headaches I would bet.

rtfm ftw!

 

[Genx87]

Interesting, however I turn off the FW through group policy so I never knew.

 

[SunnyD]

Originally posted by: funkbass81

Originally posted by: SunnyD
Aight, my server took a major hard drive dump last week, unrecoverable. The hard drive has been replaced, and unfortunately I had no backup - it was too young. So a fresh install of Win2k3 gets thrown on, updated, and wow, cool, SP2 is out!

I configure the domain, the dns, dhcp, IIS, etc... go to test everything out and NOTHING.

Everything "appears" to be configured correctly, but nothing. The server is there, ports on the router are forwarded, but nothing, not even from inside the network. My client PC's aren't even getting DHCP addresses or hit the server. W.T.F.?

So I figure something stupid happened to windows, and reinstall the whole shebang, but no, same thing happens. The server can see the outside world obviously, as it can download updated and patches and even SP2... wtf.!

Then on a whim, something clicked and I popped into the control panel, and looked at the security settings. "Hmm, let's turn off the firewall and see what happens..." Poof, my clients now have DHCP addresses, I can resolve DNS, and the server is all together there.

WOW. Just... WOW. This service pack is going to cause a few little headaches I would bet.

rtfm ftw!

Oh I'm sorry, I wasn't even aware that SP2 was released when I setup this box. Just one of those handy little automatic updates that I didn't pay attention to.

 

[funkbass81]

so you just patch and install service packs without testing first? ;confused

 

[stash]

Just one of those handy little automatic updates that I didn't pay attention to.

Nice try, but SP2 won't be available on automatic updates until June. It is only available by manually going to Windows Update or downloading the network install.

 

[Smilin]

Windows Server 2003 service pack 2 does not enable the firewall that I am aware of.

I tried to reproduce this but it doesn't repro.

Has anyone else seen this? I think you might have something else going on SunnyD. Post installation lockdown that was introduced in SP1 maybe? Did you complete the checklist?

 

[SunnyD]

Originally posted by: Smilin
Windows Server 2003 service pack 2 does not enable the firewall that I am aware of.

I tried to reproduce this but it doesn't repro.

Has anyone else seen this? I think you might have something else going on SunnyD. Post installation lockdown that was introduced in SP1 maybe? Did you complete the checklist?

Ya know, come to think of it, after SP2 installed, the checklist never came back up to finalize the server install.

 

[Robor]

Originally posted by: funkbass81

Originally posted by: SunnyD
Aight, my server took a major hard drive dump last week, unrecoverable. The hard drive has been replaced, and unfortunately I had no backup - it was too young. So a fresh install of Win2k3 gets thrown on, updated, and wow, cool, SP2 is out!

I configure the domain, the dns, dhcp, IIS, etc... go to test everything out and NOTHING.

Everything "appears" to be configured correctly, but nothing. The server is there, ports on the router are forwarded, but nothing, not even from inside the network. My client PC's aren't even getting DHCP addresses or hit the server. W.T.F.?

So I figure something stupid happened to windows, and reinstall the whole shebang, but no, same thing happens. The server can see the outside world obviously, as it can download updated and patches and even SP2... wtf.!

Then on a whim, something clicked and I popped into the control panel, and looked at the security settings. "Hmm, let's turn off the firewall and see what happens..." Poof, my clients now have DHCP addresses, I can resolve DNS, and the server is all together there.

WOW. Just... WOW. This service pack is going to cause a few little headaches I would bet.

rtfm ftw!

Thanks for contributing. :roll: I hope your 100th post is better than this one.

 

[funkbass81]

wait, so whose fault is it that he never read the documentation, and doesn't pay attention to what updates are being deployed? BTW, you contributed nothing yourself. glass houses and all

 

[funkbass81]

http://technet2.microsoft.com/WindowsSe...d4-b41f-6922de18c6ac1033.mspx?mfr=true

 

[funkbass81]

http://technet2.microsoft.com/WindowsSe...d4-b41f-6922de18c6ac1033.mspx?mfr=true

 

[funkbass81]

http://technet2.microsoft.com/WindowsSe...d4-b41f-6922de18c6ac1033.mspx?mfr=true

 

[smashp]

Originally posted by: SunnyD
Aight, my server took a major hard drive dump last week, unrecoverable. The hard drive has been replaced, and unfortunately I had no backup - it was too young. So a fresh install of Win2k3 gets thrown on, updated, and wow, cool, SP2 is out!

I configure the domain, the dns, dhcp, IIS, etc... go to test everything out and NOTHING.

Everything "appears" to be configured correctly, but nothing. The server is there, ports on the router are forwarded, but nothing, not even from inside the network. My client PC's aren't even getting DHCP addresses or hit the server. W.T.F.?

So I figure something stupid happened to windows, and reinstall the whole shebang, but no, same thing happens. The server can see the outside world obviously, as it can download updated and patches and even SP2... wtf.!

Then on a whim, something clicked and I popped into the control panel, and looked at the security settings. "Hmm, let's turn off the firewall and see what happens..." Poof, my clients now have DHCP addresses, I can resolve DNS, and the server is all together there.

WOW. Just... WOW. This service pack is going to cause a few little headaches I would bet.

Only for the people that dont know how to manage or support servers.

 

[ITJunkie]

Hey...on new builds it happens. I recently did a new build as well and forgot to turn off the firewall before leaving the office...lucky for me I live reasonably close.
I don't know/think SP2 had anything to do with it as much as I forgot to turn it off to begin with.
In fact, SP2 DID NOT turn the firewall back on on my other servers when I installed it. Like me, you probably forgot to disable it after re-installing Win03.

 

[PingSpike]

You only need to click reply once to post a reply. RTFM.

 

[Robor]

Originally posted by: funkbass81
wait, so whose fault is it that he never read the documentation, and doesn't pay attention to what updates are being deployed? BTW, you contributed nothing yourself. glass houses and all

STFU. Now I've contributed as much as you.

 

[funkbass81]

nothing intelligent to add to this thread. why am i not surprised? at least i gave him three links that would be helpful if he took the time to actually read.

 

[spyordie007]

Originally posted by: Smilin
Windows Server 2003 service pack 2 does not enable the firewall that I am aware of.

I tried to reproduce this but it doesn't repro.

Has anyone else seen this? I think you might have something else going on SunnyD. Post installation lockdown that was introduced in SP1 maybe? Did you complete the checklist?

I haven't seen this behavior anywhere either (on upgrade or new installs), and the release notes don't say anything about it either:
http://technet2.microsoft.com/WindowsSe...d33-ace0-225d31b7ab751033.mspx?pf=true

About the closest thing I could find was that SP2 automatically enables firewall per port authentication, but this wouldn't cause the issues described.

SunnyD can you give more information about how you did your installs (at what point the SP was applied, etc.)?

 

[Robor]

Originally posted by: funkbass81
nothing intelligent to add to this thread. why am i not surprised? at least i gave him three links that would be helpful if he took the time to actually read.

I discussed the issue earlier in the thread. Check replies 3 and 5. If you're still having trouble see HERE.

You told him, 'rtfm ftw' then - after I called you on it - you posted the same link 3 times.

Now go back under your bridge.