Two router network

[Mark Haney]

Keith Clark wrote:
> On Wed, 2009-07-29 at 13:44 -0400, Rashkae wrote:
>> Keith Clark wrote:
>>
>>> I don't seem to be able to find my Belkin Router now though.
>>>
>> This is normal, since you aren't using the WAN port anymore, the Belkin
>> router is no longer getting the 192.168.0.4 address (which was being
>> assigned by the D-Link.)
>>
>> There are two ways to go about this:
>>
>> 1. Just leave it as is.  If you need to administer the Belkin router,
>> manually assign a static IP in the 192.168.2.x range on a pc temporarily
>>
>> Example: ifconfig eth0 192.168.2.5 (You might have to stop network
>> manager for this to work from a Ubuntu station)
>>
>> You would then access the Belkin by using web browser to go to 192.168.2.1
>>
>> If you want, you can change the IP address of the Belkin Router to
>> something in the 192.168.0.x range to make access easier in the future.
>>  However, you much choose a value for x that is *not* within the
>> D-link's DHCP range.  You'll have to verify the config of the D-link to
>> see what it's current DHCP range is.
>>
>> Either way, I would suggest putting a label on the Belkin with it's IP
>> address, so that any future technician will know how to get to it
>> without using the reset button, which must now never be pressed.
>> (Hitting reset on the Belkin will re-enable the DHCP server, which will
>> royally mess up your networking until someone is able to sort it out.)
>>
>>
> 
> Perfect.  I will leave as is, label it with 192.168.2.1 for my own
> memory, and if I need to service it, I'll just change one of my
> computers over to 192.168.2.x as suggested.
> 
> I appreciate the help I got from everyone  and it is now working very,
> very well!  I even understand routers a bit better now.
> 

I'm a little late to this party, but no one really ever touched on the
core of the issue.  That the system couldn't 'browse' the server via
Nautilus.  I suppose I'm old school here, but the problem was worked
around and not addressed.

The reason you couldn't browse could have been from a couple of factors.
 My guess is that the firewalls on both routers were blocking the
NetBIOS ports (137 and 139) which are required for browsing Windows
resources.

At least, that has always fixed that problem for me.


-- 
Interdum feror cupidine partium magnarum Europae vincendarum

Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415