Couldn't get MJ running on my desktop at all. Finally tried my laptop and needed to use a powered USB hub to get it to work (powered USB hub still doesn't work on the desktop).
Anyway, I finally got it working on the laptop and had my 802.11g wireless card enabled at the time, no ethernet cable connected. Once I got it working, i set up the laptop in a more permanent location, using an ethernet connection. The weird thing is it will NOT dial out with ethernet. However, as soon as I enable the wireless card, it dials perfectly. The error I'm getting is error 3 - after which it takes me to the proxy registration (wants my UID and PW), but, never seems to be successful. FWIW, my ethernet connection is otherwise working fine. I even rebooted the laptop to make sure I acquire a network address thru the cable and not the wireless adapter.
I would not otherwise care about using the wireless card - except that the wireless access point drops the connection for 20-30 minute intervals at least once every 2 or 3 days. Not good if I'm going to be using this for making phone calls and the wireless connection goes out.
Any suggestions as to why it insists on the wireless card and not the ethernet cable?
Strange Error 3 Behavior
Moderators: Bill Smith, Pilot
-
nycfonephreak
- MagicJack Newbie
- Posts: 4
- Joined: Thu Mar 13, 2008 8:51 pm
Try disabling the wireless interface by right-clicking its icon in Network Connections and selecting Disable. Then reboot and try MJ again. If it still fails, I'd suspect some software firewall may have different rules in force for the two interfaces. If still no luck, use Wireshark to see what traffic is being blocked and/or altered. (If you run Wireshark on the wireless for comparison, note that for most cards you must turn off promiscuous mode.)
-
curiousgeorge
- Dan isn't smart enough to hire me
- Posts: 193
- Joined: Wed Jan 23, 2008 5:55 pm
- Location: California
If you are on win xp try to disable/un-install the software for your wireless card and use the one that comes built in to windows,this seems to work on some cards that have the same problem you are having, Good luck.
help! I am running out of USB ports!!!!!!!!
Tell me, Mr. Anderson... what good is a phone call... if you're unable to speak?
Tell me, Mr. Anderson... what good is a phone call... if you're unable to speak?
-
gooney
- Dan isn't smart enough to hire me
- Posts: 382
- Joined: Sat Feb 09, 2008 5:38 pm
- Location: Salt Lake City, Utah
Re: Strange Error 3 Behavior
what kind of router do you have? have you updated the firmware for that router?nycfonephreak wrote:Couldn't get MJ running on my desktop at all. Finally tried my laptop and needed to use a powered USB hub to get it to work (powered USB hub still doesn't work on the desktop).
Anyway, I finally got it working on the laptop and had my 802.11g wireless card enabled at the time, no ethernet cable connected. Once I got it working, i set up the laptop in a more permanent location, using an ethernet connection. The weird thing is it will NOT dial out with ethernet. However, as soon as I enable the wireless card, it dials perfectly. The error I'm getting is error 3 - after which it takes me to the proxy registration (wants my UID and PW), but, never seems to be successful. FWIW, my ethernet connection is otherwise working fine. I even rebooted the laptop to make sure I acquire a network address thru the cable and not the wireless adapter.
I would not otherwise care about using the wireless card - except that the wireless access point drops the connection for 20-30 minute intervals at least once every 2 or 3 days. Not good if I'm going to be using this for making phone calls and the wireless connection goes out.
Any suggestions as to why it insists on the wireless card and not the ethernet cable?
Chat with me LIVE!!! 
gooney - Salt lake City, UT (801)
Don't mind me grammar cuzz it sukks!!
gooney - Salt lake City, UT (801)
Don't mind me grammar cuzz it sukks!!
-
nycfonephreak
- MagicJack Newbie
- Posts: 4
- Joined: Thu Mar 13, 2008 8:51 pm
Some progress...
First, just to clarify, it's the wireless card that IS working ok. The ethernet connection is NOT working. Both are set the same (IP Properties set to acquire an ip address automatically).
Here's the progress report...
The router is a Linksys BEFSR41. Firmware was outdated (1.04.02 - latest is 1.04.09) I updated the firmware and MJ worked one time thru the ethernet connection. However, after I rebooted the computer, I got the same error with ethernet. The actual error was "waiting for proxy regis" immediately after dialing an outgoing number... followed by the prompt to connect to the internet [error 3]"
After rebooting numerous times, and still being unable to call out via ethernet, I pressed the reset button on the router and was able to make numerous calls via ethernet. I guess that's why it worked immediately after upgrading the firmware - the upgrade process resets the router in addition to loading the new firmware.
I can live with needing to reset the router every now and then, if this is what it takes to keep MJ happy.
I guess I still don't understand why the behavior would be different on wired v wireless since both are going thru the same router. Just when I think I know everything I need to know, I realize how much more there is that I don't understand.
Anyway, thanks for the suggestions. I probably would never have tried the router's reset button had you not pointed me at the router as a possible source of trouble.
First, just to clarify, it's the wireless card that IS working ok. The ethernet connection is NOT working. Both are set the same (IP Properties set to acquire an ip address automatically).
Here's the progress report...
The router is a Linksys BEFSR41. Firmware was outdated (1.04.02 - latest is 1.04.09) I updated the firmware and MJ worked one time thru the ethernet connection. However, after I rebooted the computer, I got the same error with ethernet. The actual error was "waiting for proxy regis" immediately after dialing an outgoing number... followed by the prompt to connect to the internet [error 3]"
After rebooting numerous times, and still being unable to call out via ethernet, I pressed the reset button on the router and was able to make numerous calls via ethernet. I guess that's why it worked immediately after upgrading the firmware - the upgrade process resets the router in addition to loading the new firmware.
I can live with needing to reset the router every now and then, if this is what it takes to keep MJ happy.
I guess I still don't understand why the behavior would be different on wired v wireless since both are going thru the same router. Just when I think I know everything I need to know, I realize how much more there is that I don't understand.
Anyway, thanks for the suggestions. I probably would never have tried the router's reset button had you not pointed me at the router as a possible source of trouble.