View Single Post
  #4 (permalink)  
Old 03-16-2008, 05:40 PM
Gilliland's Avatar
Gilliland
PPCGeeks Regular
Offline
 
Join Date: Aug 2007
Posts: 140
Reputation: 30
Gilliland is just getting started
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: No longer able to Bluetooth DUN after 3.35

OK, after pondering it a bit longer, I found a solution - simply move the GPS port. If you go into the first page of the GPS settings, you can move the virtual GPS port to COM5. That frees up COM4 for PDANet. The GPS works fine on COM5.

However, that's not the end of the battle, at least not on my phone.

Now whenever I try to connect via DUN, the phone tries to dial and then reports an authentication error with my ID and password (both of which are blank, as they should be). From that point on, the Mogul can no longer connect to the internet (whether for the tethered PC or even for internal functions) until I restart the Mogul. Once I restart, everything works fine again until I attempt to connect via DUN.

Either I have something misconfigured, or perhaps Sprint has done something to cut down on unauthorized tethering. I'm hoping its the former, but if so I haven't figured out what.

Last edited by Gilliland; 03-16-2008 at 07:02 PM.
Reply With Quote