Win95 VM with Win XP host networking (shared folders)

[ghr]

Set up a Win95 VM with Win XP host networking (shared folders)

Overview

I created a Win95 VM for filesharing with my Win XP host. Set up host/guest networking is detailed below.

Details:
- the guest is a Win95 OSR2 (4.00.950B) machine.
- the host is a typical WinXP SP1 machine.
- VirtualBox 1.4.0.

Results

Filesharing between host and guest !

Details:
- guest has read/write access to host files
- host has read/write access to guest files
- host internet access is NOT possible, because the host firewall has to be shut down (at least in my case)

Limitations:
- for security reasons I would not recommend sharing your root drive with anyone.
- host internet access disabled (firewall down)

How to

What do you need (apart from having a basic Win95 VM): some extra information on how to setup a connection between a Win95 machine and a WinXP one. The original info (contributed by Steve Winograd, MS-MVP (Windows Networking)) is here:
http://groups.google.nl/group/microsoft ... d1c?lnk...

It is all repeated below and adapted where needed for VirtualBox.

Configure the Windows 95 network settings manually. Go to Control Panel | Network and:
1. Add these network components if they aren't already present:
- TCP/IP protocol
- Client for Microsoft Networks
- File and Printer Sharing for Microsoft Networks
2. Remove these network components if they're present:
- IPX/SPX protocol
- NetBEUI protocol
- Client for NetWare networks

3. Set the workgroup name to the same name as the Windows XP computer uses (default for XP is MSHOME). If there's a DHCP server on your network (broadband router or a computer configured as an Internet Connection Sharing host), that's all there is to it. The DHCP server will automatically assign TCP/IP properties to Windows 95. For information on ICS, see: Windows XP Internet Connection Sharing http://www.practicallynetworked.com/sharing/xp_ics. Otherwise, you need to assign static IP addresses to all of the computers.

On Windows XP (host):
1. Open the Network Connections folder.
2. Right click the network connection. (for VirtualBox that would be e.g. "VM1 External")
3. Click Properties.
4. Double click "Internet Protocol (TCP/IP).
5. Click "Use the following IP address".
6. Enter IP address 192.168.0.1.
7. Enter subnet mask 255.255.255.0.
On Windows 95 (guest):
1. Go to Control Panel | Network.
2. Double click "TCP/IP->network adapter".
3. Click "Specify an IP address".
4. Enter IP address 192.168.0.2.
5. Enter subnet mask 255.255.255.0.

Host preparations

Before creating the Win95 VM I created a Host Interface (see VirtualBox manual). Using WinXP Network setup I modified TCPIP properties to use the IP address mentioned above: 192.168.0.1 (subnetmask 255 255 255 0).

