Cisco PIX and ISA 2004

[Eniigma]

Hopefully someone can help me out here with a bit of direction on this problem of mine.

I recently installed ISA 2004 on our network. Before this out network consisted of a Cisco PIX with an outside IP in the public range and the inside interface on the same range as our network. My server had one active network card.

Pix Outside Public
Pix Inside 192.168.30.x
SBS Server 192.168.30.x

Now I have ISA installed and 2 active network cards on my server. The inside interface of the PIX and the outside interface of the server are on the same private range, but different to my internal network.

Pix Outside Public
Pix Inside 192.168.40.x
SBS Outside 192.168.40.x
SBS Inside 192.168.30.x
Internal Network 192.168.30.x

As it is set now it my network is working and users are able to browse the internet as needed. The only problem I have is when I establish a VPN connection to the PIX, I am unable to browse the network or use remote desktop or access email. These worked before the change.
I can VPN to the PIX and then ping the outside IP of the server and I can use remote desktop with the outside IP of the server.

For now I have opened everything on the ISA so I don't really think the problem is a rule issue.

First prize would be to know what the problem is and how to fix it. What I can't figure out is if it a problem with routing on the pix or if the problem is with ISA.

 

[Amida]

You need to add a route on the PIX to direct all traffic destined for the 192.168.30.0 via the Outside IP address of the ISA server.

Also make sure the port forwarding on the PIX firewall is pointing to the ISA server's external NIC IP address.

 

[Eniigma]

Thanks for the response. That's kind of what I suspected.

My pix knowledge is near non exisitant, so I will have to play around with it slowly to see if I can get it working. At least now I have a better idea of where the problem is.

 

[Eniigma]

So I am still fighting with this.

Based on 192.168.30.x being my internal network and 192.168.40.251 being the outside ip of my server

I have added the following route on the pix

route inside 192.169.30.0 255.255.255.0 192.168.40.251 1

with out any luck

Is this right? Should it be the inside interface I am routing?

This is now the response of the show route
sh route
outside 0.0.0.0 0.0.0.0 196.21x.xxx.xxx 1 OTHER static
inside 192.168.40.0 255.255.255.0 192.168.40.250 1 CONNECT static **
inside 192.169.30.0 255.255.255.0 192.168.40.251 1 OTHER static
outside 196.21x.xxx.xxy 255.255.255.248 196.21x.xxx.xxz 1 CONNECT static

** This is the original route that was on before I changed my IP's. I'm not sure how this is effecting things.

I am also confused over another issue... the VPN setup of the pix assigns an IP in the 192.168.255.x range.

 

[Eniigma]

Problem sorted.

Stupid DFU had made a typo in the IP range...

Thanks Amida for the direction. It helped a lot.