mirror of https://github.com/pikvm/pikvm.git
				
				
				
			fix
This commit is contained in:
		
							parent
							
								
									2c53d096ff
								
							
						
					
					
						commit
						57ee19e7cb
					
				|  | @ -92,10 +92,7 @@ By default, `kvmd-otgnet` will configure network connection between PiKVM and th | ||||||
|      |      | ||||||
| 6. Don't forget to `reboot`. | 6. Don't forget to `reboot`. | ||||||
| 
 | 
 | ||||||
| 
 | ??? example "An example of what the config would look like for a server host that can access PiKVM and has internet access:" | ||||||
| ======= |  | ||||||
|      |  | ||||||
| ??? example "An example of what the config would look like for a server host that can access PiKVM and has internet access (Please edit to suit your needs):" |  | ||||||
|     ``` |     ``` | ||||||
|     otgnet: |     otgnet: | ||||||
|         firewall: |         firewall: | ||||||
|  | @ -111,33 +108,47 @@ By default, `kvmd-otgnet` will configure network connection between PiKVM and th | ||||||
|     ``` |     ``` | ||||||
| 
 | 
 | ||||||
| 
 | 
 | ||||||
| ======= |  | ||||||
| ## Working with Windows Computers | ## Working with Windows Computers | ||||||
| This has been proven to work with Windows: | This has been proven to work with Windows: | ||||||
| 1. Set the driver type to `rndis` (see above) | 
 | ||||||
| 2. Download this driver on the Windows machine and unzip it somewhere: [https://modclouddownloadprod.blob.core.windows.net/shared/mod-rndis-driver-windows.zip]  | 1. Set the driver type to `rndis` (see above). | ||||||
| 3. Open the devices manager \ | 
 | ||||||
|  | 2. Download [this driver](https://modclouddownloadprod.blob.core.windows.net/shared/mod-rndis-driver-windows.zip) on the Windows machine and unzip it somewhere. | ||||||
|  | 
 | ||||||
|  | 3. Open the devices manager:<br> | ||||||
|      |      | ||||||
| 4. Select `Properties` of the `Composite KVM Device` \ | 
 | ||||||
|  | 4. Select **Properties** of the **Composite KVM Device**:<br> | ||||||
|      |      | ||||||
| 5. Select the `RNDIS Device` and click properties \ | 
 | ||||||
|  | 5. Select the `RNDIS Device` and click properties:<br> | ||||||
|      |      | ||||||
|  | 
 | ||||||
| 6. Switch to the "Driver" Tab and then click "Update driver" | 6. Switch to the "Driver" Tab and then click "Update driver" | ||||||
|  | 
 | ||||||
| 7. Click "Browse my computer for driver software" \ | 7. Click "Browse my computer for driver software" \ | ||||||
|      |      | ||||||
|  | 
 | ||||||
| 8. Click "Let me pick from a list of available drivers on my Computer" \ | 8. Click "Let me pick from a list of available drivers on my Computer" \ | ||||||
|      |      | ||||||
|  | 
 | ||||||
| 9. From the list of available hardware types, scroll down and select "Network adapters", then click next \ | 9. From the list of available hardware types, scroll down and select "Network adapters", then click next \ | ||||||
|       |       | ||||||
|  | 
 | ||||||
| 10. Click "Have disk" \ | 10. Click "Have disk" \ | ||||||
|      |      | ||||||
|  | 
 | ||||||
| 11. Click Browse, navigate to the folder where you've stored the driver and select the `RNDIS.inf`, press Open and then OK \ | 11. Click Browse, navigate to the folder where you've stored the driver and select the `RNDIS.inf`, press Open and then OK \ | ||||||
|      |      | ||||||
|  | 
 | ||||||
| 12. Select "Acer Netchip RNDIS/Ethernet Gadget" and click Next  \ | 12. Select "Acer Netchip RNDIS/Ethernet Gadget" and click Next  \ | ||||||
|      |      | ||||||
|  | 
 | ||||||
| 13. Dismiss the warning about non-compatible drivers by clicking "Yes" \ | 13. Dismiss the warning about non-compatible drivers by clicking "Yes" \ | ||||||
|      |      | ||||||
|  | 
 | ||||||
| 14. You're done - the device should now be recognized. \ | 14. You're done - the device should now be recognized. \ | ||||||
|      |      | ||||||
|  | 
 | ||||||
| 15. Verify the card is working by pinging your piKVM in a console: `ping 169.254.0.1` \ | 15. Verify the card is working by pinging your piKVM in a console: `ping 169.254.0.1` \ | ||||||
|      |      | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue