CS1000E, IP sets can't registered to the Node IP behined the NAT

[ROTA78]

Dear All,
thank you for this web site and ur always support realy it is very usefull for me.

The problem:
------------
We have CS1000E Rls 5.5 new installation we update the deplist also.

ip range as follow
T-lan:
------
Node IP : 192.168.4.100
ss : 192.168.4.35
MGC1 IP : 192.168.4.32
MGC1-DB IP: 192.168.4.34
MGC2 IP : 192.168.4.36
MGC2-DB IP: 192.168.4.43

E-LAN:
------
CS IP : 192.168.3.30
ss IP : 192.168.3.35
MGC1 IP : 192.168.3.32
MGC1-DB IP: 192.168.3.34
MGC2 IP : 192.168.3.36
MGC2-DB IP: 192.168.3.43

Now while I tried to register from the network 192.168.4.0
I got local mode on the IP set screen.

We have configuring NAT on the router as follow real IP (as global IP) to the node IP 192.168.4.100

I can ping to the global real IP from the internet
I can connect to the EM as well.

The proble is while login to the Node ip from the internet
using IP set I got the following error from the SS

05/08/2009 16:07:32 LOG0003 TPS: tpsRemoteMsgDispatch: TPSAR tsak is not up and
runing. Check config.ini file. Send the AR_TIME_OUT back to 0x30d020cc
05/08/2009 16:07:38 LOG0004 CSV: ITS4011 196.205.155.124 connecting to node 1, T
N: 096-00-01-00, 0x6004 [Soft Reset: RUDP retry exhausted, code: 2] (201)
05/08/2009 16:07:50 LOG0004 CSV: ITS4011 196.205.155.124 connecting to node 1, T
N: 096-00-01-00, 0x6004 [Soft Reset: RUDP retry exhausted, code: 2] (201)

05/08/2009 18:02:47 LOG0003 TPS: tpsRemoteMsgDispatch: TPSAR tsak is not up and
runing. Check config.ini file. Send the AR_TIME_OUT back to 0x30d020cc
05/08/2009 18:02:48 LOG0004 CSV: ITS4011 196.205.155.124 connecting to node 1, T
N: 096-00-01-00, 0x6004 [Soft Reset: RUDP retry exhausted, code: 2] (201)
05/08/2009 18:03:06 LOG0004 CSV: ITS4011 196.205.155.124 connecting to node 1, T
N: 096-00-01-00, 0x6004 [Soft Reset: RUDP retry exhausted, code: 2] (201)


And the set screen show forwarding and reseting and intered in loops.

so any one have any ideas


Thanks

Rafat

 

[johnpoole]

what ip are you assigning to the set?.. you can't dhcp, that requires the same broadcast domain as the dhcp server.. you can't assign a 192.168.x.x and expect that to get routed..

john poole
bellsouth business
columbia,sc

 

[ROTA78]

Dear john,

We assign a real IP to the set... from anther domain in the internet...

regards,
Rafat

 

[FaridMcs]

No