My client PC will NOT browse the Internet

Sometimes, even the slightest misconfiguration of the TCP/IP settings, DNS, or other network component can prevent RideWay from working properly. If you have followed the set-up instructions in the Help Files of RideWay, and you get one of the following messages on your client PC:

• "Connection to server reset"
• "Cannot Resolve DNS Entry"

We're here to fully assist you:

• I want DGL to review my configurations
• I want to use DGL's exact, recommended step-by-step configurations

How do you configure for use with a cable modem, DirecPC, or ADSL Modem

RideWay is an ideal solution for optimizing your cable modem, DirecPC, or ADSL modem access investment. Configuring for one of these connections for use with RideWay varies slightly from standard configuration with a dial-up modem connection. For your convenience, we have provided comprehensive configuration instructions for each:

• Cable Modem Configurations
• DirecPC Configurations
• ADSL Modem Configurations

Why do I have to use IP Addresses that begin with "192.168.1.."?

In most cases, RideWay is in use as a private or an unregistered network. To maximize performance of RideWay and to prevent an IP on your network from conflicting with a "real" or registered IP address elsewhere on the Internet, use one of these types of addresse schemes when configuring TCP/IP for your network:

• Class A range: 10.x.x.x
• Class B range: 172.16.0.0-172.31.0.0
• Class C range: 192.168.1.x-192.168.254.x

A more concrete example: You have 5 networked PCs and wish to assign private IP addresses to run RideWay, a user would assign these addresses to the network cards ("NIC card") of each PC as follows:



• Server PC running RideWay: 192.168.1.1
• Client PC: 192.168.1.2
• Client PC: 192.168.1.3
• Client PC: 192.168.1.4
• Client PC: 192.168.1.5

Return To Top