Most likely caused by problems with the host name or address as entered in the paging service setup or the telnet proxy setup. May also indicate that the host itself is down, or that part of the network connecting the user's computer to the host is down, or that the host is simply not accepting connections on the specified port.

• Make sure there is a Working Internet connection
• Make sure there is not a firewall blocking the Internet connection from the InfoRad software
• Make sure there is not antivirus software blocking the Internet connection from the InfoRad software.
• If all the above checks out, then it could be that the paging company or cellular company to which you are sending is down. Hopefully, they are only down temporarily. Feel free to call into our office to find out if our call volume has increased. If so, it's a good chance that the paging / cellular company is down.

NOTE: Today, some software companies, such as McAfee, may develop an Internet Suite of software that provides both a firewall and antivirus. This kind of grays the line between what, or which side of the software, may actually be blocking. At the same time, some software suites have services that run in the background. Therefore, it's not always the case where the antivirus or firewall software is disabled using the icon on the Task bar, because the service is still running in the background. There have been cases with InfoRad customers where an exception had to be added to the software (in various places - on both the antivirus and the firewall side) so that the InfoRad software can run properly, sending text messages via Internet email mostly. Error 6002 can also occur when trying to send text messages via the Internet SNPP protocol (Ie. Nextel two-way Messaging, Nextel Text Messaging - Internet SNPP, and Alltel PCS - Internet SNPP).

The majority of InfoRad cases indicate that this error is caused by antivirus software (normally McAfee Enterprise software) blocking the InfoRad software from sending text messages via Internet email. The result is to add InfoRad's executable (winpage.exe) as an exception to the McAfee software.

