in a simple small office network, auto IP detect won't get on network

[Maximus96]

we got a small office setup using 192.168.1.XXX IP numbers and 255.255.255.0 subnet. we got a dlink access point and linksys 4 port router. every now and then something would act up and the computers on wireless will not be able to see the rest of the network of the wired computers. the wireless would have a strange IP thats totally different and a subnet of 255.0.0.0 when i force it to go onto the network by assigning an IP in the correct range and change teh subnet back, it'll see the network but no longer get on the internet. when i let it automatically get an IP, it would be in the odd range again but will see the internet but not the network. any ideas? please help.

 

[asm0deus]

we had this problem at our old office, i think the dhcp server wasnt working right. I couldnt do much about it so I wound up just assigning them manually. I'm supposed to go over there pretty soon to fix one of these

 

[MrControversial]

I used to have this problem before switching to XP Service Pack 2.

 

[vi edit]

Welcome to the wireless age

Seriously...wireless is still in it's infant stages and has a lot of kinks still in it.

About the only thing you really can do is just do a release and renew on IP and see if it will grab a new one.

Are you using encryption of any sort? Sometimes the encryption settings can get mucked up and cause it not to validate and grab an IP from the router.