Windows 2000 in VM Under Win 7??

[zzz2496]

OK, first...

Read this guide, it will allow your Win7 to route traffic between subnets

Once done, well... you know, make routes, check connections, etc...
If you can enable routing capability in Windows 7, you'll be able to connect to domain without any problem, install VAX driver in the 2K, and all...
Since the 2K is effectively on a "real" network, it should work

zzz2496

Ps. Try to ask a vacant IP address to your IT guy, it'll save a lot of your time

 

[Jeffs]

I'm really confused by this article you pointed me to. 1) It's an XP article. 2) it talks about a computer with 3 network cards being the router. I don't see how this relates to this application.

Need further clarification.

The 192.168.10.x IP address is out of the question.

 

[zzz2496]

Let me check something first...

zzz2496

 

[zzz2496]

Grrrr... I'm stuck... crap...

Jeffs, how many memory do you have on your work machine?

zzz2496

 

[Jeffs]

The host has 4gb, of which 3 are used (32bit OS)

 

[zzz2496]

Here's our "position":

The VM is 90% up and running. Right now, you can connect to your VM via .0.x IP, and everything is good, but you need your VM to be able to access your .10.x IP.

Here are my ideas:

1. Make your Windows 7 acting as a router between you and your network(s) (.0.x, .10.x, .25.x, and .26.x). But I'm bumping to a dead end, I can't even configure my own virtual machine to do that (using a bonded interface = one NIC, multiple IP addresses). I'm still trying to solve this issue, which led me to the second idea...
2. Since you have some memory to spare, I'm suggesting you to make a new virtual machine, and create a virtualized router on it, that way we don't need to change Windows 7's configuration but in expense of several hundred MB of memory to be used by the Virtualized router.

Tell me your ideas...

zzz2496

 

[Jeffs]

At this point I'm totally confused.

At this point I would like to:

a) Get the video resolved. Let's get this display to show 16 or 24 bit color at greater than 800 x 600.
b) Why did installing the VBOX additions screw everything up before?

After resolving that, let's say I could do without the virtual network, and just be able to share the host drive C: and visa/versa (have the Host share the drive C: of the VM). I wasn't able to get the shared folders to work, but then I only "touched" on it and might not have known what to expect.

 

[zzz2496]

OK, solve the display problem first then...
Make a backup of the .vmdk (Shutdown the VM, no doing snapshots or anything), copy the backup to a safe place, then install additions.
Let's see if it BSOD or not... I even installed Windows 2000 on my VirtualBox just to know what's wrong... and mine is running perfectly...

zzz2496

 

[Jeffs]

I'm essentially "backed up" from before.

Remember your W2K is a clean install. Not a 10 year old polluted one like mine.

 

[zzz2496]

Good point... urgh...

Edit: Can you "clean" it up a bit, uninstall useless things/programs/protocols/whatever (like the DEC/VAX thingie), make it as "plain" as possible before installing the Additions...

zzz2496

 

[Jeffs]

OK. I installed the Vbox Additions. When prompted for the display driver, I installed it. When prompted for the Mouse driver, I declined - since I think that was the source of the blue screen. I suppose I can try the mouse again later, after I save the pc115 file again.

I have the display running at 1152x864 32bit color. Video issue solved.

Now, shared folders. This isn't going to work without network support, is it?

 

[zzz2496]

(Please excuse me for a moment)
My god, Seeing Windows 2000 logging in, hearing the piano intro... God... what a memory... I'm feeling all warm and fuzzy inside...
(/Please excuse me for a moment)

I see, good, display driver is up and running, now, can you make the network to "Bridged" again?
Once you done that, put it in the .0.x network. Ping your Windows 7 host, report when you have pongs.

zzz2496

 

[Jeffs]

The network still is bridged, and is set to 192.168.2.1/255.255.0.0

When pinging the host at 192.168.10.224, I get no reply (request timed out).

When pinging an XP box sitting next to my desk at 192.168.10.54, it responds.

OK, now I'm confused. Nothing else I tried on 10.x responds.

When pining some of my industrial equipment on 25.x and 26.x, they respond.

