I am having a weird problem. After a ticket was opened with Symantec due to a failure to connect to client, I was asked to shut off all 3 profiles in the Windows firewall and try to connect. It did and I was able to run a backup. When I turned the firewall back on I was still able to connect and run backups, so it appeared that there was a glitch in the firewall that was corrected with a stop and start of the firewall. This appeared to have happened after an update was loaded. I few days ago, it happend again and it was after an update. So I did the same thing and everyhting ran fine. Now it appears to be getting worse and after only a couple of days the connection was failing again. I checked to firewall inbound rules and the Netbackup ports are allowed, but only the the domain profile, client is running 2008. My question is, does this sound like a Netbackup issue or a Windows issue? I can't see it being Netbackup as I can backup the server as long as the firewall off and for some time after it's turned back on. Thanks, Dan Seymour

I had a recent bout with the windows guys on a new server. And I kept telling them I could not connect, check the firewall policy. They kept saying it was applied.... but I still could not connect. that is when one of the 3 guys looking at it found it was not in the correct group. Once they fixed that it worked. So just something else about windows I have to remember to have looked at when I have issues with a server.

Windows Firewall problems

J_H_Is_gone
Level 6
15 years ago
I had the same issue when we first got 2008 servers.

So we have a firewall policy to open up the ports.
But a second issue was that
the server's machine account must be in the right active directory ou container for the firewall policy to work.
Andy_Welburn
Level 6
15 years ago

directory ou container for the firewall policy to work."

That I wasn't aware of - good shout Judy.
smwoodcrafts
Level 6
15 years ago
Thank you. I just wanted to make sure I wasn't missing something.

smwoodcrafts
J_H_Is_gone
Level 6
15 years ago
I had a recent bout with the windows guys on a new server.
And I kept telling them I could not connect, check the firewall policy.
They kept saying it was applied.... but I still could not connect.

that is when one of the 3 guys looking at it found it was not in the correct group.
Once they fixed that it worked.

So just something else about windows I have to remember to have looked at when I have issues with a server.
smwoodcrafts
Level 6
15 years ago
What do you mean by not in the correct group?
A little more is that this backup was working fine. Then it started failing. It seemed to coincide with a Windows update that was applied, but I can't be 100% on that.
The ports are allowed in the domain profile of the firewall, shich is where it appears it's supposed to be.

Thanks,

smwoodcrafts
J_H_Is_gone
Level 6
15 years ago
in the active directory ou container.

I hae no idea what that is, just that is what the windows guys said they had to do to fix my issue with that new 2008 server.
smwoodcrafts
Level 6
15 years ago
ok Thanks. I'll see if I can get them to stop passing the buck and actually check it out.

smwoodcrafts
Andy_Welburn
Level 6
15 years ago

"Organizational units are Active Directory containers into which you can place users, groups, computers, and other organizational units and to which you can assign Group Policy settings or delegate administrative authority."
smwoodcrafts
Level 6
14 years ago
I do have an update on this. It isn't a solution, but it stopped being a problem. After all the agruements about needing the firewall on and not being able to run without it. They decided they didn't want to deal with finding a solution and turned the firewall off. Bandaid fix but I no longer have the problem.
Will_Restore
Level 6
14 years ago
So was it group or firewall? You marked the group issue as solution.