Re: remoting over router/NAT
- From: mihaidu@xxxxxxxxx
- Date: 20 Jan 2007 06:28:47 -0800
In this case, remoting is running one-way (client to server) so you should
not have any NAT issues. The default configuration should work.
You only need to specify the server port - there is no need to specify any
client ports.
I currently have a couple application running in a NAT environment (even
NAT to NAT) and it works fine.
P.S. If you telnet directly to the application, can you connect? If not -
could be a firewall issue.
I disabled any firewalls temporarly just to be sure that isn't the
problem, it still doesn't work.
port to communicate. As the server sends data to the client (eg. returnFrom the TCP point of view, it is clear that the client also uses a
values of functions, etc.) there are some TCP packets going from the
server to the client. As the NAT is the only thing between the two, i
suspected that the problem lies there. BUT I'm not sure and I'm also
not very good at interpreting my tcp dumps. Where else could the
problem be? NAT configuration? Do I need trigger ports?
Mihai
.
- Follow-Ups:
- Re: remoting over router/NAT
- From: Spam Catcher
- Re: remoting over router/NAT
- References:
- remoting over router/NAT
- From: mihaidu
- Re: remoting over router/NAT
- From: Spam Catcher
- Re: remoting over router/NAT
- From: mihaidu
- Re: remoting over router/NAT
- From: Spam Catcher
- remoting over router/NAT
- Prev by Date: Re: remoting over router/NAT
- Next by Date: Re: remoting over router/NAT
- Previous by thread: Re: remoting over router/NAT
- Next by thread: Re: remoting over router/NAT
- Index(es):
Relevant Pages
|