I have a 501 with an AD server connected to ethernet1 (AD server address is 192.168.100.1.) and a client computer connected to ethernet0 (client computer 192.168.11.108). The client successfully sends two UDP packets to my AD server and the AD server replies to my client. My client computer then tries a LDAP connection to authenticate to my AD server.
I have a 501 with an AD server connected to ethernet1 (AD server address is 192.168.100.1.) and a client computer connected to ethernet0 (client computer 192.168.11.108). The client successfully sends two UDP packets to my AD server and the AD server replies to my client. My client computer then tries a LDAP connection to authenticate to my AD server.
This is where the problem starts. The IP address the client is using for the LDAP connection is 192.168.100.1 (remember that the client is on the 192.168.11.x subnet!). I end up getting “No Translation group found” errors in my syslog because the PIX does not know how to translate 192.168.100.1 on the outside interface.
I though maybe I need a static route command so I added:
route inside 0.0.0.0 0.0.0.0 192.168.100.2 1 (where 192.168.100.2 is a wan router on our lab network)
This command did not fix the problem.
How do I tell the PIX that when it gets a packet for 192.168.100.1 on the outside interface (which again is the 192.168.11.x subnet) to route it to the inside interface and on to our wan router so that the AD server gets the LDAP request?
I have a 501 with an AD server connected to ethernet1 (AD server address is 192.168.100.1.) and a client computer connected to ethernet0 (client computer 192.168.11.108). The client successfully sends two UDP packets to my AD server and the AD server replies to my client. My client computer then tries a LDAP connection to authenticate to my AD server.
This is where the problem starts. The IP address the client is using for the LDAP connection is 192.168.100.1 (remember that the client is on the 192.168.11.x subnet!). I end up getting “No Translation group found” errors in my syslog because the PIX does not know how to translate 192.168.100.1 on the outside interface.
I though maybe I need a static route command so I added:
route inside 0.0.0.0 0.0.0.0 192.168.100.2 1 (where 192.168.100.2 is a wan router on our lab network)
This command did not fix the problem.
How do I tell the PIX that when it gets a packet for 192.168.100.1 on the outside interface (which again is the 192.168.11.x subnet) to route it to the inside interface and on to our wan router so that the AD server gets the LDAP request?