Frequently Asked Questions

1. What modem initialization (or init) string should I use?
   
2. What should I do if InJoy will not dial?
   
3. InJoy will not autostart my programs. Why?
   
4. My TCP/IP application can't see my dial up connection. Why?
   
5. Do you have a IP Masquerading check list?
   
6. I'm running IP Masquerading and get an "IP Address table exhausted" error. Why?
   
7. The first time I click on Dial (after a boot) the modem will not respond. It won't even respond to AT in the terminal window. Why?
   
8. How do I connect to the IBM Global Network (IGN also known as Advantis)?
   
9. I find that when the line is busy or for some other reason InJoy doesn't connect on the first attempt the subsequent redial fail. What InJoy does on a redial attempt is dial the phone number then almost immediately disconnects and cycles for another dial attempt.
   
10. Occasionally I get "PPP: Invalid FCS" what is this cryptic message? And what to do to get rid of it?
    
11. I cannot connect to a NT server with CHAP, Why?
    
12. Why do I keep getting this error message from InJoy? PPP:Unknown protocol: 0x200d, PROTOCOL REJECT
    
13. Why do I get this "Unsupported Protocol 80fd"?
    
14. The corporate LAN uses SecurID from Access Control + Encryption. Can I use InJoy
    
15. Are there more questions and answers recorded somewhere?
    

What modem initialization (or init) string should I use?

• Use a string known to work well with your modem, and your ISP. For example if you are upgrading from other Warp Dialers (e.g. DOIP, iLink/2 or the Advantis dialer), open the working dialer and copy its successful string.

• If you are upgrading from another operating system it may be more difficult to learn the strings in use there. Sometimes searching non-executables on the "modem driver disks" shipping with new modems will turn up several good strings to try.

• A user reported it is possible to learn what the win9x/nt dialers are using by using this procedure: From Control Panel --> modems --> properties --> connection --> advanced, set the check box "Record a Log file". Then start a modem connection through the point where the modem has dialed and the other end has responded. Then in the WINDOWS directory, there will be a file named "ModemLog...." with a file extension of ".TXT". The actual name may have the name of the modem as part of the logfile name, i.e., if you have a 56K Plug and Play modem, the name may be "ModemLog 56K Plug&Play.TXT". In that log file you will find the actual modem init strings that were used for the connection.

• You can probably use your modem manual to optimize a partially satisfactory string (whether from the InJoy default, another dialer or operating system).

• Consult the files MODEM.IAK or MODEM.LST installed with Warp. They are usually in the x:\MPTN\ETC or x:\TCPIP\ETC directories. They may contain your brand/model modem, or may give strings for other models which will work with yours.

• The latest version of MODEM.IAK can usually be found at:

  ftp://service.software.ibm.com/ps/products/tcpip/
  fixes/v4.0os2/updatedmodemlist/modem.iak

  NOTE: The URL address should be on one line with no breaks.

• You can search for an appropriate modem init string at:

http://www.in.net/cgi-bin/modemcgi?searchdata=YOURMODEM

where =YOURMODEM should be replaced with:
=hayes
=lasat
=usr
=zoom
and etc

• The technical support folks at many ISPs have lists of suggested modem init strings.

• This FAQ.TXT file contains many strings reported by users to be good for particular modems. You might be lucky if you do a text search of this file using the name of your modem manufacturer.

• Avoid using &W in your string. Search on &W in this file for details.

• Of course there might be someone on the InJoy Mail List using the exact same brand/model modem as you.

This problem can have many causes, and solutions. This check list might offer you some help:
1. Make sure not to use InJoy in a full screen session. Some COM drivers have problems with that.

2. Can other programs access your modem at the selected speed?

3. Can you give AT commands to your modem in the 'Terminal Mode Window'?

4. Did you put in your phone number?

5. Are the initialization strings valid for your modem? InJoy expects text replies from the modem, e.g. 'OK', 'NO CARRIER'.

6. Do you experience strange hangs when accessing COM port? Then try changing the 'hardware flow control' setting.

7. Try changing the 'Script Delay' timer settings found under 'script options'. One second should be sufficient.