If you want to share your c:\ drive: allow c:\ to be shared (e.g. as C, and allow users to modify your files as well; this will give read/write access to your c:\ drive (note: not recommended for security reasons).

Be sure to have the same workgroup for both machines - host and guest. In my case I had to disable the firewall.

Client preparations

If you want to share your c:\ drive: allow c:\ to be shared (e.g. as VIRTC)

File sharing

Now you should be able to read from and write to the host.

Some checks:
- on the Win XP host, you can click Start > Search ... > Search for computers to access your guest; or use explorer and type in the addressbar: \\guestname\guestsharename
- on the Win95 guest, use Explorer; the network computers should show up under Network Neighbourhood.
- on the Win95 guest, use Explorer > Extra > Search > Computer....

Performance

Speed in transferring a large file: approaching 10 Mbps, fine.

Limitations / to do

The firewall can be configured differently to avoid its shutdown and still allow networking.

[Paul jones]

I can acces the Guest Win 95 system via shared network folder from the host XP but when \I try to access the host from the guest I am told \\Name is not accessible. Can you help please.

[stefan.becker]

Help yourself, post Infos & exact approach.

[Ramon Zarat]

Hi. I'm an emulator aficionado. I like to emulate for a hobby.

Same issue here. Followed EXACT instruction. IPX and NetBEUI have been removed. TCP/IP protocol, File and printer sharing
and Client for Microsoft Network have been added. I can go on the Internet no problem under the Win95 guess. I've disabled the XP host firewall completely, no change. From the Win95 guest, I can see my router at 192.168.0.1 in Internet explorer.

What I CAN do now is access the Win95 guest share from the XP host, but not the other way around. From XP host, I mapped the shared Win95 folder (C:\SHARE) and it's working fine. This is the things I've tried to access my XP host from Win95 guest and the result:

From the Win95 guest, if I click on "Network Neighborhood", take a good 3-4 minutes with the "flask light" searching, then click "Entire network", so it search again but with the "hourglass" this time for another 3-4 minutes and eventually I get the error: Unable to browse the network. The network is not accessible. For more information, look in the Help Index at the topic "Network Troubleshooter"". I've looked, no help there...

Tried to map a network drive manually (right click network neighborhood) with \\HOST-PC-NAME\SHARE-NAME, didn't work either with the error: "The following error occurred while trying to connect E: to \\HOST-PC-NAME\SHARE-NAME. The computer or share name could not be found. Make sure you typed it correctly, and try again." The XP host PC Name is "PCMAIN" and the share name is "DATA".... Impossible to go wrong... Beside, it work just fine in from XP guest to XP host.

Tried to use the built-in Virtualbox share drive feature with \\vboxsrv\DATA. Same error, but happened much faster. Then I realized it requires guest addition... Still interesting that the error happen instantly instated in 3-4 minutes!

Also tried the "Find computer" option (right click network neighborhood) with the name "PCMAIN". After 5 minutes, it just stop with no error and finds nothing.


NOTE: Sharing from/to XP, VISTA or WIN7 guest to/from XP host is working fine. Only Win95 can't see my network.

NOTE2: Just for fun, I've tried to change my "Workgroup name" in the Win95 guest (Control panel / Networking, Identification tab) to something different than my XP host. Rebooted and now I can see this new Workgroup name AND my guest share under Network neighborhood but still no trace of the XP Workgroup. XP host now see both the XP and Win95 with 2 different names as 2 distinct Workgroup. Strange that when both workgroup have the same name, the Win95 guess network neighborhood don't work anymore.


CONFIGURATION SETUP:

HOST:

Windows XP pro SP3 fully patched
Microsoft security essential
Windows XP Firewall
Peerblock R223 (HTTP allowed)
DFI NForce 2 motherboard with Latest Drivers
Nvidia Nforce 10/100 Networking controller
Athon XP-M 1700+ (1467Mhz) overclocked to 2.6Ghz (200FSB X 13), Prime95 and 3Dmark 2006 24H Stable.
1.5GB RAM Kingston 113332 1T ( 3 X 512MB) Dual channel
GeForce 6800GS AGP 256MB Nnidia drivers V191
WD Raptor 36GB OS/APP Drive
WD Caviar Green 1.5TB for visualization
Antec 550W PSU
Dlink DI-655 router/DHCP server with firmware V1.21

NOTE: This PC successfully interface/share:
Externally on the LAN: 1 win2K3 server, 2 wireless Vista laptop, an Xbox1 running XBMC. Can access IRC channel, POP3, FTP, Usenet and torrent at full speed.
Externally on the WAN: Running a FTP server, a web server.
Internally: VMware V7, Virtual Iron, Citrix Xenserver, Virtual PC, Qemu (All running running XP-Vista- Win7 + some linux) and also PearPC (Mac OSX sharing with SMB protocol with host), WinUAE (OS3.9) and Ballistix on Mac OS 9. Some of these run through a Open VPN TAP virtual NIC.


GUEST:

VirtualBox V3.1.0 R55467
Win95 OSR2 (Build 4.00.950B) fresh and clean install, no patch, no guess addition (not supported yet...)
TCP/IP protocol
File and printer sharing
Client for Microsoft Network
VBE VGA driver V2.0
RAIN CPU HTL V2.0
Bridged PCnet-FAST III (AMD PCNET Ethernet Adapter).


Thanks,

Ramon Zarat

[rauli]

I'm having the same problem (now with VB 4.1.8 ) as the others:
I can't see the physical machine from the virtual Windows 95.
I followed the instructions step by step. DHCP worked, so I skipped the static IP addresses assignment, but I did the rest.

The original document explains how to connect 2 physical machines (one with Windows XP, other with Windows 95) so I think the missing part is the VirtualBox configuration:

Which mode must be used for the NIC in the virtual machine (NAT, Host-Only, bridge...) ?

Anything to configure in the host-only network adapter installed by VirtualBox in Windows XP? (the document tells which components must be present or removed in the Windows 95 network connection, but nothing about the Windows XP network connection)

Note: I'm using the 1st version of Windows 95, not OSR 2.x

[mpack]

The network mode would have to be "Host Only" or "Bridged" - the latter only if there is a router connected which can hand out IP addresses via DHCP.

Then just make sure both computers are part of the same workgroup. I should mention that I've never created a Win95 VM, since I see Win98SE as Win95 with the bugs fixed.

[rauli]

Thanks.

I was already using Windows 95 NIC in host-only mode.

I was using the same workgroup for both systems, but yesterday I tried to change it for a shorter name, and the result was the same: Windows XP can access Windows 95 shared folder, but not the opposite.

I thought "If one can access the other's folders, then the worgroup must be OK" but I also tried configuring a different workgroup name on each system and (surprisingly) Windows XP still can access Windows 95 shared folder (and, of course, not the opposite).

I read the NetBIOS entry in Wikipedia, and it says that "NetBIOS over TCP" in older systems can use TCP port 137 for name service. I don't know if Windows is such an "older system", but I tried to add an exception in XP firewall for this port, and it didn't work. The SMB entry in Wikipedia also mentions TCP port 137.

I don't have any NetBIOS or SMB component on XP or 95 NICs, but Isuppose it's included in the "MS network client", or in the "file/printer sharing". In the XP firewall NetBIOS ports are included in the "file/printer sharing" exception, without TCP 137, that's why I added just this port.

The last thing: When I start Windows 95 it asks me for a username/password to start the session. Does XP need to know that user in order to let him/her access XP shared folders? (I suppose it is the same with Windows 95/98/ME)

[mpack]

I was using the same workgroup for both systems, but yesterday I tried to change it for a shorter name, and the result was the same: Windows XP can access Windows 95 shared folder, but not the opposite.

That was the result I used to get with Win98. I used to assume that was because XP is probably backwards compatible with W98, but W98 is not forward compatible. Fine theory, however I'm pretty sure I recently discovered that my WIn98 VM could see the shared folders on my host. I would need to check that tho - I don't use the Win98 VM for much except the occasional test.

The last thing: When I start Windows 95 it asks me for a username/password to start the session. Does XP need to know that user in order to let him/her access XP shared folders? (I suppose it is the same with Windows 95/98/ME)

If you search online you'll find out reasons why Win9x prompts for username and password on startup, and how to turn it off. I do remember that when trying to get Win98 to access a host share, Win98 wanted to enable full network logon including a password. In the end I put the shared folder on the Win98 side, so the latter could access it locally without a password. My XP host didn't need a password to access a W98 shared folder.

[rauli]

Thanks again.

I disabled the login box appearing at Windows 95 startup.

Most important: After many attempts, my XP host can access my guest 95 shared folders, AND my Windows 95 guest can access my host XP shared folders! At last

What I did: Well, I tried many things, but I think it's enough to:

• Add NetBEUI and IPX/SPX protocols in Windows 95 network configuration, in spite of the howto (1st post of this thread).
• Add NWLink NetBIOS and NWLink IPX...(*) protocols in the VirtualBox Host-Only Network in Windows XP.

I didn't need to disable the Windows Firewall, and I didn't need to add any exception to it.

I'm not doing more tests today, but:

• I suspect that TCP/IP protocol is not needed (could be removed) from Windows 95 network configuration.
• I suspect it could also be removed even from the VirtualBox Host-Only Network in Windows XP, but I would not do it because other VirtualBox machines could need it (any guest connecting to Internet DOES need it).

(*) I can't read full name because Spanish description is very long and it's cut.

[rauli]

I managed to share folders using only TCP/IP protocol (without NetBIOS and IPX/SPX).

I started from a new VM (just after W95 installation), followed ghr's howto and made sure:

• In network connection properties -> Primary Network Logon is set to MS Network client.
• In network connection properties -> TCP/IP protocol -> Properties -> Links: MS Network client and file/printer sharing are (both) checked.
• Windows asks for a username/password at startup, and a username (any) is introduced. No password is needed, even if Windows asks for it in another dialog box.

I'm not sure if this is required, but: In the host system (XP), in network connections -> VirtualBox Host-Only adapter -> TCP/IP protocol -> Properties -> Advanced options -> WINS -> NetBIOS configuration: Enable NetBIOS over TCP/IP (I didn't touch it, I left it as it was).

If you don't want to introduce a username, use the NetBIOS configuration (as in my previous post). With that approach I don't remember the setting I used for Primary Network Logon.

If you don't mind to introduce a username, I would use TCP/IP instead of NetBIOS.

On both cases, leave Windows XP Firewall untouched (running, with no extra exceptions).