| Error 734 from RASDIAL |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Drg Unregistered guest |
Hey guys, Trying to get MMS receiving working but I keep getting the error "734" from RASDial when it's using my modem. I created a 56000 bps modem and set it all up in dialup networking, I added: AT+CGDCONT=1,"IP","internet" to the modem initialization strings. I can now connect to it fine using Windows dial-up networking. However, when trying to use NowSMS to test the connection, I get error 734. This was the same error code I received from Windows when I omitted the AT+GDCONT line. So my assumption is NowSMS is failing to send that line to my modem. What can I do about this? There's nowhere I can put initialization strings in NowSMS and it seems to "override" Windows's settings. I really need a way to do this or the software won't be worthwhile for our business. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4351 Registered: 10-2002 |
Enable the MMSWAPDEBUG.LOG (on the Serial #) page of the NowSMS configuration, and you should see that we are issuing this command. (The MMSWAPDEBUG.LOG will show it.) Are you using NowSMS v5.51? (When it tests the modem configuration, it will update some modem drivers that cause problems with the PDP context being lost.) Also, keep in mind that NowSMS is going through Windows dial-up networking, so if you have an extra initialisation command defined for the modem driver, it is going to be executed when NowSMS connects to the modem driver. (As I explained in another thread on this topic, you should enable the Windows modem log as well, and you would see the extra initialisation command being sent.) For a 734 error, it is also possible that your provider requires a username/password to connect to the APN. There is a login name/password setting in NowSMS, under where you configure the GPRS APN name. This should match the username/password that you are using when you do your own connections via a DUN profile. -bn | |||
| Drg Unregistered guest |
I am experiencing the same problem. I have put the initialization command in Dial-Up networking. When I connect using Windows, it works just fine, I get an IP address, everything is dandy. When I use NowSMS .. "Connection Failed" appears on my mobile and NowSMS gives me the 734 error. That is the EXACT same error as when I omit the AT+CGDCONT line from the initialization in DUN. My only conclusion is that NowSMS is simply failing to send that line to the modem, or is somehow overriding the DUN defaults. No username/password is required, because DUN is working just fine. I've tried every other single setting in NowSMS and nothing works. Is it possible to release a fix for the software? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4409 Registered: 10-2002 |
This is not a general problem. I believe it is something specific to your configuration. However, I don't have enough information about your configuration to make a diagnosis. I haven't seen any log files, and I'm just working from very limited information trying to provide my best guess and pointers. So continuing in that vein ... If you have a dial-up networking profile that is working, you can configure NowSMS to use it directly. In the "Network Connection" field, you will find the DUN profiles listed with a "Dial-up:" prefix. I generally recommend using a "Modem:" entry here, where NowSMS automatically creates the modem profile. However, I do not know why the "Modem:" entry is not working in your case, so there is no harm in trying the "Dial-up:" entry (although you should make sure that "use default gateway" is not checked in the profile, otherwise you may lose local network connectivity when the dial-up connection is initiated). Beyond that, perhaps I should be more clear in my saying that I'd like to see the log files that I have told you to look at. For example, MMSWAPDEBUG.LOG should show us issuing the AT+CGDCONT command. I'd like to see that, as it might point out what the problem is, or provide another clue. I'd also like to see the Windows modem driver log. Go into the Windows Control Panel, selecting Phone & Modem Options, Modems, Properties, Diagnostics ... then enable "Append to Log" ... try connecting again, and select "View Log". The log file might provide more information about what the modem driver thinks is going wrong. And actually, that brings up another question/issue ... are you trying to use the "internet" APN from NowSMS or a different APN? (It is unusual for the "internet" APN to be used for MMS sending/retrieval.) In any event, I'd like to see the two logs ... MMSWAPDEBUG.LOG ... and the Windows modem driver log. Preferably, I would like to see these logs showing connection attempts when you are using a "Modem:" selection for "Network Connection" (and not the "Dial-up:" selection that I recommended above that you try). -bn | |||
