timeout

i'm using redhat 7, and ipchains for the firewall,
i open all connection to outside
and allow all connection from other network(202.???.???.???) to inside (192.168.12.0/24)

INPUT         - ACCEPT
OUTPUT        - ACCEPT
FORWARD       - MASQ
From inside(192.168.12.0/24) to outside allow all
From other public 202.???.???.0/24 to inside allow all

all the connection is ok, but i always got problem with
mapping,
if i map a drive to other network (202.???.???.???) from the inside network (192.168.12.0/24) after sometime it will give a timeout, but then if you click again on the drive... it will be ok again...

i don't why this happen (the timeout)... can i set no timeout.. so the mapped drive will always connected?

thanks
LVL 1
ichenAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

j2Commented:
Your default policy for forwarding is MASQ. You cannot masquerade SMB traffic without getting the error you mention. You must create rules which opens (atleast) port 135-139 between the two nets WITHOUT masquerading (which most likely will break something else) But that is the breaks :)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ichenAuthor Commented:
create rules which opens port 135-139 without masquerading??
what do you mean by that?
ipchains -A forward -s 192?????? -d 203?????? 135:139 (without -j MASQ? is it??)
j2Commented:
-A forward -s 192.168??? -d 203??? -p TCP --destination-port 135:139 -j ACCEPT and that has to come before the masquerade for the same network. And since you are using "dark" IP's (the 192.168 net) this probably will not wor, but it is the only way to get a reliable SMB connection. You also of cource need bidirectional routing between the networks.
j2Commented:
oh, you need to add -b (bidirectional) to that rule aswell.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.