Author Topic: (vmWare) routing  (Read 1380 times)

iddu

  • Are we there yet?
(vmWare) routing
« on: 07 March, 2011, 02:55:46 pm »
Got a box, with Server 2003 & 2 NIC's (A & B)

It hosts a VMWare "Server 2003/ISA2004" config, with 3 vNIC's (A1, B1 & C1)

A1 & B1 bridged onto vSwitch0, hard mapped to A (Net #1)

C1 bridged onto vSwitch2, hard mapped to B (Net#2)

(ping) Traffic on  A1/B1 transists A to LAN/InterWebz without issue.
(ping) Traffic on C1 doesn't transit correctly.

Net #2 is a 10.0.0.0/24, no gateway
Host NIC "B" is @ 10.0.0.192, connected to 4-port hub
"vISA" C1 is @ 10.0.0.193, vBridged to B
"tin" server is @ 10.0.0.100, connected to (same) 4-port hub

So, ping results are:
-->vISATinHost
vISAOKOKOK
TinFAILOKOK
HostOKOKOK

Anybody know the incantation to get "Tin" to cross the bridge to "vISA"

I'd offer you some moral support - but I have questionable morals.

tiermat

  • According to Jane, I'm a Unisex SpaceAdmin
Re: (vmWare) routing
« Reply #1 on: 07 March, 2011, 02:59:23 pm »
What version of VMWare? IIRc there is a limitation with 3.X whereby you can only one vLAN per physical NIC.
I feel like Captain Kirk, on a brand new planet every day, a little like King Kong on top of the Empire State

iddu

  • Are we there yet?
Re: (vmWare) routing
« Reply #2 on: 07 March, 2011, 04:57:17 pm »
What version of VMWare? IIRc there is a limitation with 3.X whereby you can only one vLAN per physical NIC.
Server 2

Think it's oK, found a numpties guide :thumbsup: OTOH, stop messin' about and use Tin+3 NIC's ::-)


I'd offer you some moral support - but I have questionable morals.