Re: Access limitations(?), and moving to a simple LAN

Haven't seen any more on here from Jeremy lately, so I'm just posting an
update on the progress we made yesterday afternoon:

Broadband:
Telewest replaced the cable modem. It worked fine when I plugged it in
directly to my Windows laptop. IP address was assigned over DHCP, so able to
connect to Internet straight away, browse the web and read emails. Less
than 20 mins till Norton popped up a message saying the first worm attempt
had been blocked ... ;-)

However when we tried plugging the cable modem into Jeremy's RPC (RISC OS
3.7), which doesn't support DHCP, we had to manually assign an IP address of
the form 192.168.100.x (the modem was 192.168.100.1, which we entered as the
gateway address) and as we didn't know the DNS server addresses for
blueyonder, weren't able to progress further. Searched the blueyonder
support pages and tried a couple of Google searches but no luck.

Network switch and Kyocera printer:
Taken out of the system for the time being, to keep things simple.

Router (Draytek Vigor 2300):
Using my Windows laptop, downloaded latest firmware (v 2.5.2) and installed
it on the router.

Was able to communicate with the router (192.168.1.1) via its embedded Web
server, which correctly showed the MAC addresses of all connected devices.
The problem was I really didn't understand all the options on the Draytek
router's setup pages - compared with my old setup at home (a belkin wireless
router plugged into an rcomp adsl modem/router) it seemed so much harder to
configure.

For starters, we couldn't access the cable modem at all through its
192.168.100.1 address when it was attached to the WAN port on the router was
present. There didn't seem to be an obvious place in the router setup to
enter the WAN address, so we tried changing the router's IP address range
from 192.168.1.x to 192.168.100.x to match the cable modem, but that was a
bad mistake as we completely lost the ability to communicate with the router
and had to do a factory reset to get it back to 192.168.1.x

At that stage we decided to call it a day...

Next steps:
Plug Iyonix directly into cable modem, to see if DHCP in RISC OS 5 works
Find out DNS server addresses for blueyonder so can start web browsing from
the RPC
Get to grips with Vigor router setup pages
Try plugging Iyonix, RPC, and Kyocera printer into the router, assigning
them addresses of the form 192.168.1.x and seeing if they can still ping one
another and use ShareFS

I'm leaving Edinburgh soon, but I guess Jeremy will continue to post as
further progress is made. Next time I'm back I hope to see a fully
functioning network with broadband access on both iyonix and the 2 RPCs,
complete with dial-up on one RPC as fallback, and printing to the networked
Kyocera enabled from all machines ;-) Should be entirely possible!

Cheers
--
Govind Kharbanda
.

Relevant Pages

  • RE: Questions about 192.168
    ... X.X.X.255 is a broadcast address normally. ... If yours is old, it may not be a router, but lets keep it ... list to drop pings and other types of suspect traffic.) ... router or cable modem can do if they are untrained, such as run W2K and not ...
    (Security-Basics)
  • Re: Problem getting VPN to work with a Netgear FR314 router
    ... my LAN and the corporate network. ... range of addresses to the 172.16.xxx.xxx range on the router. ... the corporate firewall and was able to do everything I was hoping for. ... cable modem / firewall / to communicate and thought that perhaps their ...
    (comp.security.firewalls)
  • Re: Trying to Get My Home Network Back Up
    ... connected to the Internet port and the 3 PC cables connected to slots one two ... The device is a Linksys Broadband Firewall Router with 4-Port switch and VPN ... > If the device that connects to your cable modem is a router, ...
    (microsoft.public.windowsxp.network_web)
  • Re: Networking to PREVENT connectivity!
    ... > or Cable modem broadband will be available for at least 10 years. ... > Router", for the three users there, and one to our long range bridge. ... Everyone WANTS to connect to everyone on their network. ... > addressing tree would be necessary for the "WAN router" to act as NAT ...
    (comp.dcom.lans.ethernet)
  • Re: QOS VOIP - Hosted IP PBX Provider
    ... CCIE R&S (in progress), CCIE Voice ... configure QoS on the router, as well as on your switches, as well as ... In general, you must configure QoS on all your devices - the router, LAN ...
    (comp.dcom.sys.cisco)