Myself and Peter Egerton ran an 'Introduction to Windows 10 IoT on the Raspberry Pi' session recently at a WMUG event and we had some issues connecting remotely into the Raspberry Pi on the network we were presenting from. Not all was in vain as we were able to run our Blinky tutorial, albeit a cut down version, direct from the IoT tutorials on the SD Card.
So I thought I would run through the steps to get the Pi set up with a direct connection to a laptop without need for a network.
You will need to configure your device in advance on a network to achieve this. You can follow my Installing Windows 10 IoT Core on a Raspberry Pi 2' blog entry here - http://wmug.co.uk/wmug/b/pwin/archive/2015/07/26/installing-windows-10-iot-core-on-a-raspberry-pi-2 if you need to get the OS onto a SD Card.
When I have connected to the device via the remote PowerShell session and run an 'ipconfig /all' I can confirm that currently I am using a DHCP server to obtain my IP address.
I can now use the netsh.exe command to set the IP address to a static one.
If I run netsh interface show interface I can obtain the Interface name of the Ethernet Adapter. So the Pi interface is labelled 'Ethernet'
Next I can issue the following command to set the IP address to a static one
netsh interface ipv4 set address "Ethernet" static <ipaddress> <subnet> <gateway>
Now if I enter an ipconfig /all, I can see that DHCP is no longer enabled and I have my IP address set statically.
and I can still ping the device.
Next I need to go to my PC and set the IP address on the Ethernet card to run on the same subnet as the Pi's static address. So for my example I will set to 192.168.1.134 as my Pi is configured to 192.168.1.133.
Finally I need to connect the PI directly into my device with an Ethernet cable from the Pi's socket to my PC's. Then power on the Pi. Once powered up I can see that my Ethernet connection has changed status to 'Unidentified Network'.
At this point I can successfully ping the Pi and run a Remote-PSSession to the device. Happy days!
I can now connect directly to the Pi, safe in the knowledge that I don't have to rely on LAN based network connectivity to be able to remote and upload to it.