Laptop boots PC off wireless internet

espresso

FireFox wrote: »

You'll get more help here I'm sure if you give more info..............

Agreed, when you have answered FireFox's questions:

1. on the desktop run ipconfig /all and post the full results.
2. Connect the laptop and run ipconfig /all and post the full results.
3. Post the full ipconfig /all results from the desktop, while the laptop is connected.

DCFC79

I had a similar issue with my laptop and my brothers iphone, 1 would kick the other off the connection, resolved it by getting a new ip address for the laptop, cant recall how i did it

Damo66a

When a wireless router broadcasts it has two different ranges depending on the router. Wireless G and Wireless B (B being the old style of wireless in its infancy).

Some wireless network adaptors have the capability of being backward compatible. By that I mean that they can run in both G and B wireless modes. However, not all of them do this. Heres a scenario for you:

Lets say your PC is Wireless B and the laptop is wireless G.
All the time the pc is connected to the router(without the laptop) it will be running in B mode. As soon as the laptop comes on and connects to the wireless router, the router will switch to G mode allowing the Laptop to connect. The wireless router will only be able to use one mode at a time.

That said, i think what we need to do is to tell your router to run in B mode only and see if it lets the pc on at the same time.

Now most adaptors that you get can do both wireless G and B modes and it will just switch between the two as needed. However, some can only do wireless B. If the router has switched over to wireless G, then it will disconnect the PC connecting in wireless B mode if it doesnt have the facility to connect in G mode.

princessamy86

righty hoo, I'll get home from work in about an hour so I will try and give lots and lots of info then you lovely people can help me! Thanks

princessamy86

FireFox wrote: »

In case you didn't get this sorted...

It looks like you're laptop's at least getting its IP (192.xxx...) from the router.
You could try the same (ipconfig) on the desktop when its connected and make sure its IP is different from the laptop.
They'll be similar but shouldn't be the same. For example the Laptop may be something like 192.168.1.101 and the desktop 192.168.1.102.
When you do 'ipconfig' also make note of the 'Default Gateway' value - something like '192.168.1.1'. You'll need this to log on to your router setup page.

You'll get more help here I'm sure if you give more info (that applies to everyone posting on this board!) e.g.
1. how you're connected - ADSL/cable broadband?
2. the model number of your Netgear router?
3. the OS on each of you're PCs (XP/Vista and their relative Service packs)
4. whether you have an ethernet connection you could use on either PC.
edit - oh and also whether you have Firewall software running on either PCs e.g. Zonealarm

Just a bit of a bump really as a lot of people seem to be having similar Wireless issues and it would be good to get to the bottom of it for you.
I'm sure someone here will be able to offer more help

1. I have ADSL broadband
2. Model number-I don't know it, I have the serial number but where would I find the model number?
3. Both are on XP
4. I can't use an ethernet connection because it won't reach-I need to use my laptop at the table

No firewall software that I know about.

Hope that's the info you need, I've actually got the laptop running now and both computers are connected. It would seem it just boots the OH half off when he is gaming?!? Not sure I really understand that. Just wanted to say a big thank you to anyone who tries to help with this.

johnmc

Check the BIOS settings for the PC.

Disable "Start on LAN".

princessamy86

How do I do that please johnmc?

johnmc

It depends on your PC. As it boots up look for the prompt for "Setup" or "BIOS". Usually pressing <F2>.

Once in it's a case of going through the screens looking for the "Boot on LAN" and check it's set to No.

If it's any concellation mine does it if it fails to boot for whatever reason or if I have to hard-reset it. Usually shutting it down properly sorts that out, though.