Symantec Backup Exec 11d RALUS 通信错误

发布于 2024-07-04 09:52:00 字数 1570 浏览 10 评论 0原文

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

眼睛会笑 2024-07-11 09:52:00

当然听起来像防火墙问题。 尝试停止 iptables,然后再次运行。 此外,RALUS 可以转储日志文件 - 这可能会提供更多信息。

我自己使用较旧的 UNIX 代理,它使用端口 6101 IIRC - 但我相信较新的客户端使用 tcp/10000 进行控制,使用 1024-65535 进行传输。

最后的手段是启动网络嗅探器。 ;)

Sure sounds like firewall issues. Try stopping iptables, and running again. Also, RALUS can dump a log file - which may give some more to go on.

I use the older UNIX agent myself, which uses port 6101 IIRC - but I believe that the newer client uses tcp/10000 for control and 1024-65535 for transfer.

Last resort is to fire up a network sniffer. ;)

旧情别恋 2024-07-11 09:52:00

为了澄清答案,解决方案是开放 1024-65535 之间的 TCP 端口。

iptables 看起来像这样:

[root@MYSERVER ~]# service iptables status  
Table: filter  
Chain INPUT (policy ACCEPT)  
target     prot opt source               destination  
RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0  

Chain FORWARD (policy ACCEPT)  
target     prot opt source               destination  
RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0  

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination  

Chain RH-Firewall-1-INPUT (2 references)  
target     prot opt source               destination  
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0  
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           icmp type 255  
ACCEPT     esp  --  0.0.0.0/0            0.0.0.0/0  
ACCEPT     ah   --  0.0.0.0/0            0.0.0.0/0  
ACCEPT     udp  --  0.0.0.0/0            224.0.0.251         udp dpt:5353  
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:631  
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:80  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:443  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:22  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5801  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5802  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5804   
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5901  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5902  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5904  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:9099  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:10000  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:1025  
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited

我执行了这个命令来添加新规则:

[root@MYSERVER ~]# iptables -I RH-Firewall-1-INPUT 14 -p tcp -m tcp --dport 1024:65535 -j ACCEPT

然后它们看起来像这样:

[root@MYSERVER ~]# service iptables status  
Table: filter  
Chain INPUT (policy ACCEPT)  
target     prot opt source               destination  
RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0  

Chain FORWARD (policy ACCEPT)  
target     prot opt source               destination  
RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0  

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination  

Chain RH-Firewall-1-INPUT (2 references)  
target     prot opt source               destination  
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0  
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           icmp type 255  
ACCEPT     esp  --  0.0.0.0/0            0.0.0.0/0  
ACCEPT     ah   --  0.0.0.0/0            0.0.0.0/0  
ACCEPT     udp  --  0.0.0.0/0            224.0.0.251         udp dpt:5353  
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:631  
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:80  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:443  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:22  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5801  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5802  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5804  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpts:1025:65535  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5901  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5902  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5904  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:9099  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:10000  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:1025  
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited  

当您验证它有效时保存 iptables:

[root@MYSERVER ~]# service iptables save

To clarify the answer, the solution was to open up the tcp ports from 1024-65535.

The iptables looked liked this:

[root@MYSERVER ~]# service iptables status  
Table: filter  
Chain INPUT (policy ACCEPT)  
target     prot opt source               destination  
RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0  

Chain FORWARD (policy ACCEPT)  
target     prot opt source               destination  
RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0  

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination  

Chain RH-Firewall-1-INPUT (2 references)  
target     prot opt source               destination  
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0  
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           icmp type 255  
ACCEPT     esp  --  0.0.0.0/0            0.0.0.0/0  
ACCEPT     ah   --  0.0.0.0/0            0.0.0.0/0  
ACCEPT     udp  --  0.0.0.0/0            224.0.0.251         udp dpt:5353  
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:631  
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:80  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:443  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:22  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5801  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5802  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5804   
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5901  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5902  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5904  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:9099  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:10000  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:1025  
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited

I executed this command to add the new rule:

[root@MYSERVER ~]# iptables -I RH-Firewall-1-INPUT 14 -p tcp -m tcp --dport 1024:65535 -j ACCEPT

Then they looked like this:

[root@MYSERVER ~]# service iptables status  
Table: filter  
Chain INPUT (policy ACCEPT)  
target     prot opt source               destination  
RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0  

Chain FORWARD (policy ACCEPT)  
target     prot opt source               destination  
RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0  

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination  

Chain RH-Firewall-1-INPUT (2 references)  
target     prot opt source               destination  
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0  
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           icmp type 255  
ACCEPT     esp  --  0.0.0.0/0            0.0.0.0/0  
ACCEPT     ah   --  0.0.0.0/0            0.0.0.0/0  
ACCEPT     udp  --  0.0.0.0/0            224.0.0.251         udp dpt:5353  
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:631  
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:80  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:443  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:22  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5801  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5802  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5804  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpts:1025:65535  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5901  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5902  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5904  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:9099  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:10000  
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:1025  
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited  

Save the iptables when you've verified that it works:

[root@MYSERVER ~]# service iptables save
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文