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

ASA 5505 with ASDM

Hi Experts,

I have a computer in DMZ interface that needs to join domain where is in inside.
All necessary ports are open.
When I try, I got the following error

"Deny TCP(no connection) from x.x.x.x /58923 to y.y.y.y/139  flags RST on interface DMZ"

I googled it and found below solution

"check your config for 'sysopt connection timewait'. If not, try adding it. Some software wants to do a two-way hangup at the end of a connection, and this option keeps connections open until both sides ack the closing."

Is this right one? If so, i just type 'sysopt connection timewait' in command line interface, right? or something else needs to be done.

This issue need to be resolved pretty sooon. Please help!!!!

Thanks in advance..
0
Ksean
Asked:
Ksean
  • 2
  • 2
1 Solution
 
pclinuxguruCommented:
can you ping your domain controller from the computer in the DMZ and can you ping the computer from the domain controller?

Reason I ask is generally stuff in the DMZ can't talk to stuff on the inside. That is what makes it a dmz. You can make it do it if you really want to... requires some configuration though and then it is pointless having the dmz.
0
 
KseanAuthor Commented:
I don't want any ping either direction because I didn't open ports for ICMP. All I need is to join domain. Any idea?
0
 
pclinuxguruCommented:
Well you need to test traffic from the dmz to the inside. Without ping I am not sure how you would do that.

DMZ traffic is blocked from inside traffic and vice vera.

If you want to simply join it to the domain then plug your cable to a switch on the inside interface and join it. Then move it back.
0
 
KseanAuthor Commented:
good job
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

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