Does anyone have any idea what causes a VNETSUP Error 6107? I know it is a virtual driver for a network, but I am getting it on 2 different computers that are not networked together in any way. It comes up after I start the computer and then goes into an endless of restoring registery back-up then restart - restoring registery back-up then restart. The only common part is a 300 AMD K6-2 chip.

I believe this is caused by a missing windows file. Try to restore it from the CD.

You will want to go into the control panel, click on network, and then remove all items in the network config. then go into the add/remove programs and windows setup and take the check out of dialup networking. reboot the system and then add the check back to dial up networking, and add back in your network configuration items.. works for me all the time in tech support

I tried, but all the Control Panels were locked out by another error dialog box. I cannot get out of the endless 6107 loop... I can activate Explorer.exe but that's about it...

Your registry is corrupt; you're going to have to restore it from backup or reinstall Windows.See http://support.microsoft.com/support/kb/articles/Q145/8/36.asp In my case, I'm getting it on a specific PC; I've reinstalled 20 times but it's still happening;I'm guessing my instance is hardware related.

Yeah - I've been having this problem (On a stand alone comp - but with DUN and a NIC installed running W95c) a lot as well. Sometimes when it occurs, it manages to restore but quiet often it just comes up with the same error everytime. I have to deltree windows and reinstall when that happens :(. I did recently (about 5 mins) find this though, haven't had chance to try it out yet... .24. How do I address "VNETSUP error 6107"? Date: Tue, 14 Nov 1995 06:33:34 GMT From: patrickm@airmail.net (Patrick Moore) Message-ID: <489dap$jbf@server.iadfw.net> Microsoft's answer, from Knowledge Base article Q137454, is to delete the following Registry entry: HKEY_LOCAL_MACHINE\System\CurrentControlset\Services\VxD\vnetsup You can delete it if you want, but if you have it in your old system.ini, or win.ini etc., it will just show up again and again every time you restart windows. Do a search of these files in your windows directory and remove any reference to vnetsup. Then remove it from your registry, ******** I would strongly suggest you backup your startup files ( four in all including msdos.sys ) before you change anything in your registry. Also - someone said in another thread that if they leave the machine shut down for a few minutes the problem goes away - does this actually work?? Thanks, Mark

I had this problem until last night. In frustration, I used regedit to delete all references to VNETSUP. I had a back up registry that worked without fail so I figured I had nothing to lose. I have had no problems since doing this. I have been able to install, shut down, etc. If you back up a working copy first, you have nothing to lose. Based on my research, you should only need VNETSUP if you are using workgroups.