I have our lotus sametime (instant messaging) server in the dmz and works from inside and outside as it should. We had a site to site vpn connection with hgnwse and Maltex on our pix, and I moved to the ASA yesterday successfully, well almost. Those two locations can no longer see the sametime server in the dmz. Everything on inside to those locations is working fine (AS400, lotus notes, etc) They could see the dmz while the tunnel was connected to pix, so Im sure its something small im missing. Here is a current config with several items Ive configured but not implemented. The only item that is actually in dmz is sametime server. I have to get issues like this one resolved before moving the more critical servers into it.
from a pc in maltex that Im vnc'd to, I cant ping the 10.2.253.252 (sametime server) or even the 10.2.30.13 (inside interface of asa) I can ping most anything that is on the inside network I think its either an access issue or routing issue.
any help is appreciated
I have tried adding the below, and still getting same results
access-list nonat-dmz permit ip 10.2.253.0 255.255.255.0 10.2.23.0 255.255.255.0
access-list nonat-dmz permit ip 10.2.253.0 255.255.255.0 Hgnwhse 255.255.255.0
access-list nonat-dmz permit ip 10.2.253.0 255.255.255.0 Maltex 255.255.255.0
nat (DMZ) 0 access-list nonat-dmz
After applying above, all should be fine. Try reloading ASA.
Also please attach the latest config.
You have the following route
route inside 10.0.0.0 255.0.0.0 10.2.0.2 1
That route makes the traffic to 10.244.12.0 Maltex and to 10.249.48.0 Hgnwhse be routed to inside instead to your default route outside. Make the following change, then try again.
no route inside 10.0.0.0 255.0.0.0 10.2.0.2 1
route inside 10.0.0.0 255.0.0.0 10.2.0.2 200
If no luck, post the output of