Okay, I'll check for excess IPs next time I get on. Note that we're only using one NIC, "Wireless Network Connection", both to connect wirelessly to the school internet and to the robot's d-link. To connect to the internet, I made a little script on the desktop:
Code:
@echo off
:start
for /f %%V in ('netsh wlan connect KM-Wireless') do set TEST=%%V
if %TEST% neq Connection 2>nul (pause|echo+Could not connect to access point KM-Wireless. Press a key to try again, or close this command line window to end. . .)
if %TEST% neq Connection goto start
netsh interface ip set address "Wireless Network Connection" dhcp
Then to connect back to the robot, we simply restart driver station, which automatically sets the static IPs for the NIC and ethernet. (Please note that we haven't run this batch script, we simply do the procedure I described, and get the problem I described.)
We have access point 2077 set to connect automatically. We do not have KM-Wireless set to connect automatically.