SatSig topic:

Connecting Tooway Modem via Network Router

(Read 31163 times)

Nov 9^th, 2008 at 6:40pm

I have a D-LInk DIR-655 wireless router.
As usual, it has an IP address of 192.168.0.1.
Connecting two or three pc's to the network works fine (using the LAN ports on the router) - one of the PC's is a laptop, connected via the wifi.
Everything works normally.

But I cannot get the network to see the Tooway modem, and therefore the internet.

I've tried connecting the modem via a LAN port and the WAN port (on the Router), but with no success.
All PC's are set up for automatic IP address and DHCP is enabled.

If the modem is connected directly to a PC, excluding the network in other words, it works perfectly.

I feel I must be making a very basic error - can anyone assist and point me in the right direction please?

Cheers
Sean

Nov 9^th, 2008 at 8:48pm

You need to find the operational IP address and subnet of your Tooway modem. It is likely that your service provider has already told you this. e.g. 123.123.123.1 255.255.255.252

This means that you have a network ready at the ethernet port on the Tooway. An example network is called 123.123.123.0 The gateway is 123.123.123.1 You can connect only one PC with 123.123.123.2 You also have a multicast address 123.123.123.3 The .252 inn the subnet mask means that a total of 4 IP addresses exist. (.248 would mean a total of 8 IP addresses, with 5 of them available for PCs)

Read more about https://www.subnet-calculator.com/ This will help your understanding if your Tooway has an IP address not ending in 1 or a mask not ending in 252

Check by connecting a PC direct to the Tooway modem. The PC needs to have the same subnet mask as the modem e.g 255.255.255.252, the gateway is the Tooway modem IP address e.g. 123.123.123.1 and the IP address of the PC needs to be different, eg 123.123.123.2

Use two DNS servers as told to you by your service provider.

Open a DOS command prompt window and type ipconfig /all Write down the information.

Having understood the modem connection and successfully accessed the internet, connect your router WAN port to the modem. Your PC needs to be connected to the router via one of the LAN ports. The IP address of your PC now needs changing to match the LAN network which you invent. You have already invented your LAN, presumably name=192.168.0.0 Router gateway 192.168.0.1 You are using DHCP bu you could allocate each PC in the range 192.168.0.2 upwards. The number of PCs you may connect will be 253 if the you use the default subnet mask 255.255.255.0

Your router manual is here https://static.compusa.com/pdf/D-link-DIR-655-Manual.pdf (note 7.9 Mbytes file size)

If someone reading this has a Tooway modem, please add your sugegstions and say if I am right or wrong.

Best Regards, Eric

Nov 21^st, 2008 at 12:05am

Thanks for the reply Eric.

This has now been solved.

To cut a long story short:
I changed the ADSL router for a Cable/DSL one - the D-LINK DIR 635.

It only works with a Crossover cable.

Then it was simple - plug the Tooway modem into the Internet socket and off it went, no need for any configuration at all.

The Wifi LAN is brilliant on this router, being the Draft n version. It connects at 130 Mbps and even works all the way down the garden!

Nov 21^st, 2008 at 11:02am

Sean, glad to know that solved the problem. For Tooway clients thinking of using wireless, please invest in a cable/DSL router opposed to ADSL.

Nov 23^rd, 2008 at 6:50pm

I've installed quite a few Tooway systems in Southern Spain and our customers usually require a wireless network in their home as well.

We have been using the SMC Barricade SMCWBR14-G2 Cable/DSL router and it works like a dream - very reasonably priced too.

One thing I noticed early on was that you can't "hotswap" the router onto the Tooway modem if you have already connected a PC previously - you have to power off the modem, then plug in the router and then power on again. After this, you can connect as many wired and wireless devices as you like, with the router doing all of the DHCP work with a 192.168.2.x subnet.