hi Bill_Fleury,
thx for your reply.
First my answer to your question .
Yes , ISA server is one of my virtual Machines!
--------------------------
Next week i will go to school for some maintenance.
And try to change my settings and will look if things works.
to be continued.
greatings,
Jos
Main Topics
Browse All Topics





by: Bill_FleuryPosted on 2007-09-11 at 16:10:30ID: 19872848
1) Correct me if I read this wrong, but you are running the ISA server inside of a VM, correct? If this is the case, then why are the PC's getting 192.168.0.2 for a gateway? Your VM should have networking configured in bridge mode, the ISA server should have both an IP on the 192.168.0.0 network and the 192.168.1.0 network, on the virtual interfaces that correspond with each of the physical network cards. Then, if your ISA is configured to perform NAT (or transparent proxying), you should be able to give your workstations a gateway of the ISA server vm's 192.168.0.0 address.
Here is an example of how you would set it up:
DC - Physical machine
LAN - IP- 192.168.0.2
Subnet Mask: 255.255.255.0
Gateway: Nothing
WAN - IP - 192.168.1.3
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.99
ISA Server - VM
LAN - IP - 192.168.0.3
Subnet Mask: 255.255.255.0
GW: Nothing
WAN - IP - 192.168.1.4
Subnet Mask: 255.255.255.0
GW: Nothing
Member Server - VM
LAN - IP - 192.168.0.4
Subnet Mask: 255.255.255.0
GW: 192.168.0.3
WAN - disabled.
Workstations - Physical Student Stations
LAN - IP - 192.168.0.X
Subnet Mask: 255.255.255.0
GW: 192.168.0.3
***Further research may reveal that you can disable the WAN connection on the physical DC, but I am not sure how this will affect the virtual interface, so you can play with that after things are working***
Now, as long as you have transparent proxying set up properly to NAT the workstations through to the outside world, they should be able to get out fine. Also, you should have all machines in the domain's DNS configuration set to use the NS for your local Active Directory domain, otherwise you will experience slow login times and lookup errors, and errors for basically everything else that uses Active Directory as it is heavily DNS dependant.
Now, onto your other question.
2) Enabling RRAS should be fairly easy using the Routing and Remote Access Configuration Wizard. This comes up by default when you enable RRAS for the first time. Be sure to select your WAN connection as the connection to the internet. One thing to note before we go further: You must ensure that the network you are connecting to the VPN from (ie: your home network) does not use any of the network ranges you have listed above. This includes:
192.168.0.x
192.168.1.x
10.0.0.x
If your addressing on your home network falls into one of these ranges, you will have definate routing problems when you connect to the VPN and thus fail to communicate through the tunnel. For more information on that topic, please see:
http:Q_21750753.html
If you have followed the wizard properly and it still stops you from communicating with 192.168.1.99, please do a "route print" while RRAS is enabled and we will try to determine the problem.
I hope this helps clear up a few things for you, please let me know how you make out and if you need further help.