Problem getting MMS Error 734 (2DE) from RasDial

Problem getting MMS Error 734 (2DE) from RasDial SearchSearch
Author Message
Gareth Reakes
New member
Username: Gareth_reakes

Post Number: 7
Registered: 08-2005
Posted on Thursday, October 06, 2005 - 05:02 pm:   

Hey,

This has just started happening. Was fine yesterday, now the SMS notifications are received but nothing is downloaded. I have swapped modems, reinstalled NowMMS (on a different computer as well) and checked the sim card works in a phone (it does). This is a live service so I would really appreciate some quick help :-)

The modem tests normally under the modem dialog but the mmswap log has problems:

16:55:13:140 [16C8] GetCIDForAPN: MC35 (GPRS)
16:55:13:140 [16C8] GetCIDForAPN: orangemms
16:55:13:140 [16C8] GetCIDForAPN: AT+CGDCONT=?
16:55:13:265 [16C8] GetCIDForAPN:
+CGDCONT: (1-2),"IP",,,(0),(0)

OK

16:55:13:265 [16C8] GetCIDForAPN: minCID = 1, maxCID = 2
16:55:13:265 [16C8] GetCIDForAPN: AT+CGDCONT?
16:55:13:375 [16C8] GetCIDForAPN:
OK

16:55:13:375 [16C8] GetCIDForAPN: AT+CGDCONT=1,"IP","orangemms"
16:55:13:500 [16C8] GetCIDForAPN:
OK

16:55:13:609 [16C8] WSPRasDial: Before RasDial NowSMS - MC35 (GPRS)
16:55:17:734 [16C8] WSPRasDial: Error 734 (2DE) from RasDial
16:55:17:734 [16C8] WSPRasDial: Closing connection
16:56:04:531 [16C8] InitTAPI: Returning cached TAPI session information


If you leave it running the error keeps appearing.

Any suggestions?

Gareth



Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5076
Registered: 10-2002
Posted on Thursday, October 06, 2005 - 09:06 pm:   

Hi Gareth,

The GPRS connection is being rejected.

The question is why.

The only time I have seen this error before was on a network where a username and password were required for connecting to the APN. When the username and password were not supplied, this error would occur.

"orangemms" doesn't require a username or password, however. But maybe if you have one configured, that might cause a problem?

My first suggestion would be to try the "Test Connection" in the user interface, and see if it reports any more detailed information. (In particular, if your MC35 modem driver got re-installed, it might tell you that it needs to update the driver if it detects something in one test that only is carried out by the "Test Connection" button, and not by the server itself.)

The next suggestion would be to try to put the SIM into a phone and see if it can send/receive MMS with the phone. But that might not be a good option because then the waiting MMS messages will get downloaded to the phone instead.

So an alternative would be ... Do you have another Orange SIM? If so, do you get the same error with that SIM? What I think we need to determine is whether the problem is SIM specific (i.e., if for some reason, Orange is not letting it connect to the "orangemms" APN any more).

-bn
Gareth Reakes
New member
Username: Gareth_reakes

Post Number: 8
Registered: 08-2005
Posted on Friday, October 07, 2005 - 09:31 am:   

Hey,

Thanks for the quick reply. I did already try it in the phone (and hope that MMS were mot sent in that time except my test one) and it was fine. This happens for all sim cards (I have tried another one). When I installed it on a new computer the test conneciton button did indeed result in some changes being made to the driver, but they seemed to have no effect.

As a last resort I downgraded a M$ update that seemed to have nothing what so ever to do with anything this might touch. The problem is now cured. Note I do not say the update was the problem, as it seems unlikely to me but I cant see anything else that has changed. When I have an hour I will downgrade the other box NowMMS is on and see if that makes it work.

Cheers,

Gareth
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5085
Registered: 10-2002
Posted on Friday, October 07, 2005 - 07:51 pm:   

Hi Gareth,

Another point worth mentioning...

NowSMS dynamically creates a dial-up profile named "NowSMS - modem driver name", in this case "NowSMS - MC35 (GPRS)".

Try making a connection via that dial-up profile manually.

That should result in the same error.

It may be worth deleting that dial-up profile, and letting it be created all over again.

-bn
Gareth Reakes
New member
Username: Gareth_reakes

Post Number: 10
Registered: 08-2005
Posted on Tuesday, October 18, 2005 - 11:38 am:   

Hi,

This problem has occured again. I don't seem to have any "NowSMS - MC35 (GPRS)" in dial up in network connections. Could this be a problem?

Gareth
Gareth Reakes
New member
Username: Gareth_reakes

Post Number: 11
Registered: 08-2005
Posted on Tuesday, October 18, 2005 - 11:48 am:   

I removed the modem completly and reinstalled the driver and then added it back to NowSMS. No luck. Here is the log

11:45:17:343 [F4C] GetCIDForAPN: minCID = 1, maxCID = 2
11:45:17:343 [F4C] GetCIDForAPN: AT+CGDCONT?
11:45:17:468 [F4C] GetCIDForAPN:
OK

11:45:17:468 [F4C] GetCIDForAPN: AT+CGDCONT=1,"IP","orangemms"
11:45:17:578 [F4C] GetCIDForAPN:
OK