8. SIO solves lots of communications problems and is shareware that is highly recommended by me. Try it, if it works for you be sure to register it.

If none of this helps, join the free InJoy Mail List and post your experience there. You can subscribe to the list at:

F/X Mailing Lists

Make sure that the path, working directory and parameters for your program are correctly set.

Make sure you click on the [Update] button for the individual autostart modules BEFORE before you click on the [Ok] button to save the changes to all modules.

Or: When I launch Netscape it reports "There is no connection with your Internet service provider." I click "Don't connect" and Netscape loads and works fine. Why does Netscape not know I'm already connected?

If you are using Warp v4.0, use the set of utilities for the LAN. Those do not use or reference the LINKUP.EXE explained here for InJoy users with Warp v3.0:

Warp v3.0 and Warp v4.0-modem Internet applications start up by using IBM's LINKUP.EXE. That program checks to make sure the IBM dialer has a connection, and if not it launches the IBM dialer.

That is real convenient, except you don't need the IBM dialer and should remove the reference to LINKUP.EXE from those applications.

To do that, just open the settings notebook and in the 'Program' tab (1) Delete LINKUP.EXE from the 'Path and file name:' block; (2) Replace it with a fully qualified path, plus the program file listed in the 'Parameters:' block

example: C:\Netscape\Netscape.exe

(3) Erase the executable in the 'Parameters' block (and, in the case of Netscape only, add the switch "-3" (without the quotes) which causes NS/2 2.02 to report itself as version 3.0 to all Web sites; (4) Close the settings note book.

The next time you connect with InJoy, and THEN launch the application it should work . . . if all goes well.

In addition to Netscape, the Bonus Pack applications are started via LINKUP.EXE and will need the same attention. Or, use the LAN version of all the applications.

There is no master check list as your current configuration affects what steps you have to take (like, do you already have TCP/IP configured?). You should start by reading the IP Masquerading section in USERGUID.DOC

If you are an expert, all you need to know is that:

1. The LAN clients should have a good nameserver entry
2. LAN clients should have the InJoy PC configured as default route / gateway.
3. You must enable masquerading in InJoy
4. Turning off "Masquerading of the InJoy PC" is a good choice
5. IP forwarding should be enabled on the InJoy PC (ipgate on)
6. That's it! It is that easy!

If you are not an expert, there are lots more hints in the Often Asked Questions file at Often Asked Questions.

If you need help with OS/2 routing, then you check out these legendary articles:

http://www.edm2.com/0411/os2routes.html http://www.edm2.com/0501/os2routes.html http://www.edm2.com/0502/os2routes.html

1. The most likely cause is that you are trying to run more masqueraded clients than your license will support. See REGISTER.TXT to determine the level for your license.

2. If you have the top of the line InJoy Professional Enterprise Server/Client (with an unlimited number of clients available) you need to write me with the number of clients you need to run and I'll fix you up.

3. If you ARE running less clients than your license allows and the table fills up, you need to know that ANY IP packet that InJoy has to be send out will have a source IP address. If the source IP is not in the table already, then it will be put in the address table. If, for example you have a license for 4 users but the table fills up before the fourth user gets out I recommend you run IPTRACE and IPFORMAT to see where those IP packets come from? Because, InJoy doesn't specifically support *any* four concurrent users, just the first four IP addresses it sees after it starts. You need to find how the table is filling and stop that traffic before it gets to the address table...one way to do that is with the F/X Packet Filter Plugin.

4. InJoy will record any IP address that is going through it (to the Internet). Unfortunately a TCP/IP stack has a real good memory too and even though you have no applications running, the TCP/IP Stack can still be attempting a close a connection (by periodically sending out packets with the FIN bit set)..

   This can be a problem if you are constantly getting new IP numbers from the ISP. Imagine you running a program that has a connection to a server on the Internet. Then InJoy times out (idle timeout) and the PPP0 interface is gone and you kill InJoy. The program never did manage to close the TCP/IP connection, so the TCP/IP stack will continue to send out packets even though the PPP0 interface is long gone.

   Now, you call the the ISP again and get a new IP number...and the TCP/IP hasn't yet forgot about the old one.

   Repeat this a number of times and you have the problem!!!!!!

   The solution is better housekeeping or DoD with a fixed PPP interface!

Try doing aMODE COMx 1200at the command line (in the COMx part substitute the port number InJoy and your modem are on). See if that won't "wake up" the modem and allow it to dial on the first try after boot. (It doesn't seem to matter what speed you use.)