That's all for today, time to head home. I just noticed you're in Indonesia. What time/day is it there now? It's Wednesday 16:50/4:50pm here.

Thanks for the help today. More tomorrow morning. I'm going to make a copy of the virtual machine file before I head out since it's in a "nice state" right now.

 

[zzz2496]

You and I are 12 hours apart (5AM over here)

It's bridged, good...
Tomorrow, put it into 192.168.0.x/24 please, wreaking havoc with IP addressing is the last thing you want to do.
Use a Class C with 24 bit subnet mask, and we'll figure out how to route the request to your other devices.

zzz2496

Edit: From my perspective, I would never even try to connect 2 different subnet together. I see that you put 192.168.2.1/16 and try pinging other network addresses... My god... no wonder we're in this whole mess (sorry...)... The way I was taught in my Cisco labs was: "Connect only to your network, only to peers with the same network address as you". My teacher's example was "If you're living in Block 'A' and have a house number of "1", ask your new neighbor who doesn't know the neighborhood to send a package to your sister's house in Block "AZ" house number "166"?". The package might make it, it might not... it depends on your "stupid" neighbor. This is like Windows, we don't know how Windows will react if we "force" it to communicate with a network peer that is not on the same network address as it. Sometimes it successfully communicate, sometimes it's not... so to avoid any unpredictability of Windows's TCP/IP stack, we should use the proper way of IP addressing... What I mean is, if your Windows 7 is 192.168.0.1/24, put your Windows 2000 in 192.168.0.2/24, NOT 192.168.0.2/16, it will do weird things, I promise you that...

 

[Jeffs]

Yes, yes... I know the implications and understand what you're saying. It was an experiment. I don't think it's the problem though, but we'll attack that tomorrow.

Just give me the correct subnet number for /24 = 255.255.?.0 and /16 so I'm ready to go tomorrow.

 

[zzz2496]

/8 = 255.0.0.0
/16 = 255.255.0.0
/24 = 255.255.255.0

Edit: sorry if I sound like a douche, it's 5 AM... sorry...

zzz2496

 

[Jeffs]

Morning again. I've got to do something else for an hour or so before I get back to the VM. I'll be back.

 

[jimbo45]

Hi there
Lunch time here -- just come back from "The Pub".

First thing to do is ensure your Network allows incoming connections on ALL machines (Firewall / Router).

Now from the VM try pinging first the Router -- usually address 192.168.x.1 or 10.10.x.1

If that's Ok now ping another machine on the network.

If that's Ok now from any machine on your network ping the VM.

Ensure File and Printer sharing set up / enabled --you can use the Network wizard on the W2K machine.

Ensure also that the Workgroup name is the same for all machines on the newtork and you have the same user id / password on the W2K machine as the other machine(s).

Then either NAT or BRIDGED should work.
I've never had a problem with VM networking -- even got a W95 machine running for demo.

Cheers
jimbo

 

[zzz2496]

Hi there
Lunch time here -- just come back from "The Pub".

First thing to do is ensure your Network allows incoming connections on ALL machines (Firewall / Router).

Now from the VM try pinging first the Router -- usually address 192.168.x.1 or 10.10.x.1

If that's Ok now ping another machine on the network.

If that's Ok now from any machine on your network ping the VM.

Ensure File and Printer sharing set up / enabled --you can use the Network wizard on the W2K machine.

Ensure also that the Workgroup name is the same for all machines on the newtork and you have the same user id / password on the W2K machine as the other machine(s).

Then either NAT or BRIDGED should work.
I've never had a problem with VM networking -- even got a W95 machine running for demo.

Cheers
jimbo

He doesn't have a "router" per say...
He's now out of IP addresses to use, and I'm stuck on how to add this new node to the network... I was suggesting a "Router VM" to route his Win2K VM so that it can connect to the "real" network...

zzz2496

 

[Jeffs]

OK, I'm back.

The router is at 192.168.10.41, however the VM can not be 192.168.10.x because of address shortage.

That's why I want the VM to NAT through the host, which is at 10.244, and can reach the router.

When I select NAT, there is no networking, the address assigned is 0.0.0.0/0.0.0.0. When I use bridged, with a static IP, it works fine. So that's where it's at, trying to get NAT working.