nah i dont want a real one, just internal. yes its netgear. thanks jsut finished setting it up. :) my new static IP is set up along with my port forwarding of port 43594 for both TCP and UDP
I've had to use the ipconfig three different times from three different computers for three different things.
so far: Windows 7 is THE hardest. I did it on Vista and XP and they are MUCH easier
and i am totally bookmarkign this webpage as this is the best help for windows 7 I have found so far. amybe ill get some help with another problem I've been having tomorrow
Ok... simple trick... If you're setting up static IPs inside a LAN you can quite simply make them up as you go... there's no need to even care what address DHCP might assign... In fact if you are running DHCP for wireless devices you want to actually avoid the DHCP range on your router (to avoid collisions).
It's a private lan... so...
You can get the first three numbers from your router's admin address. In your case 192.168.1
The subnet mask on any net with fewer than 254 machines is always 255.255.255.0
With a subnet mask of 255.255.255.0 the only number that can change is the last one and that you can simply assign on your own in the range of 2 to 254, so it doesn't conflict with your router itself.
Most home router's gateway and dns relays use the same ip address as their admin screen.
Real easy.... Now, don't get me wrong, I'm not saying you did all that searching for nothing... just the opposite... think how easy it will be next time...
Im actually using windows 10 and had the same problem, and tried what i read here, but it was a little different on windows 10, but it worked. i had been trying to fix this for so long and finally its fixed. thanks so much.
For some reason, I had to start CMD w/ 'run as admin' to get ipconfig working again.
Probably to do w/ a cdir command I did for GNS3 VM purposes (I must have forgot I did one outside of the VM on my main host desktop).
So was probably in wrong directory in CMD prompt. ;_;
Enjoy!
-Nikky
Quote