If that does help, you can put that line in a simple *.cmd to be started at each boot, and that problem is no more.

If the above doesn't help, then try the SIO.SYS com-port driver.

InJoy works fine with IGN...everything is exactly the same as for any other provider EXCEPT in the 'User ID....' block on InJoy's 'Host Setup' page you need to put MORE than just your user ID...

My line (for my Tunnel2@ibm.net account) looks like this:

internet.dkinet.Tunnel2

To fill yours in:

1. Go to IBM's Customer Service folder (mine is in the IBM Internet Connection Folder) and find the icon for your user ID (mine says 'Tunnel2 user ID') and open it.

2. Click on the 'identity' tab and in the box 'User ID' is where I got the Tunnel2 for my InJoy User ID entry line.

3. On the same page is a block 'Name' and that is where the dkinet came from...yours might be usinet or ukinet or whatever...

4. The first part, internet, seems to be constant no matter where you hook in.

5. Fill in all other setup information (like nameserver, domain name, telephone number, etc) and make sure you are calling a v34 node (only they have PPP).

6. Try hooking up WITHOUT using the script autolearn feature . . . just go to the scrip page and press the 'reset' button and make sure autolearn is turned off.

7. Try removing the X from these two settings on the PPP options page:
   
   [ ] Addr & Cntl field compression
   [ ] Protocol compression
   

   One user reported connection reliability near %100 by doing that.

8. Please refer to http://www.fx.dk/injoy/advantis.html if you still have problems, or subscribe to the InJoy Mail List.

This is often the result of InJoy not receiving a "failed to connect" signal from the modem. This may occur if the modem's initialization string (or modem default) for the S7 value is more than what is set in InJoy's "Dial Timeout" on the "Communications setup" page. That situation allows InJoy to 'time out' and disconnect PRIOR to the modem's 'time out'. The solution is to either decrease the S7 time, or increase the value set in the "Dial Timeout".

Bottom line: Modem S7 needs to be LESS than InJoy's dial timeout.

But, another user noted:

Cardinal 33.6 internal, Rockwell chipset. InJoy would dial the first number OK, but if it got a busy signal all subsequent dial attempts would abort just after dialing and never connect. Problem turned out to be in the setup string - but not a timeout setting. Seems this modem (and 2 other 28.8 modems sitting here with Rockwell chip sets) do not respond as documented to dropping DTR with &D3 in the setup. Changing this back to &D2 cured the problem.

The message means that there was an invalid Frame Check Sequence on one or more Internet Protocol (IP) packets of data traversing the link from the ISP to you. If the packet(s) is of the UDP type and were in error they are discarded. If the packet was a TCP it will be retransmitted. In any case, the time that the packet took to traverse the link is lost and may even be doubled, if the corrupted packet is resent.

Sometimes the error message indicates that your PC's COM port has been over run by incoming data. Buffered UARTs are nice (examples include the Hayes ESP II, the LavaLink650 and many more - usually about $US 60-70), but there still is only so much interrupt latency that can be endured before incoming data gets dumped to make room for the next packet.

Decreasing the 'Port Speed' on the communications setup page MAY decrease the number of Invalid FCS packets reported. And, some say there is almost NO difference between port speeds of 56K and 115K. Because, when receiving pre-compressed Internet data such as GIF's, JPegs, Mpegs, audio, demo programs and zip files. These files are compressed prior to the sending modem's attempt to compress them as part of the transmission protocol. Therefore you can't expect much benefit in the higher port speeds for those files. However, Web pages, FTP directories/messages, NNTP news, and SMTP/POP3 E-mail are all uncompressed text. With those files the actual amount of data moved will increase with the higher port speed.

Some experience the invalid FCS error as being correlated to "pegging the CPU" which is then too busy to process data waiting at the port, and the data is dumped.

