For Windows networking to work you need to boot an image inside DOSBox.

Which is what I'm doing. Should've mentioned that, sorry.

MB6 is in theory kind of old at this point and offers no particular advantages over ykhwong's build.

Don't you need winpcap?

Have it installed. I actually tried installing it twice, since it wasn't picking up my adapter. (plus it needed to be updated. 🤣)

Any other details you'd care to share..?

Have you seen http://home.arcor.de/h-a-l-9000/ne2kstuff/db_ne2000.html ? What do you get with realnic=list ?

Status Window says that it's using the MS Tunnel Interface Driver on localhost. I read somewhere else to try that driver, but it didn't work. I have that set, only because it chooses to not recognize my real card, an Atheros 802.11 a/b/g/n Dualband Wireless Network Module. I'm thinking that the issue is with WinPCap communicating with DOSBox. If that's the case, how would I get it working correctly? If it's not, is there any other potential problems there could be?

Edit: Just saw your question about the list parameter. This is what I get:

- Network adapter 'Realtek RTL8168C/8111C PCI-E Gigabit Ethernet NIC' on local host
- Network adapter 'MS Tunnel Interface Driver' on local host
- Network adapter 'Microsoft' on local host
- Network adapter 'Sun' on local host
- Network adapter 'MS LoopBack Driver' on local host

A moment's Googling does indeed suggest that Winpcap and wifi drivers do not mix.
http://www.winpcap.org/pipermail/winpcap-user … ber/004490.html

Perhaps the Network Monitor suggested therein is worth a try.

What other values for realnic have you tried? "Atheros" evidently isn't going to do it, since it isn't even in the list.

You should list out your realnic first, then write it down.
And re-open the dosbox.conf and write that number into that file.
It's a matter of detection.

Jorpho wrote:

A moment's Googling does indeed suggest that Winpcap and wifi drivers do not mix. http://www.winpcap.org/pipermail/winpcap-user […]
Show full quote

A moment's Googling does indeed suggest that Winpcap and wifi drivers do not mix.
http://www.winpcap.org/pipermail/winpcap-user … ber/004490.html

Perhaps the Network Monitor suggested therein is worth a try.

What other values for realnic have you tried? "Atheros" evidently isn't going to do it, since it isn't even in the list.

Wouldn't work. All network monitor does is just capture packets for reading. It can't act as a driver. Capturing isn't the same as sending/receiving.

I've tried using LoopBack as well, with the same results. Does Error Code 0 definitely mean that the problem is outside of DOSBox, and that there's no way that it can be anything inside of MS-DOS?

And I remembered reading something about WinPCap and wifi cards... but I thought that they would've fixed it. So, it looks like my only option would be to use LoopBack, but I have no idea why that wouldn't be working, either.

Before I fool around with things on my PC outside of DOSBox, I just want to be sure that there's nothing else that could be the issue inside of DOSBox itself. Am I setting the proper settings inside WfW for a DHCP setup (see original post)?

Keith wrote:

Wouldn't work. All network monitor does is just capture packets for reading. It can't act as a driver. Capturing isn't the same as sending/receiving.

Hmm, I misread that earlier.

I've tried using LoopBack as well, with the same results.

Meaning, you used "realnic=loopback" in your DOSBox.conf? Did anything appear in the status window?

Does Error Code 0 definitely mean that the problem is outside of DOSBox, and that there's no way that it can be anything inside of MS-DOS?

I'd say the lack of anything in the status window is more telling than anything else.

If you want to rule out problems with Windows 3.x, you can try using the Novell IPX drivers at http://home.arcor.de/h-a-l-9000/ne2kstuff/db_ne2000.html in DOS for testing purposes.

Sorry for the late reply, I was busy with quite a few things.

Anyways...

I meant I used the list number for the loopback adapter. Trying to type in "MS LoopBack" displays normal output/expected output in the status window, but returns the same results when trying to use it. I'll take a look at the IPX Drivers.

Thanks.

Maybe disable COM2 as it uses IRQ3. If it still says something about IP driver error the error could be in your Win3.11 configuration.

You meant in the config file, right?

1serial1=dummy
2serial2=disabled
3serial3=disabled
4serial4=disabled

Still got the same results. 😖 It did get rid of the warning that came up when trying to configure the network adapter, though.