Skip to main content

Smart Prepaid Broadband - ERROR 619: A connection to the remote computer could not be established, so the port used for this connection was closed


ERROR 619: A connection to the remote computer could not be established, so the port used for this connection was closed

This error appears to my Smart Prepaid Broadband two weeks ago.


This is what happen. I insert the SIM card of the prepaid kit to my cellphone to use the remaining load balance to text my girlfriend. After I sent a message, i return it to prepaid kit then connect it to my pc. The ERROR 619 shown out after i click the connect button from the Smart Broadband Prepaid Software.


I thought that there was a problem with the SIM card or the hardware of the prepaid kit, that's the time i decided to call Smart Customer Service. Operator told me that the signal on my After some troubleshooting, ERROR 619 is still there. And my final decision is to bring it to the nearest smart wireless outlet on the next day.

During the next day, i finally tried my Smart Broadband Prepaid Kit to connect to the web. I didn't expect that it will connect to the web without the ERROR 619.

Until now, I'm still wondering about what happen to my Smart Prepaid Broadband. Maybe i'll stop using the sim card to my phone again. I'm thankful that i can use internet again. Yes!!!
Labels:

Comments

Anonymous said…
you know what, im also having the same problem as what you have. have you find a fix already? i think theres nothing to do with the prepaid kit coz, my moms laptop is getting the error, so what i did, i tried my prepaid kit on her laptop and it didnt work, same exact error... and i did try her prepaid kit on my laptop and it did work. so its with her laptop. i tried switching usb ports, same thing. i tried on other user account, i did not work. so there is somethings wrong with the software... there might be installed softwares that conflicts with the smart prepaid kit... other prepaid kits worked fine...
4/07/2011 11:21:00 PM
Anonymous said…
you know what, im also having the same problem as what you have. have you find a fix already? i think theres nothing to do with the prepaid kit coz, my moms laptop is getting the error, so what i did, i tried my prepaid kit on her laptop and it didnt work, same exact error... and i did try her prepaid kit on my laptop and it did work. so its with her laptop. i tried switching usb ports, same thing. i tried on other user account, i did not work. so there is somethings wrong with the software... there might be installed softwares that conflicts with the smart prepaid kit... other prepaid kits worked fine...
4/07/2011 11:23:00 PM
Post a Comment

Popular posts from this blog

The security log on this system is full. Only administrators can log on to fix the problem.

The security log on this system is full. Only administrators can log on to fix the problem. To resolve this issue, use an account that is a member of the Administrators group to log on to the computer. Then, follow these steps to specify that Security log events can be overwritten: 1. Click Start, point to All Programs, point to Administrative Tools, and then click Event Viewer. 2. Right-click Security, and then click Properties. 3. In the Log Size area of the Security Properties window, click the Overwrite events as needed option under When maximum log size is reached. 4. Click OK. 5. Close Event Viewer.
11 comments
Read more

CWBLM0011 - An Internal License Management Error Occurred.

CWBLM0011 - An Internal License Management Error Occurred. RESA II started recieving error messages when users would sign on with client access express running on Windows 2000, the first client would connect but the second would get a license code error that said internal licensing error, here is a description from IBM's website, "Windows NT/2000 Restricted Users (User Group) attempting to start a 5250 terminal emulation session running Client Access Express (5769XE1) V5R1M0 receive a CWBLM0011 error message. This error does not occur when logged on to the PC as the Windows Administrator. The error appears more frequently when the users attempt to start multiple Client Access sessions." It appears to happen because the user doesn't have permissions to update some registry keys that client access likes to update occasionally, so this error message can happen at any time and doesn't appear to have any rhyme or reason. In RESA II's case, Tim believed it was ca...
6 comments
Read more