And, sometimes the problem is because the ISP's modems are overflowing their buffers trying to get data to you quicker than their setup will allow. In that case there is nothing you can do to decrease bad FCS packets (except call the ISP . . . but, don't be surprised if they are sure the problem is at your end).

And, some say it is nothing but line noise.

One user wrote:

You probably will never get rid of FCS error totally on a "normal" dialup connection. If your PC is at a high CPU utilization you may get what is called over run. That is the net trying to send data, but your PC is to busy to accept it, so some of it gets thrown away. But most likely the culprit is your phone line. FCS errors mainly mean that your PC had run the incoming data trough an "validation" routine and found that the data is not correct. That means that somewhere between the sender and you the data was corrupted. On a normal phone line you must expect that. And, depending on how often you get the errors there may be nothing you can do about it. I work at a company that has a little over 100 dedicated data circuits, some analog (voice) some digital. All of them at some point in time get temporary errors due to data corruption on the link. In fact I can create them at will on any link, except 100% fiber.

You MAY be able to reduce the FCS errors some. In your house, or work location, make sure that you have as few as possible AC powered devices around or near you computer, modem and phone cable. Computer equipment it normally o.k., but desk top lamps can cause some problems. The biggest problem causer is cheap little fans.

Tony Rall said:

Invalid FCS - Bad frame check sequence (corrupt ppp packet). May not have been intended as a ppp packet if OS/2 has entered ppp mode while the remote system is still sending text messages. The latter can often be corrected by improvising a better Login Sequence. But you don't have to do anything at all if you just get a few of these messages at the start of the connection. If they continue throughout your session, you should try to correct the problem - they usually indicate a phone or modem flaw that can be corrected by some combination of the following:
• getting a better serial card (with a buffered uart)
  
• running the com port at a lower speed, as low as 9600
  
• replacing the serial cable
  
• getting a better phone connection (note that if the modems are both using error control, such as V.42, this is not a likely cause for the bad packets)
  
• using a better initialization string for the modem
  
• suppressing modem compression (such as V.42bis)
  
• replacing the modem
  
• replacing com.sys with the shareware sio.sys (or vice versa)
  
• running ppp.exe at a relatively higher priority in your system (Note: I don't know how to do this)
  

[NOTE to Tony's Note: We know how to run ppp.exe at a higher priority . . . don't run ppp.exe, run InJoy instead, it allows you to set its priority.]

• Regarding the last point, OS/2 V4 users have reported a marked increase in "invalid FCS" errors. This is quite possibly caused by some high priority system process hogging the processor. One possibility that occurred to me is the voice recognition support.
  

And posted in a newsgroup:

It can be caused by many things: noisy lines, wrong modem init strings of the modem, disk driver clashes, etc. I have tried many different solutions both in Warp 3 and Warp 4. Most effective for me was adjusting the disk driver switches. That is using the /!BM and /!SMS options for BASEDEV=IBM1S506.ADD in CONFIG.SYS. (Typehelp imb1s506.add at a command line for more information.)

Take a look at Peter Moylan's Warp 4 tuning tips. Search on "fcs" and you will find an interesting discussion of invalid FCSs for Warp 4.

And, another users list of fixes:
1. Buy a faster computer :)
   
2. Increase Injoy's priority (in PPP options)
   
3. Install Bus-Mastering drivers (or just turn them on if you have Warp 4 to cut down on the load your hard disk puts on your machine.)
   
4. Turn off Write caching.
   
5. Disable multiblock disk writes in the "BASEDEV=IBM1S506.ADD" line of your CONFIG.SYS (typehelp ibm1s506and look for /!SMS).
   
6. Try the SIO communications drivers in place of COM.SYS
   
7. Lower your port speed.
   
8. Lower the "MAXWAIT" setting in your CONFIG.SYS
   
9. If your modem is an external, then make sure your serial port has a "buffered UART". 16550 are the most common.
   
10. Check the modem cable.
    
11. Make sure you havn't done anything silly like turning off hardware handshaking (ie. flow control).
    

