Quote:
Originally Posted by TB0ne
No, probably not. As has been mentioned to you before, you are NOT ALLOWED to discuss the contents of the RHCE test/labs, per the agreement you signed when you took it. Don't be surprised if the moderators close this thread.
You should go back to your networking basics. If you don't have a route from one network to the other, that will cause it to not work. If you don't allow traffic on that port to go through the firewall between those two networks...that will cause it not to work. Selinux restricting access?
Also, what diagnostics have you performed? What have you tried?
|
I wouldn't discuss about the RHCE test i want to discuss the lab/real case for the topic in the books for the RHCE only man.
Quote:
Originally Posted by TB0ne
If you don't have a route from one network to the other,
|
[root@serverX station6]# ping 172.24.5.6
PING 172.24.5.6 (172.24.5.6) 56(84) bytes of data.
64 bytes from 172.24.5.6: icmp_seq=1 ttl=64 time=0.324 ms
64 bytes from 172.24.5.6: icmp_seq=2 ttl=64 time=0.353 ms
64 bytes from 172.24.5.6: icmp_seq=3 ttl=64 time=0.346 ms
64 bytes from 172.24.5.6: icmp_seq=4 ttl=64 time=0.308 ms
[root@BT ~]# ping serverx.example.com
PING serverx.example.com (192.168.114.129) 56(84) bytes of data.
64 bytes from serverx.example.com (192.168.114.129): icmp_seq=1 ttl=64 time=0.269 ms
64 bytes from serverx.example.com (192.168.114.129): icmp_seq=2 ttl=64 time=0.340 ms
64 bytes from serverx.example.com (192.168.114.129): icmp_seq=3 ttl=64 time=0.287 ms
^C
Quote:
Originally Posted by TB0ne
If you don't allow traffic on that port to go through the firewall between those two networks
|
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:139
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:445
10 780 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:137
0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:138
Quote:
Originally Posted by TB0ne
Also, what diagnostics have you performed? What have you tried?
|
I tried turn off the fw in the server then from pc3 :
#
[root@BT ~]# smbclient //serverx.example.com/common -U kratos
Enter kratos's password:
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
The same issue ....So it is not fw issue.
Also looking hint from /var/log/samba and see
[2013/08/22 16:17:07.062227, 0] lib/access.c:338(allow_access)
Denied connection from 172.24.5.6 (172.24.5.6)
[2013/08/22 16:17:58.297683, 0] lib/access.c:338(allow_access)
Denied connection from 172.24.5.6 (172.24.5.6)
[2013/08/22 16:17:58.296399, 0] lib/access.c:338(allow_access)
Denied connection from 172.24.5.6 (172.24.5.6)
[2013/08/22 16:17:58.313968, 0] lib/access.c:338(allow_access)
Denied connection from 172.24.5.6 (172.24.5.6)
Quote:
Originally Posted by TB0ne
Selinux restricting access?
|
samba_create_home_dirs --> off
samba_domain_controller --> off
samba_enable_home_dirs --> off
samba_export_all_ro --> on
samba_export_all_rw --> on
samba_portmapper --> off
samba_run_unconfined --> off
samba_share_fusefs --> off
samba_share_nfs --> off
sanlock_use_samba --> off
use_samba_home_dirs --> off
virt_use_samba --> off
and :
drwxr-xr-x. root root system_u
bject_r:samba_share_t:s0 /shared/