Obi100 No longer working with TWC after switching modems
Bubba:
Hi Felix,
I had already turned off wireless on the modem and turned the router into the Access Point in order to get all my other devices working. I just don't know why my Obi device isn't working. It's got two solid green lights and was able to update it's firmware. I can see it connected to my modem through the administrator portal.
Maybe it's time to suck it up and buy another modem...
MikeHObi:
giqcass trying to have the d-link act independent so it gets it's own connection to the net, and then your SBG900 has it's own connection.
That is certainly something to try. By sticking the d-link in the SBG900's DMZ, all data through the port to the D-Link should flow straight through and not touch the firewall or nat routing inside the SBG900.
Usually a home network has netmask of 255.255.255.0 which means all ip addresses on that network must have the same 3 values, with only the last changing. your two routers should have the same IP network, and the SBG900 network cable should be plugged into a standard switch port on the d-link, not the WAN port. (Wan ports are tied to routing. If both devices are on the same network you need switching, not routing, typically routing is only needed between the cable companies network and your home network, thus is already handled by the SBG900).
giqcass:
Log into your Obi and make sure it is using 192.168.0.101 as the gateway address. Also make sure it is either finding a DNS server or assign the ones i listed above.
The setup I was suggesting was intended to be used with the devices on different subnets to avoid conflicts. DHCP on or off is no problem. I also intended the WAN port on the Dlink be connected to the LAN port on the modem. It can be done as MikeHobi suggested LAN to LAN but then both devices should be on the same subnet with Dlink DHCP off.
I have set up my networks in both ways and for my equipment LAN to WAN on different subnets gave better results.
If I were a betting man I would say the obi is using a self assigned APIPA or AVAHI style address right now.
Bubba:
Hi guys,
Thanks for your continued contribution to my problem solving issue. I wanted to let you know that I bit the bullet and bought a stand alone modem, the SB6141, and should have that shortly. By eliminating one issue (the two wireless devices fighting for each other), I hope to have my Obi working again.
But while I'm waiting for that modem to arrive next week, I tried some of the suggestions you guys said below (but still unsuccessful).
1) I went into the Obi expert settings and changed my gateway address to 192.168.0.101.
2) The Obi is pulling a DNS server from my ISP automatically.
3) DHCP is "on" on my modem's WAN settings page.
4) NAT is "enabled" on my modem's LAN settings page.
5) My router's WAN and LAN MAC addresses are both in the DMZ of the modem.
6) The subnet mask for Modem, Router and Obi are all set to 255.255.255.0
7) The modem is plugged into one of the four LAN ports on the DLINK router.
8) DHCP is "off" on my router's WAN settings.
9) Firewalls are off on both the router and modem.
10) The OBI's MAC address is in the DMZ of the modem.
Still, I got nothing on the Obi, other than being able to see the device now on my "System Status" page (something that was not visible until I tried giqcass's suggestion of putting the Obi's gateway address as 192.168.0.101). Some progress, I think...
giqcass:
I still suspect the OBi is not getting a correct IP address. The IP address of the Obi should be 192.168.0.xxx
with the xxx being a number between 1 and 254. You are outside the subnet of the DHCP server and therefore it can not hear the service broadcast. Assign the Obi a manual IP address something like 192.168.0.133 that won't be in conflict with addresses already assigned to other devices. If it still does not work consider also using the open DNS servers above in place of the DNS servers you have.
Navigation
[0] Message Index
[*] Previous page