EDIT: I totally misread what you wrote and was advising on another problem.
I'll come back to you.
IP. You P. We all P for IP.
-
Gavin Scott
- Admin
- Posts: 6442
- Joined: Fri 15 Aug, 2003 13.16
- Location: Edinburgh
- Contact:
Instead of having them on automatic - set them manually. Try setting 192.168.0.1 on your pc and 192.168.0.2 on your sisters laptop. Does that work? If you have any others connected set those the same, just alter the last number in sequence! Make sure the subnet mask is set to 255.255.255.0 on all the computers.
Hope it helps!
Hope it helps!
I can truly symphathise with wireless networks. When I first got mine I got some awful DrayTek Vigor ADSL Router as well as a Linksys Wireless Broadcaster and anoter set to Wireless Repeater mode. It's not a funny sight when you have to spend approximately 4 hours setting up subnets (as each manufacturer is different) and configuring the bloody things! There's no excuse not to just buy a nice box which does it all. 
All "IP Conflict" means is two computers are connecting to the network, but somehow they have ended up with the same IPs.
It would help if you posted a screenshot (Use Alt+PrintScreen to take it and then paste it into Paint and save it as a JPG, then post it on this forum) of the Wireless Network properties area. Once you're connected (or not, as the case may be -- having tried to, anyway), Click Start >> Connect To >> Wireless Network Connection ... . Click the Support tab and take a screenshot as described above. Alternatively simply type out the informaiton dispalyed. Before you panic, try clicking the Repair button which may help to resolve the issue. Finally, if all this doesn't work, has your sister got Service Pack 2? A major feature of it is the updates to Wireless Networking and this may solve your problem.
If you know you need to delve deeper, the suggestion of using manual IP assignment would be favourable. You will need to alter the settings on your router accordingly; decheck the DHCP box. On your routher see if you can find settings to alter the IP Pool Range. It may be that yours is set to too small a range (e.g. 12-15) to handle all computers thus generating a conflict. If you want to have fun you can also change the 192.168.1.x value to something more imaginative... but you probably wouldn't want to bother with that
The whole point of DHCP is to assign IPs to computers automatically so you don't have to worry, but in this case it's clearly gone wrong.
By the way -- irrelevant and probably the least of your worries but I thought I'd ask -- I hope you have WEP or Mac Address Identification set up on your router. I didn't when I first got mine and there was a list of about 15 unique IPs connecting!
All "IP Conflict" means is two computers are connecting to the network, but somehow they have ended up with the same IPs.
It would help if you posted a screenshot (Use Alt+PrintScreen to take it and then paste it into Paint and save it as a JPG, then post it on this forum) of the Wireless Network properties area. Once you're connected (or not, as the case may be -- having tried to, anyway), Click Start >> Connect To >> Wireless Network Connection ... . Click the Support tab and take a screenshot as described above. Alternatively simply type out the informaiton dispalyed. Before you panic, try clicking the Repair button which may help to resolve the issue. Finally, if all this doesn't work, has your sister got Service Pack 2? A major feature of it is the updates to Wireless Networking and this may solve your problem.
If you know you need to delve deeper, the suggestion of using manual IP assignment would be favourable. You will need to alter the settings on your router accordingly; decheck the DHCP box. On your routher see if you can find settings to alter the IP Pool Range. It may be that yours is set to too small a range (e.g. 12-15) to handle all computers thus generating a conflict. If you want to have fun you can also change the 192.168.1.x value to something more imaginative... but you probably wouldn't want to bother with that
The whole point of DHCP is to assign IPs to computers automatically so you don't have to worry, but in this case it's clearly gone wrong.By the way -- irrelevant and probably the least of your worries but I thought I'd ask -- I hope you have WEP or Mac Address Identification set up on your router. I didn't when I first got mine and there was a list of about 15 unique IPs connecting!
AWFUL? I think there's a typo there somewhere.cdd wrote:I can truly symphathise with wireless networks. When I first got mine I got some awful DrayTek Vigor ADSL Router
I don't know how you set yours up, but my vigor 2600g (few months old) works perfectly well with both wired and wireless clients. There are a few bugs like it sometimes reboots, and it doesn't work on anything other than 192.168.x.x apparently (I've not tried changing it, the default subnet works fine for me).
Compare that to a linksys wrt54g I bought last saturday (not for me mind), which decided it would die on wednesday - great quality control there.
I find any wireless problems I have are to do with windows, that likes to lose wireless settings, or would need the wireless card to be disabled/enabled before it wants to connect.
Posting this from a PC connected to a wonderful vigor 2600g running 2.5.7rc13.
Which randomly reboots and has very limited IP settings, you mean?moo wrote:a wonderful vigor 2600g running 2.5.7rc13.
Beh, who am I to talk? I uploaded the wrong firmware file to my router and killed it - before I even got adsl. Thank god for my trusty laptop and speedtouch to back things up while I get it sorted out.
Knight knight
The rebooting is odd - I get it, other people don't.
And as for the IP problem, I haven't seen anyone else moan about it, only 1 - I don't know if it does break if you dare change it from 192.168.x.x as i've never had to try it
EDIT: it turns out that the IP bug was fixed ages ago, so it's only the sometimes-rebooting that exists
EDIT 2: it does work perfectly well, changed to 10.0.0.0.
And as for the IP problem, I haven't seen anyone else moan about it, only 1 - I don't know if it does break if you dare change it from 192.168.x.x as i've never had to try it
EDIT: it turns out that the IP bug was fixed ages ago, so it's only the sometimes-rebooting that exists
EDIT 2: it does work perfectly well, changed to 10.0.0.0.