Interesting problem with 3 blade servers and Win 2008 Server
We moved into a new office not so long ago and had an IT firm do all the wire runs, phone system and setup the new servers we have. 3 HP blade servers with a SML2048 switch (which, I am regretting, we have went through two switches in a matter of months, and doing research others have been having the same problem with it).
Well anyway, each blade server has Windows 2008 Server running on it. We have one server take care of most of the work load, DHCP, DNS, Active, etc. (lets call it Server A).
Our second server (Server 
is our primary file server. Our third server (Server C) is our terminal server.
Okay, a few weeks ago we were having problems with Server C. We could not RDP into it at all, in fact the only way into it was through our KVM we have setup for the servers.
I took a look and figured it must be a issue with the licensing server (which is the same server as the terminal server) but I could not do anything about it, the IT Firm had the information for it so we called them in to uninstall and reinstall the licensing server. Nothing. (We still have contact with them because they are still working on our office in the city).
What they found it out to be, which to me is weird, maybe you guys its not, but it was the fact that Server C's firewall was not on. Once the service was enabled and started, we could communicate with the server again.
Well today I wake up to find that all the servers took a crap. Initially over the phone it sounded like the file server (Server was down, I tried RDPing into the terminal server, nothing. I pinged it and got nothing making me think the switch was down.
Got to the site, took a look at Server B - I was able to ping Server C with it, but not ping Server A. I went onto Server A and tried to ping B, nothing, C worked. I looked at the switch and restarted it (which seems to be the fixes for this model, temporary anyway).
Still nothing. I took my laptop out and connected it to the switch and noticed that the DHCP server was not handing out IPs.
I was stumped, I restarted all the servers, etc. Nothing.
One last thing we tried with the suggestion of another IT person was to enable the firewall on the file server. Well we did, and boom! Was able to ping it from Server A. I then thought, well if I cannot still ping Server A let me enable the firewall as well. Well I did and that worked!
Now, internet was up, people were getting IPs and access to files.
Here is my question after all of this. Why, out of no where does the servers suddenly require the firewalls (Windows Firewall) to be active? They have been running for a few months with them off, and now all of the sudden they need to be on to establish any type of connectivity?
That leads to the second question, usually when I had a problem with a computer I would shut the firewall off and be able to access it, yet this is reversal.
I am a networking guy so my server knowledge is not that great so any help would be great guys. The IT firm has no clue why this is happening either.
Thanks!
-Jon
is our primary file server. Our third server (Server C) is our terminal server.Okay, a few weeks ago we were having problems with Server C. We could not RDP into it at all, in fact the only way into it was through our KVM we have setup for the servers.
I took a look and figured it must be a issue with the licensing server (which is the same server as the terminal server) but I could not do anything about it, the IT Firm had the information for it so we called them in to uninstall and reinstall the licensing server. Nothing. (We still have contact with them because they are still working on our office in the city).
What they found it out to be, which to me is weird, maybe you guys its not, but it was the fact that Server C's firewall was not on. Once the service was enabled and started, we could communicate with the server again.
Well today I wake up to find that all the servers took a crap. Initially over the phone it sounded like the file server (Server
was down, I tried RDPing into the terminal server, nothing. I pinged it and got nothing making me think the switch was down.Got to the site, took a look at Server B - I was able to ping Server C with it, but not ping Server A. I went onto Server A and tried to ping B, nothing, C worked. I looked at the switch and restarted it (which seems to be the fixes for this model, temporary anyway).
Still nothing. I took my laptop out and connected it to the switch and noticed that the DHCP server was not handing out IPs.
I was stumped, I restarted all the servers, etc. Nothing.
One last thing we tried with the suggestion of another IT person was to enable the firewall on the file server. Well we did, and boom! Was able to ping it from Server A. I then thought, well if I cannot still ping Server A let me enable the firewall as well. Well I did and that worked!
Now, internet was up, people were getting IPs and access to files.
Here is my question after all of this. Why, out of no where does the servers suddenly require the firewalls (Windows Firewall) to be active? They have been running for a few months with them off, and now all of the sudden they need to be on to establish any type of connectivity?
That leads to the second question, usually when I had a problem with a computer I would shut the firewall off and be able to access it, yet this is reversal.
I am a networking guy so my server knowledge is not that great so any help would be great guys. The IT firm has no clue why this is happening either.
Thanks!
-Jon
Currently :study:: A+ (self study and in class)| Network+ | CCNA (self study and in class) | A.A.S. Network Design and Administration (Almost done!)
Comments
-
Jonk
Member Posts: 39 ■■□□□□□□□□
Just got a call this morning that Server A and Server B is not reachable again. Server C can be RDPed, but cannot login due to the domain being down. I bet its the firewall settings. If we turn it off now, everything will work.
WTF?Currently :study:: A+ (self study and in class)| Network+ | CCNA (self study and in class) | A.A.S. Network Design and Administration (Almost done!) -
Jonk
Member Posts: 39 ■■□□□□□□□□
Update:
Went to site again to fix the issue. IT Firm showed up and took a look, editing some settings, etc. but I still had the question: Why is it doing this every night?
So after they left I took a look at the logs and notice on all three servers, a security information notification stating that the firewall has been shut down, then another one stating the firewall status from automatic is now disabled.
I looked before those notifications and noticed that the group policy was loaded successfully. So I went through the policy on the DC and noticed that the firewall policy was configured - took a look and it was configured to be disabled.
I changed that to automatic, noted that the new group policy was taken in successfully the event log, and we will see how that goes.
I did notice that it looks like the policy was changed on the 8th to disable the firewall, which now explains why they have been having problems with this.
How fun.Currently :study:: A+ (self study and in class)| Network+ | CCNA (self study and in class) | A.A.S. Network Design and Administration (Almost done!)