I've searched the www and I can't seem to find a conclusive answer to my problem, hoping someone here can help me.

Two home pc's, PC A. is windows vista and PC B. is XP Home Edition. I'm using a Sweex wireless router, PC A. has a belkin wireless card and B. has a Sweex wireless card. The problem is if either PC is connected to the internet it knocks the other PC's connection to 10.0.0.8(the wireless router address?) and the other PC remains connected.

Why the heck will they both just not use the same bloody connection...It's a noob question with an obvious simple fix I imagine...but it's just doing my head in at this stage....help!...pweeeeze?

Edit: I've already updated the XP machine(LLTP) so the Vista machine will 'see' it in network Lan.

Knowing a bit more would help (for instance DHCP and NAT configuration, model and revision of router, possible use of proxies, IP Addresses, whether they are assigned by DHCP or not, if the problem happens on all ports or just 80-http or something else, if the machines regularly ping each other before and after the problem appears).

Quote from CSU1 :

The problem is if either PC is connected to the internet it knocks the other PC's connection to 10.0.0.8(the wireless router address?) and the other PC remains connected.

Does this happen when only PC A is connected to the internet and PC B isn't, or vice versa?

Well, like mine is, you have one pc directly plugged in, Via Ethernet, if its close to the router, and the Wireless, and it should log on automatically through the master user account of the email

Quote from wheel4hummer :

Does this happen when only PC A is connected to the internet and PC B isn't, or vice versa?

No, if I reset the router and modem the two pc's will connect and stay connected, however if I restart or reboot one pc that pc will only connect to 10.0.0.8, meaning I have to go back and reset the modem and router and two pc's...it's very annoying.

Albeig, all standard windows settings apart from tcp over net bios is disabled and the network is encrypted and uses wep security..also the machines have no need to ping one and other directley...just standrd connections.

Quote from CSU1 :

Albeig, all standard windows settings apart from tcp over net bios is disabled and the network is encrypted and uses wep security..also the machines have no need to ping one and other directley...just standrd connections.

I just made a few standard questions that are part of a standard troubleshooting procedure. Without some of that info I can't go on because the information given is way too generic. But I bet it would have been easy to do an ipconfig /all on each machine and try using ping with firewalls disabled just to see if there are errors in address attribution (which may be the case) and if you're able to ping in and out of your network.

After all I didn't ask for a complete comparison of two Wireshark packet captures from each PC...

why not giving manual ip adress to pc's? one is 10.0.0.9 and other is 10.0.0.8 should do.

First, you don't know if he already has assigned fixed ip addresses (although improbable), and second, you cannot assign 10.0.0.8 to a machine because that's the address he declared as being used by the router. More information are badly needed in this case.

yeah sorry for the lack of information as everything is untouched...as in windows network settings...ip's??? I believe they are dynamically assinged by my isp???

as far as I can make out when one of the pc's drop off the network from either low signal or system reboot the modem/isp will not assign an ip as there already is a pc running with an assigned ip address, the pc that dropped off the network then searches and only finds the wireless router(10.0.0.8)(modem won't give it an ip)...does this even make sense to you i'm sorry but I cant get my head around this one...what other information woud you need to fault find in a wireless network running two PC's(vista+XP) both which have their ip's assigned dynamically?

Quote from CSU1 :

yeah sorry for the lack of information as everything is untouched...as in windows network settings...ip's??? I believe they are dynamically assinged by my isp???

Your external IP address is assigned by your ISP. Your internal IP addresses are assigned by the router. Try manually setting the computers IP addresses to 192.168.1.100 and 192.168.1.101.

That won't work. The router has an internal ip address (as said by CSU1) of 10.0.0.8, with a subnet of 255.0.0.0 (but it could be also 255.255.255.0), so assigning internal addresses in a completely different subnet would completely screw connectivity until the original settings are restored. Ip addresses have to be in the same 10.0.0.x range with 10.0.0.8 as gateway and the same subnet mask of the router, but then again you have to check if the chosen addresses are served by NAT correctly. And not only that.

Edit: unless he's in a subnet and the reported IP address is the external one, of course. Fastweb works this way in Italy.

...ok as I said above, in layman's terms(I don't fully understand)it's as if my modem (not router) will not assign an ip to the pc that dropped off the network because the second pc has an address assigned, the modem does'nt bother with second pc. The pc only 'sees' the router and connects to 10.0.0.8

In this case it is resolved reseting the wireless router and rebooting the pc

I'm extremely confused, yet I see a possible reason through the fog. Is this a modem (not a router) assigning a single IP address? If so, you have your answer.

ntl modem
Sweex router

...sorry I thought I explained this