Page 1 of 2
Networking problems
Posted: 3. Feb 2017, 00:36
by Maynard Cornchowder
My point of sale network runs Counterman. An old 16bit dos program. No, i don't want to upgrade. I have hardly any issues running counterman on windows 7 or older machines. My entire network has mismatched OS's and the only trouble I run into is when I'm using windows 10. Boom, Virtualbox to the rescue!
Now the issue I'm having is, I need my POS to talk to the VM. I've tried mapping the network drives and can't get it to find my pos network that I need to use. I made a VM with windows xp SP3. I'm new to VM software but I've been reading the manual and have a good idea on how to navigate. I tried changing my network driver from "NAT" to "NAT NETWORK" but it won't let me choose a name, and won't let me change without having a name. I switched to "bridged" just to see what would happen, I get to the network log in and type in my info but nothing happens.
Please help!
Re: Networking problems
Posted: 3. Feb 2017, 14:54
by scottgus1
Ok, you want your guest to get on the network that the Counterman software is running on. Your host PC will have to be connected to that network, too, then you would Bridge your guest to the host's network card (Note that it should be a wired network card for best connection.) Bridged makes your guest look as if it was just another PC on the network.
Now you will need to know how your shop POS network works to get your guest to communicate. When you plug a new PC into that network does it automatically connect? If so the guest should connect too, then you just have to get the Counterman software running, just as you'd do if you installed Counterman on a real PC.
If you have to set IP addresses net masks and such to get a new PC to recognize your shop POS network, you will have to do exactly the same thing inside the guest XP. Then install Counterman as usual.
Using Bridged, you just think of the XP guest as another new PC on the network and you should be good.
If you have any further questions or any errors come up, let us know.
Re: Networking problems
Posted: 3. Feb 2017, 18:15
by Maynard Cornchowder
The Host PC is connected to the network. The guest also has internet access. All through the lan. I've chosen bridged. R. Click "my computer" > map network drive > type in server info > nothing happening. It doesn't automatically connect unless I tell it to remember the password.
Re: Networking problems
Posted: 3. Feb 2017, 18:21
by scottgus1
Please open a command window on the host PC, and the guest, and run "ipconfig" in each. Copy the text output of each command and post the output on the forum in a "Code" tag, identifying which is host and which is guest.
Also, if the "server" you are trying to share a folder on is another PC on the network, run an "ipconfig" and post the output of that machine, too.
Further, please attach the guest's .vbox 'recipe' file as a zip file, using the Upload Attachment tab under the textbox where you type new posts. You can find the guest's .vbox file by right-clicking the guest in the main Virtualbox window and choosing Show in Explorer. Be sure your host OS is set to show known extensions.
Please don't obfuscate any data in the command outputs, that's exactly the stuff we need to see if your guest is set up properly. We won't be able to hack in, don't worry.
FWIW:
It doesn't automatically connect unless I tell it to remember the password.
This is expected. You must tell the OS what password to use tp get automatic re-connect.
Re: Networking problems
Posted: 3. Feb 2017, 18:22
by Maynard Cornchowder
It's weird because I can see other computers on the network. Using the server login info, I can connect to the other PC's. I just can't see the server's PC
Re: Networking problems
Posted: 3. Feb 2017, 18:28
by Maynard Cornchowder
This feels like a trap...
Re: Networking problems
Posted: 3. Feb 2017, 18:39
by Maynard Cornchowder
I can't post what you asked me too. says I have to be a member for 1 day and have 1 post before I post urls. Can I PM or email you?
Re: Networking problems
Posted: 3. Feb 2017, 18:48
by scottgus1
All this info can be posted on the forum without offsite third-party website involvement. Just read the instructions carefully.
Re: Networking problems
Posted: 3. Feb 2017, 19:00
by Maynard Cornchowder
It'll have to wait a few hours.. I created my account less than 24 hours ago so it won't let me post what you asked.
Re: Networking problems
Posted: 3. Feb 2017, 19:06
by scottgus1
You can post all of the command outputs as text clipboard pastes. Enclose the pasted text in Code tags.
The .vbox zip file is attachable. See the instructions I posted on how to attach it. You can do this right now if you just read the posted instructions.
Re: Networking problems
Posted: 3. Feb 2017, 19:13
by Maynard Cornchowder
host
Code: Select all
C:\Users\KT's Cycle>ipconfig
Windows IP Configuration
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::2414:28b8:a1a8:c764%11
IPv4 Address. . . . . . . . . . . : 192.168.56.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : hsd1,tx,comcast,net
IPv6 Address. . . . . . . . . . . : 2603:300c:404:4800::3771
IPv6 Address. . . . . . . . . . . : 2603:300c:404:4800:e0b3:62c:9aab:53e2
Temporary IPv6 Address. . . . . . : 2603:300c:404:4800:302d:aa3f:f7be:5c5
Temporary IPv6 Address. . . . . . : 2603:300c:404:4800:71b8:371c:d569:f66
Temporary IPv6 Address. . . . . . : 2603:300c:404:4800:c171:db18:c0ef:20d
Link-local IPv6 Address . . . . . : fe80::e0b3:62c:9aab:53e2%9
IPv4 Address. . . . . . . . . . . : 10.1.10.209
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::fc91:14ff:fe8a:1e23%9
10.1.10.1
Tunnel adapter isatap.{DF5197C5-8758-4522-A3F6-F2FF739D510E}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:34e5:77c4:302d:1163:f5fe:f52e
Link-local IPv6 Address . . . . . : fe80::302d:1163:f5fe:f52e%10
Default Gateway . . . . . . . . . :
Tunnel adapter isatap,hsd1,tx,comcast,net:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : hsd1,tx,comcast,net
C:\Users\KT's Cycle>
Guest
Code: Select all
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\POS1>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection 3:
Connection-specific DNS Suffix . : hsd1,tx,comcast,net
IP Address. . . . . . . . . . . . : 10.1.10.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.10.1
C:\Documents and Settings\POS1>
Re: Networking problems
Posted: 3. Feb 2017, 19:29
by scottgus1
The guest seems to be on the same network as the host, good. What PC has the folder you're trying to share? And what are you entering to point to the shared folder?
Re: Networking problems
Posted: 3. Feb 2017, 19:41
by Maynard Cornchowder
I haven't been able to run ipconfig on the pc with the folder i'm looking for.
When I'm trying to connect, i've been mapping the network drive and trying to find S: //server/pos
which every other pc on my network has.
Re: Networking problems
Posted: 3. Feb 2017, 19:44
by scottgus1
OK, I don't know if it's just a typo, but it should be \\server\pos, not //server/pos
In the guest OS, open the Run box (Windows flag key + R). Type \\server. Hit OK. What happens?
Re: Networking problems
Posted: 3. Feb 2017, 20:08
by Maynard Cornchowder
typo sorry.
After I run \\server it comes up with a username and password prompt.
in which after I type in the info, nothing happens.