Ben Keyser
asked on
Blocked ports on sbs 2011 server
Good day
I am stuck with an SBS 2011 server that seems to block all ports incoming. At first I thought the router I used for testing may be a problem, so I switched the server to a router that is currently used on an SBS box without problems. Ports still blocked. Quickest check for me now is simply disable firewall on the server - Firewall settings in control panel and stop the firewall service. Still, incoming ports (25, 443, 3389) stay blocked.
I verified this with MX toolbox as well as http://www.yougetsignal.com and http://canyouseeme.org/
Any ideas?
As I said, the router on the server at this moment is the same router I use on my own server - the ports are open and working on my server. But on this one they show blocked.
I am stuck with an SBS 2011 server that seems to block all ports incoming. At first I thought the router I used for testing may be a problem, so I switched the server to a router that is currently used on an SBS box without problems. Ports still blocked. Quickest check for me now is simply disable firewall on the server - Firewall settings in control panel and stop the firewall service. Still, incoming ports (25, 443, 3389) stay blocked.
I verified this with MX toolbox as well as http://www.yougetsignal.com and http://canyouseeme.org/
Any ideas?
As I said, the router on the server at this moment is the same router I use on my own server - the ports are open and working on my server. But on this one they show blocked.
ASKER
No 3rd party firewall (or antivirus yet, for that matter. Both servers although completely independent, same IPS
On the new box, is everything working properly? (Telnet to localhost should work, if not, it wasn't ever a firewall issue, the software wasn't working properly in the first place)
Try running the SBS BPA - fix anything it finds. Then run the FMNW, then restart the SBS.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just pointing out that the BPA takes about 5 minutes and the FMSW takes even less. It would have been helpful if you had reported on the results of these two tools.
ASKER
Yes Larry, you are right. But BPA leadds to "fix this, investigate here etc". Taking 5 minutes to run BPA is not the issue. I was out of time trying to fix it and BPA was not going to fix anything.
I appreciate the input and I realise everyone one EE is computing for points but I was at the cut-off point. I could not spend anymore time. This is a live server that went down following a bad software install. It had a history starting Saturday morning already. And now it is up and running 100%, and I am restoring the backup. Had I spent more time investigating (possible) solutions; well, that is what I would have been doing now. I made a judgement call and that was no more investigating. Scrub. It was the right call.
Once again, I appreciate your concern and input, but I stand by my decision
I appreciate the input and I realise everyone one EE is computing for points but I was at the cut-off point. I could not spend anymore time. This is a live server that went down following a bad software install. It had a history starting Saturday morning already. And now it is up and running 100%, and I am restoring the backup. Had I spent more time investigating (possible) solutions; well, that is what I would have been doing now. I made a judgement call and that was no more investigating. Scrub. It was the right call.
Once again, I appreciate your concern and input, but I stand by my decision
ASKER
Scrubbed the server. Could not spend more hours trying to resolve the issue
If you did that, I agree, something strange is up (maybe even 3rd party firewall on the server?)