But unless you want to tell me otherwise, I guess those are all separate issues beyond the topic of this post, which is for a driver that will work with my old NIC. Also, the LAN2 connection on the HP/Win7 machine has now changed itself back to Public Network two times since I reset it to Home Network, so I don't know what's going on with that, though I have made sure that the box to "treat all connections as public" is not checked. I can't see the HP/Win7 machine from the XP machine, and the connection between the XP and Win2000 now says "inaccessible," so something's apparently changed there.
My third machine, which is running Win2000, is not included in the network map on the HP/Win7 machine, but under Computers Near Me on the Win2000 machine I can see the HP/Win7 machine, and today I successfully transferd a batch of files from HP/Win7 to Win2000. When I click "See full map" for the LAN2 connection I see icons for my HP/Win7 machine, my XP machine, and my hub, so it looks like all that is as it should be. GREAT Ethernet for windows 7 32 bit :) worked like a charm :) 24-Feb-19 23:55 thnx a lot. For anyone who may be interested, this document helped me get all that business straightened out:Īfter I made the LAN2 a Home Network connection (same as my onboard ethernet LAN), I began receiving packets. I searched for an answer and changed the LAN2 connection to Home Network, as it had somehow been designated as Public Network (not by me, though).
After the driver installed I could see under LAN2 Status that I was sending packets but not receiving any. At least, I've got a LAN2 connection in the Network And Sharing Center and seem to have made some sort of connection with my other two networked machines.
Ethernet driver controller for windows 7 install#
So now that I've followed your instructions for the manual, I'm happy to report that the install completed and that the driver works for my NIC. No, in a rush to leave for an appointment yesterday I'm afraid I didn't think to try the manual install method, as I just assumed (after several attempts with the auto) that there must be some other issue halting the install that I'd have to fix first.