If sending text messages to pagers or cell phones (Specifically Alltel or Nextel. Can also be Cingular if phone accounts are on Cingular's Enterprise Paging) via the Internet SNPP protocol, then this error could be returned. Most likely causes are that there is a firewall blocking the Internet connection to the SNPP server across port 444. Otherwiswe, the remote host itself (the SNPP server, or possibly the telnet proxy server, if one is configured) disconnected without warning.

If sending text messages to pagers or cell phones via email (SMTP), then it is likely that you have antivirus software that is blocking the connection. Many cases indicate that anvitirus software monitors for Spam-like activity, which in turn, the antivirus software will then block the InfoRad software from making its connection to the email (or SMTP) server. Possible solutions are to disable the antivirus software from scanning outgoing email or configure the antivirus software to allow the InfoRad software to make the connection to the appropriate email server on the required port (which is normally port 25).

SMTP

The most likely case here is McAfee antivirus/firewall software is blocking your connection to the appropriate email server. Refer to McAfee tech support for assistance with configuring the software to allow InfoRad's executable (Winpage.exe) for bidirectional communication (SMTP) across port 25.

Another Case appeared when sending text messages via Internet email to TMobile phones. The customer changed the timeout from 30 to 40 Seconds and the Max Message Length from 80 to 140 Characters. The thought was that the timeout (increasing it to 40 Seconds) may have been preventing the connection by not allowing enough time for the connection to be established between the Customer’s PC and TMobile’s Email Server.

SNPP

The timeout for the paging service (set up in the paging service properties screen) elapsed with no response from the SNPP server. This problem can sometimes be rectified by increasing the timeout, but it may indicate something wrong with the SNPP server or with the network connection.

This is a popular error among InfoRad users who are sending text messages to cell phones via Internet email. Continue Reading If you are sending text messages via Internet SMTP or email. Otherwise, Refer to SNPP Below.

• The most common occurrence is InfoRad users that are connecting directly to cellular company email servers (Ie. Verizon's smtpsp.vtext.com). Therefore, we recommend that you either setup the InfoRad software to use your own outgoing email (SMTP) server or use some other 3rd party, commercial email server that you can depend on (Like maybe Google's Secure SMTP Server).
  
  
• Another common occurrence is caused by an Internet Service Provider or network that does not allow you to connect to email servers outside of their own domain. We recommend that you first try using the email server provided by your Internet Service Provider. Click Here to view InfoRad's list of ISPs. If you use Outlook, then you may find this information in Outlook normally under Tools, Services (Outlook 2000) or Tools, Email Accounts (Newer). You would need to know your outgoing email (SMTP) server address and whether or not it requires authentication. Once you have that information, for any Receiver that uses an email address for the Receiver's ID, you can enter a New Messaging Service using the email server information you obtained from above (ShowMe).
  
  
• Some Cases show that the connection to the email server is being blocked by some firewall or antivirus software. If you are familiar with configuring your antivirus or firewall software, then add an exception for the InfoRad software (normally, Winpage.exe is the executable and port 25 for SMTP). An alternative is to try disabling the antivirus software from scanning outgoing email. However, you may want to keep it scanning your incoming email. Sometimes, there is a website url sjbl.org in the response coming back from the hardware (in the error message itself) that provides you with a link to which you can browse and have yourself removed from the Spam blocking list. If this is the case, then we would caution you to investigate this issue further before you find yourself on this list again and not be able to have yourself removed from it. Check with your local Internet Service Provider and/or antivirus software to find out what their rules are concerning Spam. You may have to follow these rules to prevent yourself from ending up on such a list.
  
  
• Sometimes an email server will tell you that the email address you entered is incorrect. For instance, setup a Receiver to send to XXX5551212@vtext.com and select Verizon PCS – Internet SMTP for the Service (make sure that you also have your own email address entered under Setup, Internet Settings, ReplyTo Address). Send a test text message and you’ll get error 6203 indicating that XXX5551212@vtext.com is not a valid Verizon (vtext) email address. To fix, correct the email address and try again.
  
  
• One instance can be caused by not having a ReplyTo Email Address entered under Setup, Internet Settings. (Show Me)
  
  
• Other cases have shown that an this error can occur when an email server (Messaging Service) requires authentication but either the InfoRad Wireless software does not have SMTP Authentication enabled or an incorrect username and password is entered (under Edit, Messaging Services for version 9.7.X and higher. Version 9.6.X does not support SMTP Authentication. You will need to upgrade your software. Call (800) 228-8998 for upgrade options).
  
  
• 7/17/07 - A Customer was receiving error 6203 when using own exchange server as a Messaging Service to send to cell phone emails. The Response from the email server showed WSAEWOULDBLOCK, which is a Windows Sockets Error 10035 according to Microsoft ( Refer to http://msdn2.microsoft.com/en-us/library/ms740668.aspx ). To fix, the customer changed from using the loopback address (127.0.0.1) to the network IP of the exchange server.
  
  
• 11/27/07 - Make sure you check that the Messaging Service is setup correctly. This is what happened when I had the wrong SMTP Server Address entered for the Messaging Service (it should have been mx1.business.mindspring.com instead of mx.business.mindspring.com). The Receiver ID, of course, is techsupport@inforad.com. I received error 6203 and the Response from hardware (in the error message) showed the following:
  
  VerifySmtpConnection: Checking connectivity to SMTP server mx.business.mindspring.com:25 smtp_host: mx.business.mindspring.com smtp_port: 25 WaitForData timed out. Failed to get initial response. The SMTP server may be denying access for this domain.
  
  Another clue indicating that you may have the Messaging Service setup incorrectly can be found in the Response from hardware (in the error message). It is similar to the following:
  
  SendEmail: SMTP_Connect: Connecting to SMTP server mail.earthlink.net:25 smtp_host: mail.earthlink.net smtp_port: 25 smtp_user: NULL trying_auth_method: NONE InitialResponse: 220-pop-cowbird.atl.sa.earthlink.net ESMTP Exim 3.36 #1 Tue, 27 Nov 2007 08:58:54 -0500220-NO UCE. EarthLink does not authorize the use of its computers or network220 equipment to deliver, accept, transmit, or distribute unsolicited e-mail. login_method: NONE or already authenticated CONNECTED to ESMTP server mail.earthlink.net:25 subject: from: recipients: 550 Authentication required. Help at http://www.earthlink.net/go/emailsettings Failed when sending RCPT TO: bad_address: XXX5551212@email.com Send failed.
  
  Therefore, to fix you would go under Edit, Messaging Services, and edit the Messaging Service being used for that Receiver(s). Check the box for "My server requires authtentication" and enter a valid email address and password.

If you're sending via the Internet SNPP (supported by Nextel or Alltel phones and numerous paging companies - ShowMe), then it could be that you have an incorrect Receiver ID entered. Make sure that you are using the ten-digit phone number of the pager or cell phone. Do not use dashes, spaces, or parentheses. When this error happens, the explanation text sent by the SNPP server will be included on the error screen along with this error message. That explanation should provide more detail on why the transaction failed. The explanation might be, for example, "550 Error, pager ID must be 10 digits" or "550 Error, pager ID cannot be identified" and so on.

• Click Edit, Receivers and make sure you have the correct seven or ten-digit phone number entered. Do not use dashes, spaces, or parentheses.

The URL address for the Messaging Service could not be parsed in order to attempt a connection. Check the Messaging Service address.