Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Why XP Is Slowly Killing Me
- Thread starter bobber205
- Start date
- Sort by reaction score
Whew. Now that I know what I need to do, it's off to bed!
I'll order one in the morning. Btw balamw if you have time, could you go to newegg and pick out a good one. For luck? I trust ya.
You should always buy a wireless card that's of the same brand as your router. You'll get the best results that way.
This is definitely true if you have anything non-standard going on in the router, like pre-N or "speed-booster".
Less likely to actually make a difference here since you already have your MacBook in the mix and it probably doesn't use the same brand as your router unless you're using an Airport.
Most wireless networks will fall back to the least common denominator once you introduce a device that doesn't support all the functions.But do tell us what brand/model the router is.
B
Generic, so you should be fine with anything. Stay with a name brand where possible, like this SMC. http://www.newegg.com/Product/Product.asp?Item=N82E16833129031
Low price, good ratings, decent brand.
B
I know I shouldn't be I am considering changing my router's ip to 192.168.0.2 to avoid any confusion for xp.
May be a bad idea... Should I try?
Yes. There's no need to use ICS for anything you're doing. If XP can't deal, it's its own fault
Like I said before, the router is all you'll ever need for a home LAN. The only time you need ICS is if you don't have a router. A switch is also used for when you have one cable coming from a central router and need to equip a lot of computers with internet from that one cable.
Just leave the router settings alone and you'll have the best results.
Oh, btw Bobber, I think you need to give us your Wii's nickname too or else the friend code won't work.. Not really sure, but everyone I've seen has given their Wii nickname as well as the code, and I read somewhere the nickname is required.
If you must, change the third number instead of the fourth. e.g. make the router 192.168.1.1 instead of 192.168.0.1.I know I shouldn't be I am considering changing my router's ip to 192.168.0.2 to avoid any confusion for xp.
May be a bad idea... Should I try?
I agree with the Hobo though avoid it if you can and get the wireless NIC adapter.
B
To the original Poster of this thread... You're bashing XP because you dont know what you're doing when it comes to networking? How is that the operating systems fault? I'm not trying to bash you but just being blunt. It would be like me taking apart a car's engine and then saying its stupid if i cannot put it back together.
Anyway why are you making your network so complicated with ICS? You already have ICS..its called your router. To get everything working, do the following:
1. Configure the router's wireless with the SSID and Wep settings that you would like and make sure DHCP is enable on it and then connect to the thing with your Mac.
2. Make sure your XP box is set to DHCP and not Static and plug a long straight through cable from the router to the PC. Make sure its not a bad cable.
3. Thats it.
4. No really...it was done after number 2.
Anyway why are you making your network so complicated with ICS? You already have ICS..its called your router. To get everything working, do the following:
1. Configure the router's wireless with the SSID and Wep settings that you would like and make sure DHCP is enable on it and then connect to the thing with your Mac.
2. Make sure your XP box is set to DHCP and not Static and plug a long straight through cable from the router to the PC. Make sure its not a bad cable.
3. Thats it.
4. No really...it was done after number 2.
Dude. Did you read my post?
Trust me, I have many more reasons to bash XP. It simply isn't "trained" in the same manner as OS X and assumes too much it places it shouldn't and not enough in others.
The desktop PC cannot reach the router. It won't ever reach. I would have to rewire my house to make that possible. I have DHCP set.
All I wanted to do was create a network between my macbook and my desktop PC and XP refused to cooperate because I made the mistake of having the ethernet cord unplugged when I started up.
Trust me, I have many more reasons to bash XP. It simply isn't "trained" in the same manner as OS X and assumes too much it places it shouldn't and not enough in others.
The desktop PC cannot reach the router. It won't ever reach. I would have to rewire my house to make that possible. I have DHCP set.
All I wanted to do was create a network between my macbook and my desktop PC and XP refused to cooperate because I made the mistake of having the ethernet cord unplugged when I started up.
I tried reading the post but none of it was making any sense. Sounded like you were all over the place. Can you also give me an example about XP assuming too many things in many places when it shouldnt and how this relates to your networking issue? Just curious.
Also what happened when you set the XP box to DHCP. Did it get an address? If so, do you remember what DNS server info it grabbed from the router? When you were setting IP manually...what were you entering for DNS info?
If the DNS servers are not entered, then it cant resolve any addresses. You can ping but not surf.
Also what happened when you set the XP box to DHCP. Did it get an address? If so, do you remember what DNS server info it grabbed from the router? When you were setting IP manually...what were you entering for DNS info?
If the DNS servers are not entered, then it cant resolve any addresses. You can ping but not surf.
Dude. Did you read my post?
Trust me, I have many more reasons to bash XP. It simply isn't "trained" in the same manner as OS X and assumes too much it places it shouldn't and not enough in others.
The desktop PC cannot reach the router. It won't ever reach. I would have to rewire my house to make that possible. I have DHCP set.
All I wanted to do was create a network between my macbook and my desktop PC and XP refused to cooperate because I made the mistake of having the ethernet cord unplugged when I started up.