That doesn't help, though, because the system names remain POLAR and GRIZZLY, so there isn't a way to get the new TCPIP machines to read the POLAR2 and GRIZZLY2 profiles, other than naming the virtual machines that way. What I really wanted to do was to run the same virtual machine (TCPIP2) on both systems, just as we run the primary TCPIP virtual machine on both.
-- Robert P. Nix Mayo Foundation .~. RO-OE-5-55 200 First Street SW /V\ 507-284-0844 Rochester, MN 55905 /( )\ ----- ^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 11/20/08 1:54 PM, "Rich Greenberg" <[EMAIL PROTECTED]> wrote: > On: Thu, Nov 20, 2008 at 01:02:20PM -0600,RPN01 Wrote: > > } I set up a second TCPIP virtual machine on POLAR (TCPIP2), and created a > } TCPIP2 TCPIP file for its profile. I was able to bring this up and use it. > } The problem comes if I want to run the TCPIP2 virtual machine on both CECs. > } The two TCPIP machines are controlled by the POLAR and GRIZZLY TCPIP files, > } but is there a way to identify two profiles for the TCPIP2 virtual machines? > } Or, must I call the virtual machine TCPIP3 on the GRIZZLY system in order to > } run both at the same time? > > Perhaps name them POLAR2 & GRIZZLY2?
