Monday, October 09, 2006

routing

SCh (MTech) had asked me some days back two routing related problems:

1. A multi-homed Win2K machine was being used as a router between two subnets. Machines on either sides could ping each other, but Windows shares were not accessible - solution?

2. A hardware router, "Broadband router" from DLink, with the requirement again of machines on either side to be able to use Windows shares on both subnets.

I'd collected some links:

for win2000 routing: http://www.duxcw.com/dcforum/DCForumID2/2003.html
An example of a hardware router: http://corz.org/comms/hardware/router/bt.voyager.205_router.recipes.php
For effective routing, make the router the default gateway: http://www.microsoft.com/technet/archive/winntas/deploy/implip.mspx?mfr=true

Told SCh I couldn't help with the DLink router without knowing the exact model number. The other problem he solved himself - the Win2K machine had a firewall running, which was blocking Windows Networking.

Edit: (added 20th Nov, from a mail I sent him on 11th Nov)
Googling 'DLINK DI-524 manual' gives the Dlink page with the manual as well as
a simulation of the web-based configuration wizard. It appears that with this
router, what you want to do - allow machines on the other side of the network
to access windows shares on the inside - is not possible directly. The manual
clearly states that this router only works with NAT - no direct modification
of router tables is possible.

You can use the Virtual Server setting in the router and allow machines
outside to connect to machines inside, but configuring it for more than one
system would be difficult for Windows shares.

No comments:

Post a Comment