That looks like the right syntax for the packet driver for VMWare.
When you issue that command, does it come back with a message saying that it's loaded, and give you the NIC's mac address? That's about the best way to tell if its actually loaded.
Are you using WG's built in ethernet capabilities? Or something like Vircomm's MajorTCP?
BTW, i've had quite a bit of trial and error experience in both WG2, and VMWare (and the two combined). if you run into any odd issues, feel free to PM me.
When you installed WG, at the end of setup it asks you how you're connecting to the network. It lets you pick ethernet slip/ppp/whatever.
What did you select?
if you picked Ethernet, that;s probably your problem. I ran into the same problem when i first setup my board. You have to tell WG that it's not connected to the network, then install MajorTCP/IP and let it handle the network calls.
If you have WG and MajorTCP both trying to access the packet driver directly, one or the other wont be able to access the packet driver. At that point, you'll get the error youre reporting.
I'd imagine that there's a tool you can run that will let you re-setup WG's network connectivity, i dont know what it is though.
Thats the Problem thanks for the help ...now I know what to do to get it running This was driving me crazy because I did everything the way I always do...but I am adding the MajorTCP/IP this time and I didnt even think about that....see what going without sleep will get you hehe again thanks Venom
I set my board up years ago, and took it down due to a hdd failure when i moved.
After about a year i decided to put it up on another hdd. Took me 2 days of pulling my hair out with this exact same problem! I had forgotten how i set it up the first time, and when i went to re-set it up, i fell into the same trap. heh.
