NTL Modem - Hub - Router / Direct

[jrpmedia]

I have an NTL 10Mb Buisiness connection with 5 IP addresses.

I have the NTL Modem connected to the Netgear FS608 v3 10/100 Hub on Port 1

Port 2 on the Netgear FS608 is connected to a 3COM16 Port Hub on Port 4
Port 3 on the Netgear FS608 is connected to Netgear WGT834Tv3 Routers DSL port

Ports 6,7,8,9 on the 3COM16 Port Hub is connect to 4 Mac/PC's
Ports 2,3 on the Netgear WGT834Tv3 Router are attached to 2 Mac/PC's
Wireless on the Netgear WGT834Tv3 Router works fine

All Mac/PC's can connect to browse the WWW, get mail, see the fixed IP's.
I can register the Netgear WGT834Tv3 Router for a fixed IP O.K.
I can register 2 of the Mac/PC's on the 3COM Hub to have fixed IPs O.K.

I just cannot get the Mac/PC's on the Netgear WGT834Tv3 Router to see the Mac/PC's on the Netgear FS608 -- 3COM 16 Port Hub.

I'm using manual IP's for internal of 192.168.1.x

I'm stumped now. It's almost perfect but for local network sharing/networking.

[MovedGoalPosts]

I'd suspect you actually need to connect the modem to the router, and then the various hubs or switches to the network ports on the router.

[jrpmedia]

Nope, because then the router will take an IP using it's Mac addres with NTL and the other devices will not be able to get a fixed IP as they are behind the routers Mac address.

[MovedGoalPosts]

hmmm,

If it's anything like my office's setup (ADSL) I'd have thought your computer network workstations should generally be on the LAN side of the router, adding more switches on the LAN side to expand as necesary, with the modem, on the WAN side of the router.

You'd allocate a fixed IP from the external address to the router, and can then have your internal 192.168 range for the workstations. If you need to the router should be able to have a separate PC (s) in a DMZ, or issued with fixed external IPs.

With your setup, I can't see how the router would allow stuff that is on it's WAN side to see stuff that is on it's LAN side especially if they both are in the same IP range

[jrpmedia]

Yes, you are right, but with NTL and DSL the IP's are only given to PC's directly attached to the Modem (via. a Hub in this instance to get 5 PC's connected [1 Router Mac Address and 4 Computers with Mac Addresses])

If I want 40 PC's attached I need to put 36 of then onto the Router, 4 onto the Hub, QED.

I asked NTL if I could use a Netgear FSV338 Firewall but NTL said No, they work on Mac Addresses only, and this would still be just one Mac Address.

So apart from the 'routing' between the Router and the Hub for 192.168.1.x addresses I'm almost there.

I did try a loop-back by adding an additlonal RJ45 from the 4 Port Hub to the Router and it worked, for 2 minutes, then it all went bonkers!!

How can I get the PC's on the router to see the PC's on the hub internally on 192.168.1.x They're all connect by wires, shouldn't be a problem ?.....

[sprattgraham]

You should have your Modem connected to the WGT834T WAN Port then have your switches connected to the ports on your Router.

You can’t put your Local Network on the WAN Port.

Most routers allow more than one WAN IP and forward WAN IP to a Local IP.

[OldGeezer]

If your router doesn't handle multiple WAN IPs (mine doesn't), and you want your Macs/PCs to be visible both via WAN and LAN, then they need 2 network cards each, one for the WAN address (via hub to modem), and one for LAN address (to LAN side of router, possibly via another hub/switch).

[jrpmedia]

Thanks 'OldGeezer' I came o the same conclusion.

I must chat with NTL/Virgin 'business' support again tomorrow (they are very good) and grill them about Multi-WAN IP routers o what I am trying to do ... I'll be back...

[Matth]

Getting my head around this...

You have a service with 5 available fixed IPs, a hub/switch feeding 4 (fixed IP) systems and a router, and the remaining systems inside the router boundary.

To the systems inside the router boundary, those outside are the same as the Internet - simplest answer may be for them to have two network cards, if possible, one outward facing (fixed IP) and one inward facing (on the router) - may need some path metric tweaks, to make sure things go in the right direction.

Depending on the protocols, some things may be NAT-able.

If you were really clever with Linux stuff, maybe you could make a multi-address forwading Linux router

[jrpmedia]

Thanks, yes I think it com es down to 'physical' wire connections.

Though osx can run multiple bridges and IPs on one ether net port it (no system) cannot 'remote' bridge unless there is a physical wired connection....