Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 2 subscribers
  • Views 5735 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Drop RDP connection

Aresh
Hi,

I have a very strang issue,
I have a DNAT that must allow access to the RDP to a server behind the UTM just from  some location. I did create a group and add the allowed IP address to the list and it work as it should.just one customer cannot access I did add their IP to the list but when try to log they get this: 

2015:09:09-09:26:58 securitysrv1-1 ulogd[30899]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop" fwrule="60001" initf="eth1" srcmac="54:e0:32:06:76:9a" dstmac="00:1a:8c:f0:0f:a1" srcip="95.XX.XX.84" dstip="62.XX.199.XX" proto="6" length="52" tos="0x00" prec="0x00" ttl="113" srcport="55735" dstport="3389" tcpflags="SYN" 

2015:09:09-09:27:01 securitysrv1-1 ulogd[30899]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" 



Why is that? I did add the same IP to the list why UTM drop the connection?

Thanks


This thread was automatically locked due to age.
Parents
  • 0
    Hi Bob

    Version of the utm is 9.313,3 
    I dont know what is going on here but i did remove the problematic network from the dnat rule and as you said re-added it back and save the rule again now i can see the problematic customer can access
    I will keep en eye on this and report back
    Thanks for the tip
Reply
  • 0
    Hi Bob

    Version of the utm is 9.313,3 
    I dont know what is going on here but i did remove the problematic network from the dnat rule and as you said re-added it back and save the rule again now i can see the problematic customer can access
    I will keep en eye on this and report back
    Thanks for the tip
Children
No Data