jnbSA error: 526 unable to login
Hello,
we have upgraded from 7.5.0.6 to 7.6.1, also the jnbSA on remote site. The old one was installed on a 32bit Citrix environment and was working properly. The new jnbSA is installed on a different host (64bit) which is on a different network segment. So we guess the root cause for this issue is a firewall problem. Unfortunately we are only man in the middle and the Citrix team as well as the security team is unable to determin the root cause of the problem. How can we help them to get the things right?
Some facts:
Old Citrix host:
C:\>nslookup i68448v1.sbb.ch
Server: vaizk160.dyc-adminlan.ch
Address: 53.250.16.141
Non-authoritative answer:
Name: i68448v1.sbb.ch
Address: 172.28.128.21
C:\>ping i68448v1.sbb.ch
Pinging i68448v1.sbb.ch [172.28.32.159] with 32 bytes of data:
Reply from 172.28.32.159: bytes=32 time=5ms TTL=249
Reply from 172.28.32.159: bytes=32 time=4ms TTL=249
Ping statistics for 172.28.32.159:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 5ms, Average = 4ms
Control-C
^C
C:\>tracert i68448v1.sbb.ch
Tracing route to i68448v1.sbb.ch [172.28.32.159]
over a maximum of 30 hops:
1 1 ms 3 ms 3 ms 53.250.16.132
2 1 ms 1 ms 1 ms 53.250.16.11
3 2 ms 2 ms 2 ms uaila30vl055.t-systems.ch [53.250.112.194]
4 3 ms 2 ms 3 ms sraizk1000vl30.t-systems.ch [53.250.18.6]
5 24 ms 4 ms 4 ms sraila1001vl0100.t-systems.ch [53.250.100.3]
6 5 ms 4 ms 4 ms fvbbrz0010vl0830.t-systems.ch [53.250.17.24]
7 9 ms 11 ms 11 ms i68448v1.sbb.ch [172.28.32.159]
Trace complete.
New Citrix host:
C:\Windows\System32>nslookup i68448v1.sbb.ch
Server: vaizk160.dyc-adminlan.ch
Address: 53.250.16.141
Non-authoritative answer:
Name: i68448v1.sbb.ch
Address: 172.28.128.21
C:\Windows\System32>ping i68448v1.sbb.ch
Pinging i68448v1.sbb.ch [172.28.32.159] with 32 bytes of data:
Reply from 172.28.32.159: bytes=32 time=1ms TTL=251
Reply from 172.28.32.159: bytes=32 time=1ms TTL=251
Ping statistics for 172.28.32.159:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
Control-C
^C
C:\Windows\System32>tracert i68448v1.sbb.ch
Tracing route to i68448v1.sbb.ch [172.28.32.159]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 53.250.16.169
2 1 ms 1 ms 1 ms sraizk1000vl30.t-systems.ch [53.250.18.6]
3 2 ms 2 ms 1 ms sraizk1001vl0100.t-systems.ch [53.250.100.5]
4 1 ms 1 ms 1 ms fvbbrz0010vl0830.t-systems.ch [53.250.17.24]
5 1 ms 1 ms 1 ms i68448v1.sbb.ch [172.28.32.159]
Trace complete.
PBX log:
12:41:54[0]root@i68448:log/VRTSpbx# /usr/openv/netbackup/bin/vxlogview -p 50936 -o 103 -t 00:00:05
05/26/15 12:43:04.625 [Info] PBX_Manager:: handle_input with fd = 8
05/26/15 12:43:04.625 [Info] PBX_Client_Proxy::handle_input read returned: EWOULDBLOCK
05/26/15 12:43:04.802 [Info] PBX_Client_Proxy::parse_line, line = ack=1 From 195.141.158.126
05/26/15 12:43:04.802 [Info] PBX_Client_Proxy::parse_line, line = extension=vnetd From 195.141.158.126
05/26/15 12:43:04.802 [Info] hand_off looking for proxy for = vnetd
05/26/15 12:43:04.802 [Info] is_accepting about to return true
05/26/15 12:43:04.802 [Info] Client Expects an ACK, sent one.
05/26/15 12:43:04.802 [Info] Proxy found.
05/26/15 12:43:04.802 [Info] PBX_Client_Proxy::handle_close
05/26/15 12:43:05.438 [Info] PBX_Manager:: handle_input with fd = 8
Telnet i68448v1.sbb.ch 1556 is going through on both systems. Locally started jnbSA is working fine.
We appreciate any ideas!
Thanks, Matthias