› Forums › Network Management › ZeroShell › laptops not taking automatic ip address !
- This topic is empty.
-
AuthorPosts
-
April 17, 2008 at 12:46 pm #40996
billybolly
MemberDear friends
I have set up the internal network with zeroshell. I have an Access Point at 192.168.0.227 with dhcp disabled. The wirewless clients should normally take automatically ip address from the dhcp server of zeroshell BUT THEY ARE NOT !! Why?
When I give manualy to the laptop an ip address like 192.168.0.230, and the gateway of zeroshell 192.168.0.75, the connection is made and I can see the login page.
Any ideas what is going wrong?
April 17, 2008 at 8:04 pm #46395imported_fulvio
ParticipantVery strange. To understand if Zeroshell is missconfigured you should try to connect the laptop using the ethernet port with a RJ45 cross cable or with a fastethernet switch. If the dhcp works fine, then you have to modify the configuration of the wifi access point to avoid that the broadcast dhcp request are dropped.
Regards
FulvioApril 26, 2008 at 1:51 pm #46396billybolly
MemberThe laptop is taking automatically ip when using the ethernet port with RJ45.
The Access point is Netgear WG602 v3. I tryied every possible setting of the access point and it drops dhcp requests !Is it the Netgear AP that causes the problem?
April 29, 2008 at 2:36 am #46397Hubcraft101
MemberWould try disabling any wireless security first. If you have everything on the same network then the DHCP broadcasts can reach every device.
The only difference between this setup working and not working is whether you are plugged in wireless or wired. I’ve seen where if you enter in the wrong WEP key a windows client will say “Limited or no connectivity” and give you a 169.x.x.x address.
April 29, 2008 at 8:40 am #46398billybolly
MemberI am not using any security.
Thanks for the answer.
Yesterday we had an electricity blackout and when it restarted everything worked fine ! Zeroshell, AP, wireless and wired network !
How can you explain this?April 29, 2008 at 8:19 pm #46399Hubcraft101
MemberIn this day and age, rebooting fixes most problems. Anytime you call into a support center for troubleshooting a device 9/10 times they ask you to reboot the device first. When you build a multi-vendor network just as you have in your situation, they don’t always play nice together and rebooting them sometimes gets them to sync up and cooperate. I’m sure there is a specific technical reason why your setup wasn’t working temporarily.
-
AuthorPosts
- You must be logged in to reply to this topic.