[G-Stress]

Anybody familiar with the Motorola SBG900? I had my first experience with one of these just the other day. According to the modem it serves as a modem and a wireless gateway with built in DHCP, Firewall, etc.

The problem I'm having with it is running 1 wired machine and 1 wireless machine off of it. It clearly says on the back of the box it is set for a Class C network with a supported 253 devices at once.

As far as the menu options go the DHCP section is set to start at 192.168.0.10 with a maximum of 245 clients and this number for some reason cannot be changed. I tried to change it to 50 and a few other smaller numbers and it said it was invalid. ]

What happens is there is one desktop machine hardwired and 1 wireless machine now with them both connected to the modem after a clean power cycle which ever one grabs an ip first works fine. The other gets 169.254.x.x or it will get a proper ip but will not have any rout past the modem.

After looking through the menu options with both machines connected I noticed that the WAN ip for some reason changes to a 192.168.0.11.

This is a customer's setup I was working on. The desktop is a standard use pc and the lap-top is a work machine that needs VPN access.

Just thought I'd see if anyone else has had any experience with this modem/gateway.

[JohnWill]

Nope, but if it's connected correctly, I can't imagine it not allowing two connections. I'd have to see the IPCONFIG /ALL results from the two machines to know much more.

[G-Stress]

hmmm, im goin back tomorrow to check it out more and bringing my lap-top as well. What will happen is say the desktop gets online first then we try to connect the lap-top it will get the APIPA address then if you repair the stack, etc. and reboot it will usually connect fine with route, but then the desktop will no longer have route.

The desktop will hold the IP it had before the laptop was able to route it just won't route. Also the WAN IP then will somehow be assigned an address by the modems internal DHCP server... weird...

[JohnWill]

Like I said, we need to see the IPCONFIG. The symptoms suggest you don't have the NAT layer in the mix and you're getting the only public IP address of the account on the first machine.