11:45:17:703 [F4C] WSPRasDial: Before RasDial NowSMS - MC35 (GPRS)
11:45:21:796 [F4C] WSPRasDial: Error 734 (2DE) from RasDial
11:45:21:796 [F4C] WSPRasDial: Closing connection
11:45:31:500 [F4C] InitTAPI: Returning cached TAPI session information
11:45:31:500 [F4C] OpenDevice: lineNegotiateAPIVersion failed error 80000042 (2147483714), device = 0
11:45:33:078 [F4C] GetCIDForAPN: MC35 (GPRS)
11:45:33:078 [F4C] GetCIDForAPN: orangemms
11:45:33:078 [F4C] GetCIDForAPN: AT+CGDCONT=?
11:45:33:187 [F4C] GetCIDForAPN:
+CGDCONT: (1-2),"IP",,,(0),(0)

OK

11:45:33:187 [F4C] GetCIDForAPN: minCID = 1, maxCID = 2
11:45:33:187 [F4C] GetCIDForAPN: AT+CGDCONT?
11:45:33:312 [F4C] GetCIDForAPN:
OK

11:45:33:312 [F4C] GetCIDForAPN: AT+CGDCONT=1,"IP","orangemms"
11:45:33:421 [F4C] GetCIDForAPN:
OK

11:45:33:546 [F4C] WSPRasDial: Before RasDial NowSMS - MC35 (GPRS)
11:45:37:625 [F4C] WSPRasDial: Error 734 (2DE) from RasDial
11:45:37:625 [F4C] WSPRasDial: Closing connection


Help would be most appreciated.

Gareth
Gareth Reakes
New member
Username: Gareth_reakes

Post Number: 12
Registered: 08-2005
Posted on Wednesday, October 19, 2005 - 12:02 pm:   

OK, so I recreated eveything from scratch again and the conneciton did appear. I have exactly the same issue now though :-( Test connection says that the modem is not responding properly to gprs commands. If I connect to the modem in connections then it does indeed connect.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5161
Registered: 10-2002
Posted on Wednesday, October 19, 2005 - 05:45 pm:   

Hi Gareth,

If test connection says that the modem is not responding properly to GPRS commands, then this does not sound like the same issue. It sounds worse. Generally, in this situation, we're not getting anywhere with the modem, as it means that we are failing to set the GPRS APN.

Try the following talking to the modem in HyperTerminal:

AT+CGDCONT?

(should return OK, might also return +CGDCONT: 1,"IP","orangemms",,0,0)

AT+CGDCONT=1,"IP","orangemms"

(should return OK)

AT+CGDCONT?

(should return +CGDCONT: 1,"IP","orangemms",,0,0)

Basically, this check is failing.

This "Error 734 (2DE) from RasDial" generally occurs if the GPRS APN is not set correctly, or if the username and password (for connecting to the APN) is not set correctly.

That would seem to go along with the error about the modem not responding properly to GPRS commands. I'd also like to see an MMSWAPDEBUG.LOG that just shows the "Test Connection".

Unfortunately, I don't have any idea how a previously working configuration ends up in this state. It doesn't make any sense, unless something has gone wrong with the modem.

-bn
Gareth Reakes
New member
Username: Gareth_reakes

Post Number: 13
Registered: 08-2005
Posted on Wednesday, October 19, 2005 - 06:09 pm:   

Hey,

Thanks for the response. From my research I also agree it seems strange. However, it has now happened twice with no one even touching the machine (its a rack mounted box). I agree it does seem to suggest a modem problem. The 2 counters to that is that we swapped modems with the same result and when it happens to one, it seems to happen to the other (also on orange) that we use to send out MMS.

We have placed the sending MMS version on a non server version of windows this afternoon and this has worked. Just like the last time though, I doubt this is really the problem. Any settings or config you would like me to change I would be happy to. Since this happens accross multiple computers, modems and sim cards it seems hard to believe that no one else is having these problems. Is anyone out there running a perminant MMS recieving service with MC35i / orange? If you have read my other posts, it also seems to get into a strange state every few weeks where it doe snot respond. Has anyone else seen this?

Gareth
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5169
Registered: 10-2002
Posted on Wednesday, October 19, 2005 - 07:00 pm:   

Hi Gareth,

On the modem not responding issue, have you tried the v5.51k update?

If the modem is in an unstable state, and it is possible to recover (i.e., the firmware isn't in some sort of hung state), then this version employs a number of tricks ... which at least work in the error situations that we can simulate.

In the real world, when we have seen a problem in this area (and the culprit is not a bad cable, which happens quite frequently with USB), the problem usually occurs after sending or receiving an MMS over GPRS ... and it appears that the modem never fully terminates the GPRS connection. However, we've only had a small number of reports of problems like this, and we've never been able to recreate. But in simulated conditions, v5.51k can recover from this, as long as the modem will allow it.

-bn
Gareth Reakes
New member
Username: Gareth_reakes

Post Number: 14
Registered: 08-2005
Posted on Friday, October 21, 2005 - 11:34 am:   

Hi,

Yes that does seem to do the trick for the hung state (although a few more tests are required I think). I will get back to you.