• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4939
  • Last Modified:

Juniper Close - TCP RST http traffic

Hi All,

I am trying to pass http traffic through a ssg320 using a mapped IP and a policy that allows http traffic.  Unfortunately the web site is not working and the error is connection is reset.  In my logs I get the following.  There are a couple of other web sites that work using this policy.  Any idea why i am getting these errors?





Date       Time       Duration Source IP        Port Destination IP   Port Service  SessionID In Interface
Reason                Protocol Xlated Src IP    Port Xlated Dst IP    Port ID       PID       Out Interface
2011-12-12 07:51:48    0:00:41  50067 xxx.xxx.xxx.69     80 HTTP        63720    ethernet0/2
Close - TCP RST               6  50067      80                58    ethernet0/0

2011-12-12 07:51:46    0:00:39  49941 xxx.xxxx.xxx.69     80 HTTP        63342    ethernet0/2
Close - TCP RST               6  49941      80                58    ethernet0/0
1 Solution
its a MIP or a VIP, for the VIP theirs an option called "server check" that sometimes cause this caind of errors, can you post a SS of how its the NAT done and how the FW policy its created (obviously covering IP´s)

Regards nef
Hi Jason,

you're using a MIP since i don't see any port translation, hence the "server check" mentioned above does not apply

Since the log is from the policy, the firewall is obviously permitting it.
It's unlikely the firewall would send tcp resets for traffic it is allowing, so it has to come from the webserver.

if you have verified the webserver is accessible locally (from a host on the 192.168.1.x network) then perhaps a "snoop" will help see what's happening..

if you are familiar with telnet, could you open a telnet session to the firewall and do the following once you have logged in:  (assuming you can test with the same external ip address you tested from before..

snoop filter delete     -> may give an error no filters are applied
snoop filter ip
y      <- confirming you want to turn on snoop.

then do another test....
after the test press <escape>  in the console (to turn off snoop , or snoop off

then get the info by typing "get db stream" ...

That output is like a "tcp dump" output...

you should be able to tell if the firewall is forwarding traffic to the webserver, and if it is the webserver sending the tcp resets or not.
If the webserver is sending the resets, it's probably not configured to listen on that port or ip address...

If it is not the webserver sending the resets, we'l have to take it from there....  this output will get us on the right track and plenty people here can assist understanding the output if it's not clear.

I guess i'll read you later :)

a snoop or a flow-filter will explain whats happening with the traffic and why the web server connection is not working
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now