Products & Services 
Internet Access Email & Dial Up Dial up FAQ
Part 1: Dial-up Accounts
1.2 - Who is eligible for a RINET dial-up account?
1.3 - How much does it cost?
1.4 - How do I sign up?
Part 2: Getting Started
2.2 - What phone number should I use to connect?
2.3 - How do I configure my computer to use dial-up networking?
Part 3: Troubleshooting
3.2.2 - Why do I get an error message that there is no dial tone?
3.3.2 - The modem dials and you hear the modem on the other end answer, but eventually the connection drops and you receive an error message.
3.4.2 - I enter my username and password, but I get an access denied error message.
3.4.3 - If I make a mistake typing my username or password into the terminal server, how do I correct the error? The backspace key doesn't work.
3.4.4 - In Windows, after I enter my username and password and the ppp command, I see a bunch of characters on the screen, but the connection never completes.
3.5.2 - Using my dial-up script, the phone dials and connects and the script window starts up, but then it stops part way through.
3.5.3 - When I use a dial-up script, the phone dials and connects, but after seeing the Verifying user name and password message, the connection doesn't complete and eventually times out with an error message.
3.6.2 - Why does my session disconnect, followed immediately by the phone ringing?
3.6.3 - Why does my session disconnect after I check my e-mail?
Part 4: Miscellaneous
4.2 How can I control Unsolicited Bulk E-mail [UBE] or SPAM that comes to my account?
4.3 Does RINET support V.92 modem technology (esp. the modem on hold feature)?
4.4 I can no longer send RINET e-mail using my COX Home Internet connection. What do I need to do?
Part 1: Dial-up Accounts
1.1 - What can I do with a RINET dial-up account? A RINET dial-up account allows you to access the Internet, electronic mail, and telnet using a computer equipped with a modem. For more information, link to Getting Started with RINET
1.2 -Who is eligible for a RINET dial-up account? 1.3 - How much does it cost? 1.4 - How do I sign up? The answers to these questions may be found in RINET Service Description and Fees.
Part 2: Getting Started
2.1 - What do I need to get started using my dial-up account? After signing up for an account, you will need the following things:
- A computer running Windows 95 or better or Macintosh OS 8 or better
- A 14.4Kb or greater modem (at least a 28.8Kb modem is highly recommended)and telephone cable
- A standard analog telephone line
2.2 - What phone number should I use to connect? All RINET users should use the single dial-up number 455-0268. This number is toll-free from anywhere in Rhode Island. Note: Dialing this number from outside of Rhode Island will result in telephone charges.
2.3 - How do I configure my computer to use dial-up networking? Please refer to the RINET dial-up networking instructions for your version of Windows or Macintosh OS Dialup Instructions
Part 3: Troubleshooting
3.1.1 - What to try first if you have problems. If you are having trouble getting your RINET dial-up connection to work, first go back to the RINET dial-up networking instructions and make sure you have followed them exactly. If you are still having problems, continue on for solutions to some common problems. Before looking below for more specific hints, check the following:- Is your modem turned on (if it's an external modem)?
- Is your modem connected to the phone line properly? Most modems have two jacks, labeled LINE (or with a picture of a telephone wall jack) and PHONE (or a picture of a telephone handset). Make sure one end of the telephone cable is plugged into the LINE jack on the modem, and the other end is plugged into the phone line.
- Are you connecting to an analog telephone line? Standard modems do notwork with digital telephone lines (and in some cases, a digital line can damage an analog modem). The presence of "fancy" phones with display panels usually indicates a digital telephone system. Otherwise, you can plug in a standard analog telephone or use a special testing device to determine whether the phone line is analog or digital.
- Is your telephone line working properly? Plug a telephone handset into the line to see if you get a dial tone.
- Is your telephone cable working properly? Test the phone cable you are using with a telephone to make sure it is working correctly.
3.2 Modem dialing problems
3.2.1 - When I try to connect, my modem won't even dial. What is wrong? First, make sure that your modem really isn't dialing. Most modems have a built in speaker or connect to the computer's sound card so you can hear them dial and connect. However, if the sound is disconnected or turned off, you may not be able to easily tell if the modem is trying to dial. Pick up a telephone handset on the same line or wait for your computer to give an error message to see if the modem is really dialing or not. If the modem is really not dialing, the most likely cause is that the modem drivers are not installed or not configured properly on your computer. Troubleshooting modem driver problems is very specific to the particular computer involved, so if you are having problems you should consult yourlocal support person.3.2.2 - Why do I get an error message that there is no dial tone? If you have a telephone on the same line, first make sure that you actually have a dial tone on the line. Then, make sure that the phone cable is connected securely to the phone jack and to the "line" port on the modem. You can also get this message if you have a voice mail system that uses a special dial tone to indicate that you have a message waiting. If this is the case, you will need to check your voice mail to clear the special dial tone.
3.3.1 - The phone dials, but I get a busy signal. All the modems are in use. Try again in a few minutes.
3.3.2 - The modem dials and you hear the modemon the other end answer, but eventually the connection drops and you receive an error message. If you get as far as seeing the terminal server window, skip to the next section. Otherwise, consult the RINET dial-up networking documentation to make sure your modem properties are set correctly (8 data bits, 1 stop bit, no parity). If you are using Windows, you may not have set the Bring up terminal window after dialing option. Refer to the RINET dial-up networking documentation for your version of Windows. If all else fails, go back and create a new dial-up connection from scratch, carefully following the step by step instructions in the documentation.
3.4 Terminal server problems
3.4.1 - I can enter my username, but my password doesn't show up when I type it. That is a security feature so no one can see your password when you enter it.3.4.2 - I enter my username and password, but I get an access denied error message. Note: The RINET terminal servers no longer accept Brown or URI userids. You must use your RINET account name and password. Make sure you are entering your username and password EXACTLY, including upper and lower case letters. Do not enter any spaces in your username or password.
3.4.3 - If I make a mistake typing my username or password into the terminal server, how do I correct the error? The backspace key doesn't work. Just hit the enter key, and you'll be given another chance to enter your username and password. After three tries, you'll be disconnected and will have to dial up again.
3.4.4 - In Windows, after I enter my username and password and the ppp command, I see a bunch of characters on the screen, but the connection never completes. You must press the Continue or Done button (depending on your version of Windows) at the bottom of the terminal server window.
Note: This section pertains to dial-up script problems using Windows. If you are using a Mac and having problems with your script, go back to the dial-up instructions and start from scratch to create a new script. If you are having problems with your dial-up script, first make sure that you are able to connect successfully using the manual method. This will ensure you are not experiencing another problem.
3.5.1 - When I use a dial-up script, the phone dials and connects, but then the terminal server window pops up and prompts me to enter a username. You didn't turn off the Bring up terminal server window after dialing option. Refer to the RINET dial-up networking documentation.
3.5.2 - Using my dial-up script, the phone dials and connects and the script window starts up, but then it stops part way through. You probably made an error when typing in the dial-up script. Go back to the documentation and make sure the script is entered exactly as printed (except where your username and password are substituted). In particular, make sure there are no spaces within any of the quotation marks. Also, make sure to include ^M after your USERID and PASSWORD in the script. (The caret character (^) is located above the 6 on your keyboard).
3.5.3 - When I use a dial-up script, the phone dials and connects, but after seeing the Verifying user name and password message, the connection doesn't complete and eventually times out with an error message. Make sure when typing in the script, you replace USERID with your RINET username, and PASSWORD with your password. You must enter them exactly, with no spaces and including upper and lower case letters.
3.6.1 - Why did my dial-up connection disconnect suddenly? There are many potential causes for a disconnected session. Some examples include static on the line, a problem with the terminal server or modem pool, or someone picking up a phone extension on the same line while the phone is in use. Occasional disconnects are common. If this happens, reconnect and resume your session.
If you have frequent disconnects, you may want to contact the telephone company to have your line tested. If you suspect a problem on RINET's end (e.g., your modem works fine with other services, but disconnects frequently when connected through RINET), please contact your local Email & Dialup Support.
3.6.2 - Why does my session disconnect, followed immediately by the phone ringing? If you have call waiting, an incoming call will disconnect your session.You can include the code to disable call waiting (typically *70) under the modem dial properties to ensure your connection does not get disruptedby an incoming call.
3.6.3 - Why does my session disconnect after I check my e-mail? You may have your e-mail client set to automatically disconnect after checking for mail. Look in the program properties for such a setting and disable it.
4.1 - Why doesn't my 56Kb modem connect at 56Kb? FCC regulations limit the power output allowed for devices that connectto the telephone network, so you are unable to fully achieve speeds of 56Kb. In addition, there are other factors that can decrease the actual through put, including as the level of noise on the line. Also, there are different standards for 56Kb modems, so if the modems on both ends don't use the same standard, the highest connection speed won't be possible. Note that depending on the modem driver that is loaded on your computer, you may not get an accurate report of the actual speed at the time of your connection. If you consistently get very slow connections or have frequent disconnects, you may want to contact your telephone company to have the line tested.
4.2 - How can I control Unsolicited Bulk E-mail [UBE] or SPAM that comes to my account? Effective January 13, 2003, RINET will tag the subject line of suspected SPAM email messages with the identifier [UBE] (Unsolicited Bulk Email). End users may delete individual messages using this tag as a guide and/or set filters on their email client to file suspected emails to a user specified “junk email” directory. See the SPAM Filtering Page for further information.
4.3 - Does RINET support V.92 modem technology (esp. the modem on hold feature)? Currently RINET does not support V.92. The V.92 modem standard is not yet finalized or ratified. If, and when, the standard is embraced by the majority of modem manufacturers, RINET will pursue upgrading its modem banks to support V.92.
4.4 - I can no longer send RINET e-mail using my COX Home Internet connection. What do I need to do? Cox Home Internet Service no longer allows mail to be "relayed". This means that when you connect over your Cox connection, you can receive but not send RINET e-mail (or any other non-Cox e-mail). The remedy to this situation is to make a small change in your e-mail client to accomodate the Cox change in policy.
To fix the problem, go into your mail client (e.g., Microsoft Outlook, Netscape Mail, etc.) and change the configuration for "Outgoing or SMTP Mail Server" to "smtp.east.cox.net" (it will now say "ride.ri.net").