This is reported exactly as found on the net, for what it is worth: "In their infinite wisdom the boys at Microsoft decided to implement a non-standard CHAP version for WIN/NT presumably to tighten security. While their action has been properly reported to those maintaining the PPP-standards they somehow failed to inform the rest of the world. Trying to use a 'normal' CHAP from a non-MS platform to connect to a WIN/NT machine is bound to fail miserably."

InJoy works with the MS version of CHAP. Its as easy as: Turn on MS-CHAP (and probably turn off PAP).

It is not an InJoy problem, and if the connection keeps working don't worry about it, it's usually just PPP trying to configure a protocol you're not using. For example some ISP's have several modem pools using 'Ascend MAX' modems which will sometimes try to configure the PPP connection to include a protocol used on a Mac, and since your OS/2 box doesn't speak 'Mac' it will return the PROTOCOL REJECT error.

Of course this error message doesn't always mean there's no problem. If you're getting this error message and your connection is failing it could be because either side doesn't recognize a protocol needed to setup a working connection. Get a trace and forward it to the InJoy Mail List.

Don't worry about the 80fd - you can't do anything about it, and it doesn't hurt anything. It means that the server is trying to negotiate "compression control protocol" and ppp.exe is denying it (but it's not needed for modem compression or VJ compression).

CPP is not a very efficient protocol and it is not supported by InJoy, nor by PPP.EXE.

Other Protocol values you might see are:

Value (in hex)	Protocol Name
0001	Padding Protocol
0003 to 001f	reserved (transparency inefficient)
0021	Internet Protocol
0023	OSI Network Layer
0025	Xerox NS IDP
0027	DECnet Phase IV
0029	Appletalk
002b	Novell IPX
002d	Van Jacobson Compressed TCP/IP
002f	Van Jacobson Uncompressed TCP/IP
0031	Bridging PDU
0033	Stream Protocol (ST-II)
0035	Banyan Vines
0037	unused
0039	AppleTalk EDDP
003b	AppleTalk SmartBuffered
003d	Multi-Link
005d	reserved (compression inefficient)
00cf	reserved (PPP NLPID)
00fd	1st choice compression
00ff	reserved (compression inefficient)
0201	802.1d Hello Packets
0203	IBM Source Routing BPDU
0231	Luxcom
0233	Sigma Network Systems
8021	Internet Protocol Control Protocol
8023	OSI Network Layer Control Protocol
8025	Xerox NS IDP Control Protocol
8027	DECnet Phase IV Control Protocol
8029	Appletalk Control Protocol
802b	Novell IPX Control Protocol
802d	Reserved
802f	Reserved
8031	Bridging NCP
8033	Stream Protocol Control Protocol
8035	Banyan Vines Control Protocol
8037	unused
8039	Reserved
803b	Reserved
803d	Multi-Link Control Protocol
80fd	Compression Control Protocol
80ff	Reserved
c021	Link Control Protocol
c023	Password Authentication Protocol
c025	Link Quality Report
c223	Challenge Handshake Authentication Protocol

Above list came from RFC1548, which was found HERE!!!

Try this:

Set up an InJoy host, with the "User ID" and "Password" (on "Host Setup" screen) being those needed for the LanRover

Use something like the following connect script (you can try to let InJoy autolearn, then go back and edit to make it like this):

DE: 500
TX: \r
DE: 500
TX: \r
RX: User
TX: ***SecurID User ID here***\r
RX: PASSCODE:
IN: ***SecurID PIN here***
TX: \r


The "IN:" command used above will popup a box with the PIN already entered. You enter the SecurID number from your card and press Enter.

Note the last line sends a CR...this is needed because the "Enter" you send above is only used to close the input box.

Yes, the Often Asked Questions are found on my web site, at

http://www.fx.dk/injoy/oaq.htm

Notice:
This Frequently Asked Questions file was correct (to the best of our knowledge) on its release date. We hope it is helpful and advise you to use it thoughtfully, but at your own risk. Corrections and amplifications should be directed to the InJoy Mail List.

Copyright © 1999, 2000, F/X Communications. All rights reserved. The InJoy Dialer is published by F/X Communications