Problem Connecting After Creating Static IP Address

[St. Widge]

I created a static IP address so that I could forward the ports on my XBox and now a desktop running Windows XP and a Laptop running Widows XP will not connect to my wireless network. They both had no issues prior to creating the static IP. And, my desktop which I used to create the Static IP still connects fine and so do both of the iPads that are used in the house.

Anyone have an idea about what's going on and how I should go about fixing it?

[buzd]

This is how you spend halftime?

[St. Widge]

Originally Posted by buzd

This is how you spend halftime?

Yes, I'm that big of a geek. I'm really just too nervous to think about the game.

[buzd]

You know you can't just make up static IPs, right? What's your router's internal address?


And actually before you answer that, the problem is probably that once you set static addresses, you need to manually set your DNS addresses (either to your router or to that of your ISP), so since you didn't, you're probably connected, but addresses won't resolve.

And take a Xanax.

[zeetes]

Originally Posted by St. Widge

I created a static IP address so that I could forward the ports on my XBox and now a desktop running Windows XP and a Laptop running Widows XP will not connect to my wireless network. They both had no issues prior to creating the static IP. And, my desktop which I used to create the Static IP still connects fine and so do both of the iPads that are used in the house.

Anyone have an idea about what's going on and how I should go about fixing it?

static ip, port forwarding, broken connection on laptop, widge

somehow all of these together make sense.

[St. Widge]

Originally Posted by buzd

You know you can't just make up static IPs, right? What's your router's internal address?


And actually before you answer that, the problem is probably that once you set static addresses, you need to manually set your DNS addresses (either to your router or to that of your ISP), so since you didn't, you're probably connected, but addresses won't resolve.

And take a Xanax.

I'm really not certain what all of that means, but no, I didn't know you can't just make up static IPs. Then again, I'm not sure if I did that or not.

Anyway, it won't connect at all. It's not just that it won't resolve the addresses. (At least I think that's what it is.)

So, anyway, I set the DNS servers to my routers ISP, but it didn't help. My router's internal address is 192.168.1.1

And, yes, this is what I do during games.

[jrdbrn]

All you have to do is log in to your router and see what range does your DHCP server start at. If it starts at 192.168.1.100, then give your Xbox a static of 192.168.1.99, Subnet 255.255.255.0, Gateway 192.168.1.1.

What static did you give the Xbox?

[NewOrleansFan]

Even with an IP conflict, it shouldn't mess up both computers. The only thing comes to mind is that you may have disabled DHCP on your router by accident