Some windows network card drivers don't work well if the GW is blank. Your right, it shouldn't matter... however, not everyone is consistent in how they implement things.
Songboy - just set up a "dummy" network. Pretend your gateway and DNS are the same, non-existant device. I like to use uncommon RFC 1918 address spaces in case I forget to change things around when I eventually plug things back into a real network. The 10.x.x.x space is perfect for this. I also like to pick easy for me to remember numbers.
So let's pick 10.10.10.x as our network, and our placeholder gateway and DNS will be 10.10.10.1. Let's put the console on address 5, and the computer on address 10. With all of that here is how the console and computer should be configured:
x32 Console:
IP Address: 10.10.10.5
Subnet Mask: 255.255.255.0 (or /24 depending on the UI layout)
Gateway: 10.10.10.1
DNS: 10.10.10.1
Computer:
IP Address: 10.10.10.10
Subnet Mask: 255.255.255.0 (or /24 depending on the UI layout)
Gateway: 10.10.10.1
DNS: 10.10.10.1
Note the gateway and DNS doesn't actually exist - which is fine since we really don't need them. It's just I have seen computers, again depending on the network card driver, that don't act predictably if there isn't something plugged in there.
EDIT: and on the computer you need to set the IP address manually, NOT with DHCP - turn off DHCP and set the IP address manually (also called a static IP)



Reply With Quote