G
Guest
My remote desktop sessions are failing due a communications failure. I see
the remote server i am attempting to connect to sending a "reset" after the
initial handshake. I see it all of the time with the same packet size of
"412". My situation is that i have the server behind a Netscreen Firewall on
the "TRUSTED (192.168.221.97)" interface, the server IP is 192.168.221.100
when the connection comes in from the internet on the "OUTSIDE" interface it
is NAT'd to the "TRUST" interface and the server receives the connection
attempt. Due to security constraints on my project i have to return the
traffic via a different interface "TRUST2 (192.168.221.99)" to the internet.
This is why i think my connection fails. Here is the kicker, if i connect a
laptop to the "OUTSIDE" interface and attempt to connect to the server my
connection is successful.
Is there a way to get around this situation? I have a diagram that depicts
all of this and all of the packet captures but i do not know if I should and
where to past them.
This has stumped the Netscreen engineers, the Cisco engineers and myself for
2 months now.
Thanks,
Manuel
the remote server i am attempting to connect to sending a "reset" after the
initial handshake. I see it all of the time with the same packet size of
"412". My situation is that i have the server behind a Netscreen Firewall on
the "TRUSTED (192.168.221.97)" interface, the server IP is 192.168.221.100
when the connection comes in from the internet on the "OUTSIDE" interface it
is NAT'd to the "TRUST" interface and the server receives the connection
attempt. Due to security constraints on my project i have to return the
traffic via a different interface "TRUST2 (192.168.221.99)" to the internet.
This is why i think my connection fails. Here is the kicker, if i connect a
laptop to the "OUTSIDE" interface and attempt to connect to the server my
connection is successful.
Is there a way to get around this situation? I have a diagram that depicts
all of this and all of the packet captures but i do not know if I should and
where to past them.
This has stumped the Netscreen engineers, the Cisco engineers and myself for
2 months now.
Thanks,
Manuel