>
>
> "dunieres" <(email address - cut out)am> wrote in message
> news:(email address - cut out)...
>> Hello,
>>
>> I have a 2008 Standard Edition Server with Hyper-V. I run 4 2008 VM. The
>> host server has 2 1Gb lan cards. One is for the VM and the other for the
>> host. I use NAT for the VM with the Routing and Remote Access Service
>> configured between the VM lan card and an internal virtual card. It works
>> fine, the VM have Internet connectivity. The problem is that when I start
>> the RRAS, I lose al connectivity to the second lan card. It even does not
>> answer to ping. Nothing is configured in RRAS for the host card. I have
>> also noticed another problem the VM have no access to local computer on
>> the same lan, but it works well for outside computer. Any idea ?
>>
>> Jack TREVES
> There are quite a few problems with running a config like that. The
> simplest solution is to run RRAS in a vm rather than on the host. Put the
> vms on a private virtual network (no connection to the host) and run a vm
> as a RRAS router (I run W2k3 with RRAS using 512M of memory). This gets
> around the problems caused by Server 2008 assigning network profiles to
> the networks which you don't really want. Otherwise you need to fiddle
> with the advanced firewall settings to make it do what you want.
>
>

> Hello,
>
> I have a 2008 Standard Edition Server with Hyper-V. I run 4 2008 VM. The
> host server has 2 1Gb lan cards. One is for the VM and the other for the
> host. I use NAT for the VM with the Routing and Remote Access Service
> configured between the VM lan card and an internal virtual card. It works
> fine, the VM have Internet connectivity. The problem is that when I start
> the RRAS, I lose al connectivity to the second lan card. It even does not
> answer to ping. Nothing is configured in RRAS for the host card. I have
> also noticed another problem the VM have no access to local computer on
> the same lan, but it works well for outside computer. Any idea ?
>
> Jack TREVES

>
>
> "dunieres" <(email address - cut out)am> wrote in message
> news:(email address - cut out)...
>> It is funny to use a 2003 server to do the routing. But how can I connect
>> the second lan card of the RRAS machine to the outside world. I cannot
>> map the virtual adapter to the physical one as the RRAS MAC Address
>> should not appear on the lan. I cannot use ICS as I will have no way to
>> know the IP adress to route. So I think I will have to play with the
>> firewall settings.
>>
>> Thank you,
>> Jack TREVES
>>
>
> You can use a 2008 vm as your router if you like. (Or Linux for that
> matter). I use 2003 because it does the job and runs happily.
>
> How does your host connect to the physical network? If it is on a
> network which uses DHCP the RRAS server can get its network config the
> same way that the host gets its config. My Hyper-V host is on a LAN behind
> a D-Link router.
>
> Why should the RRAS server's MAC address not appear on the LAN? What
> problems would it cause? (Having the 2008 server register two interfaces
> with two MAC addresses (as you do now) is a problem.) If you don't want
> the LAN machines to see the RRAS server, disable Netbios over TCP/IP and
> set it to not register in DNS.
>
>

> It is funny to use a 2003 server to do the routing. But how can I connect
> the second lan card of the RRAS machine to the outside world. I cannot map
> the virtual adapter to the physical one as the RRAS MAC Address should not
> appear on the lan. I cannot use ICS as I will have no way to know the IP
> adress to route. So I think I will have to play with the firewall
> settings.
>
> Thank you,
> Jack TREVES
>

>I know well 2003 so I will use it. I am not sure that 2008 can run well with
>512 Mo memory.
>
>My hosting provider does not like to see unknown MAC on his net and
>deactivate the offending machine.
>

> Isolate your LAN from the ISP by putting a router in between (D-link
> for example). Then let the router be the DHCP server on your LAN. Now
> you can have as many MAC addresses as you like on your network, the
> only one seen by the ISP is the router's MAC address.
>