Can't access Belkin F5D8230-4 admin page after setting up as access point

[Wifisguy]

I successfully set up my old Belkin Pre-N wireless router as an access point for my 2Wire 3800HGV-B Modem. Now I need to access the Belkin's admin settings to set up WEP.

I used the instructions on page 54 of the Belkin manual found here. In doing so, I assigned the router an IP address within the 2Wire's range and Subnet mask as instructed.

But now I can't access the Belkin admin settings at the assigned IP address as I should. I checked the LAN info on the 2Wire, where the Belkin shows up at a different IP address via DHCP. I attempted to access the Belkin using that DHCP address, but no dice.

Any suggestions on how to resolve this? Much thanks for any thoughts you can offer.

 

[kanewolf]

Start with a FACTORY reset of the Belkin. That will reset it to a router. Connect your PC to a LAN port on the Belkin and connect the 2Wire to the WAN port. You should have normal access. You will need to know some things from the ADMIN page of the 2Wire. You need to assign the Belkin an address that is same first three numbers as the router, but not in the DHCP range of the router.
WEP is NOT recommended for wireless encryption. That router supports WPA which is more secure than WEP.

 

[Wifisguy]

That seems to fly in the face of the instructions, but I'll try it out. Thanks. (BTW, I did mean WPA…too many acronyms in modern life.)

 

[kanewolf]

I looked at the Belkin manual, when you put it into AP mode it disables the NAT and DHCP of the device. That means that the DHCP function is then handled by the 2 wire device. You need to be a static IP address in the same subnet as the DHCP server. You MAY (not clear from the document) need to move the cable from the WAN port to one of the LAN ports on the Belkin as part of the transition to AP.

 

[Wifisguy]

I looked at the Belkin manual, when you put it into AP mode it disables the NAT and DHCP of the device. That means that the DHCP function is then handled by the 2 wire device. You need to be a static IP address in the same subnet as the DHCP server. You MAY (not clear from the document) need to move the cable from the WAN port to one of the LAN ports on the Belkin as part of the transition to AP.

Thanks for your help kanewolf. Actually, your initial suggestions of 8/27 are what solved my issue, though I didn't get to applying them for some weeks afterward. I've been meaning to let you know but never found the time until this email popped up while I'm on holiday. As you mentioned, the key was assigning a static IP address in the router's subnet, but outside the its DHCP address range. It actually makes sense, now that I understand it. Thanks again!