Related
I am seriously frustrated here:
I have an Ameo 16 GB (T-Mobile UK) and for the 1st couple of weeks remote desktop was working fine, then suddenly it stopped working.
I thought I broke the settings somewhere, so I double-checked everything. The T-Mobile Ameo comes with the default T-Mobile Internet connection pre-configured. It actually states "This connection is pre-configured. It cannot be modified."
The default settings are programs that auto connect to the Net should connect using the default T-Mobile Internet connection, and programs that auto-connect to a private network should use "My Work Network".
"My Work Network" has no values set anywhere.
Normal Internet access is fine in either IE or Opera (branded by T-Mobile as Web'n'Walk).
I have changed so programs that auto-connect to private network use T-Mobile Internet connection, same result as before.
I have set up a custom Internet connection for "My Work Network" using "general.t-mobile.uk" as access point, "user" as username, "pass" as password and domain left blank. I can connect to the Internet with these settings, but not via Remote Desktop.
Sometimes, normally after having re-booted the Amea and manually connected to "My Work Network" (as per settings above) I can connect, but it drops the connection while I'm still typing in username and password.
Normally I get either of these error messages when trying to connect via Remote Desktop:
"Cannot connect. Likely reasons are:
1) Specified computer name or ip does not exist.
2) A network error occurred while establishing the connection"
or
"Cannot connect with current connection settings. To change your connection settings, tap Settings".
I have cleared storage memory on the Ameo five times. I have phoned T-Mobile tech support who basically told me to sod off - apparently as long as the device can browse the Net they've done their job!
I have had T-Mobile replace the device and this morning I received a brand-spanking-new Ameo. I fired it up, let it go through the customisations, and reboot, then I tried Remote Desktop without changing anything or installing anything. And I got the same as above!!!!!
Please, guys, I'm desperate! Any help is very welcome here! I do network support for a living and I got the Ameo because I can fit a server's entire screen in and have a seperate keyboard. Except now I can't use it!
I used to have a Universal, which I sold to help finance the Ameo, so I'm truly stuck!
Oh how I wish I could unlock the damn thing and flash a better ROM to it!
Just as an update, yes, I've tried using "My ISP" as well, with the same results. And yes, everything's just peachy on the servers I need to connect to - I can connect to those servers using other devices.
And no, using Logmein is NOT an option and please don't even mention any form of VNC - you have to be seriously foolish to run VNC on a server, you might as well pay for some banner ads that say "Come hack me!"
Please don't give me advice on setting up routers, or Remote Desktop on 2000 Server, Server 2003 or Server 2008. I can do those quite well.
What I cannot do is get my damn Ameo to connect and stay connected and I'm absolutely desperate for help there!
the same
my ameo on t-mobile has done same thing, stopped working about 2 weeks ago, was working fine till then, only reason i bought the damn thing (anmd yes, i too ebayed my exec, i regretting it
so anyone out there got any ideas? i have same problem using ICS so i am guessing either a network etting on the phone, or some idiot at t has closed rdp traffic (tried chanmging a port number to 80 on a test box behind my router, still no go)
What is the operating system on the target pc first off. as i had that problem with a hack fix on vista home premium
all i had to do was to re-apply the fix.
as far as remote desktop the Ameo 8gb model ( x7500) didn't have rdp on it so i used one of the ones from this forum but under another section ( i think it was networking but do s earch to find them )
needless to say mine has never stopped working
a good test is try it from your local wireless home network if it's a home pc, and if ti works then look at the forwards on your router, make sure 3398 is still forwarding to YOUR pc and that your pc still has the same IP.
if you have a static ip and no router. always check your firewall settings.
as far as other possibles if your internet is working and all other data connections then there's no reason it SHOULDN'T work as t-mobile do not filter out 3389 port.
it has to be a problem at the target machine or network in that case.
but feel free to tell us more about the target pc and how it's connected to the internet and maybe we can find a solution
also what RDP client are you using on your Ameo
Cyberjak, the target machines vary: Server 2003 Enterprise Edition running ISA Server 2006, and Server 2008.
RRAS is installed on the non-ISA servers, while ISA of course takes over where RRAS left off. In all cases ports 3389 (TC{P & UDP) is open for inbound access, and on the ISA box it is open for in and outbound access.
Had you read what I wrote in my second post you would have seen I need no help in setting up RDP. I build, support and maintain networks for a living and trust me when I say the issue is NOT with the remote servers, but with the Ameo! I can use a collegue's O2 Touch Diamond and connect to any of the servers, but not the Ameo 16 GB.
I'm using a default T-Mobile Windows Mobile 6.1 setup as my Ameo has never been unlocked or flashed, and I'm using the stock standard Remote Desktop client that came pre-loaded and that used to work.
The issue is either with the Ameo, or with T-Mobile blocking RDP.
NanoRuler said:
Oh how I wish I could unlock the damn thing and flash a better ROM to it!
Click to expand...
Click to collapse
Why can't you do this? Is your phone owned by the company and they would frown if you modified it? AP4 includes Remote Desktop Mobile, so you might try that ROM if you do unlock.
My device is a 7510 and Olipro's unlocker doesn't work on it. I have been explicitly told that the unlocker might brick it
Hallelujah! The age of miracles is upon us!
I've put in a complaint to T-Mobile, and out of the blue Remote Desktop started working, while I also received an e-mail from T-Mobile's tech support.
Here's an extract from the e-mail:
"I have came across someone else with this problem and we are trying a temporary fix by adding a update to your account which is on now, so if you could retry the connection and let me know how you get on"
My translation of the message: We screwed up by choking RDP to save bandwidth across our network, you (and presumably others) caught us out, so now we'll pretend we're the good guys and that we've discovered something wrong and we'll fix it, but don't expect us to say sorry!
I will give T-Mobile a ring today and see, I guessed it would be t-mobile as I ave a whole range of different RDP servers I connect to and none worked!
lol, T-Mobile took all of about 2 minutes to enable my RDP again, told them I knew it was there prob as I read on XDA-Developers, got to love the internet nice one NanoRuler
NanoRuler said:
Hallelujah! The age of miracles is upon us!
I've put in a complaint to T-Mobile, and out of the blue Remote Desktop started working, while I also received an e-mail from T-Mobile's tech support.
Here's an extract from the e-mail:
"I have came across someone else with this problem and we are trying a temporary fix by adding a update to your account which is on now, so if you could retry the connection and let me know how you get on"
My translation of the message: We screwed up by choking RDP to save bandwidth across our network, you (and presumably others) caught us out, so now we'll pretend we're the good guys and that we've discovered something wrong and we'll fix it, but don't expect us to say sorry!
Click to expand...
Click to collapse
RDP Port filtering or NAT misconfigured !
bhermer said:
lol, T-Mobile took all of about 2 minutes to enable my RDP again, told them I knew it was there prob as I read on XDA-Developers, got to love the internet nice one NanoRuler
Click to expand...
Click to collapse
Just realised what T-Mobile said in their e-mail "I have came across someone else with this problem" - was that you? That WOULD be funny!
Way I look at it if we don't stick together we'll get shafted by big corporations!
Used to know a guy who had something printed on the reverse of some of his business cards. It read "Doing business with your firm is like having sex: it gives one a feeling of warm bliss.....while being screwed!"
Thanks to T-Mobile I know what that feels like! Having said that I'll also categorically state the last guy I dealt with at T-Mobile knows his stuff and was very helpful.
Curious, it does lead to believe something about the ports being like group policy's that they use as the voice over ip ports only are open for WnW Max customers usually unless you scream at them after being with them for a long time. heheh
Nano, no offence mate but i've been doing similar work for years as well but it's sometimes the simple things so you can understand me asking.
you would ask a client the same thing.
NanoRuler said:
Hallelujah! The age of miracles is upon us!
I've put in a complaint to T-Mobile, and out of the blue Remote Desktop started working, while I also received an e-mail from T-Mobile's tech support.
Here's an extract from the e-mail:
"I have came across someone else with this problem and we are trying a temporary fix by adding a update to your account which is on now, so if you could retry the connection and let me know how you get on"
My translation of the message: We screwed up by choking RDP to save bandwidth across our network, you (and presumably others) caught us out, so now we'll pretend we're the good guys and that we've discovered something wrong and we'll fix it, but don't expect us to say sorry!
Click to expand...
Click to collapse
A possible solution for those of us on T-Mobile's standard web n walk
Sorry to resurrect this thread, but I thought I'd post my experiences here in case anyone else (like me) searches for a solution to enabling RDP on T-Mobile (UK at least).
I was having the same problem with remote desktop, it saying that the server was not available. I phoned up T-Mobile's helpdesk as recommended here and after getting past first line support (who didn't know what remote desktop was, and tried sending new connection settings to my phone to resolve the issue) I got through to someone who knew what they were talking about. Turns out that I'm on T-Mobile's "basic" or "handset-only" web-n-walk package, and it's not possible to use RDP on this. I assume they block the relevant ports. They told me that I could pay an extra fiver a month to upgrade to a version of web-n-walk which can handle RDP.
Well I told them I would think about it, but instead tried to find a way around it as the one or two times I need to use RDP are certainly not worth a fiver a month. My solution is probably only suitable for the more techy of us, but without much work and with no prior experience I managed to set up a SSH tunnel using FreeSSHd as a server running on my windows server (although a normal windows box should work fine - http://www.freesshd.com/) and zaTunnel as a client on my phone (http://www.zatelnet.com/zatunnel/main.php). Both programs are free.
Basically my phone takes all RDP connections and tunnels them over SSH to my windows server, which then turns them back into RDP connections. T-Mobile have no idea I'm using RDP, and if they block the SSH port in the future I can always change FreeSSHd to run on port 80 (for web). This will also work for other protocols T-Mobile might be blocking (FTP springs to mind).
Just thought I'd post this in case anyone was in my situation of needing RDP on their standard web'n'walk.
Cool! Thanks for posting your rather excellent work-around! I will certainly be referring people back to your solution.
I think T-Mobile's out of order for not allowing RDP on all plans, without absolutely clearly stating that on some plans it isn't allowed.
You're the customer and you pay for some bandwidth. Short of illegal activities, what you use that bandwidth for is none of their business.
T-Mobile Grrrr
Many Thanks for this thread.
My Remote Desktop stopped working on my phone last month but co-incidently it was around the time I was re-intsalling my server and also flashing numerous roms to my phone so thought it maybe something with that.
But then realised I could remote desktop over my wireless at home and from other networks across the net so it wasn't anything to do with config on my side. Thought either phone or network.
Flashed a rom with remote desktop that i KNEW worked and still nothing...
Thought - this MUST be T-Mobile... glad I'm not the only one.
Have sent an email and hopefully they'll enable Remote Desktop on my line.
There is no way I'm gonna start paying an extra £5 a month for something I've been using for the last 20 months as part of my package and have removed wihtout any notice/warning.
i'll tell 'em where to shove their £5 extra a month
Hey all,
So I've got a small issue. I've got a Verizon XV6800 with the MR1 Rom WM6.1, Valhalla GPS server, 3.42.50 Radio.
Internet connection sharing is not working at this point. I've gone through the winmodem and internet connection sharing cab installs, registry edits, etc. None seem to help.
I previously had a ATT tilt 8925 and had no issues whatsoever tethering it to my mac by just pairing the phone, selecting to "Using a direct Higher speed connection to reach your ISP". Starting Internet Sharing on the phone, selecting Bluetooth PAN & the default data connection, then selecting connect. Then selecting "Connect to network" On the mac through the my phone listed in the bluetooth connections. That simple.
Having installed the "Internet Sharing" cab onto the phone. Internet sharing appears to work, but the phone does not advertise this service, like the ATT tilt did on ATT's network.
I've also tried a few registry edits, and used all variations of modem scripts, and got all the dialup info from verizon directly (so I know it was right ) but could not get dialup to work either. Usually not detecting a carrier, other times lockups.
I truely want to get the bluetooth-PAN working again as it did on my tilt. Anyone have this working on the MAc with a XV6800 on verizon?
i did have it working before. I'm wondering if you might be more successful with a custom rom. Verizon installs software (at least previous roms, I haven't tested the MR1 rom) that reverts reg edits and keeps it working like VzW wants it to. This could be causing problems. First check after a soft-reset to make sure your reg edits still exist.
Also I'm sure you've tried this be in Leopard's bluetooth setup delete the phone and try again. You need to select the type of device as any device in order for leopard to see it. Can you connect the device to your mac? Try that first. If you get a BT connection non-internet connection and you change your settings delete the phone and try again. I forget some of the setting I used. Also Engadget had a how to article for BT pan using the xv6700 and Tiger most of the information is still useful. It's a couple years old so you might have a hard time finding it.
Hope some of that helps.
Cycomachead said:
i did have it working before. I'm wondering if you might be more successful with a custom rom. Verizon installs software (at least previous roms, I haven't tested the MR1 rom) that reverts reg edits and keeps it working like VzW wants it to. This could be causing problems. First check after a soft-reset to make sure your reg edits still exist.
Also I'm sure you've tried this be in Leopard's bluetooth setup delete the phone and try again. You need to select the type of device as any device in order for leopard to see it. Can you connect the device to your mac? Try that first. If you get a BT connection non-internet connection and you change your settings delete the phone and try again. I forget some of the setting I used. Also Engadget had a how to article for BT pan using the xv6700 and Tiger most of the information is still useful. It's a couple years old so you might have a hard time finding it.
Hope some of that helps.
Click to expand...
Click to collapse
As mentioned, I have tried a ton of different methods to try and use the data connection, from using dialup settings, to trying to get the Bluetooth Pan working. I've removed and re-paired the device from my mac, flashed roms, hacked away at the registry a ton of times. Nothing seems to give so far.
I've got one more suggestion, found here: http://forum.xda-developers.com/showpost.php?p=1794133&postcount=29
I'm going to give this a shot tomorrow and will let you know how it goes.
Eponymous069 said:
Hey all,
So I've got a small issue. I've got a Verizon XV6800 with the MR1 Rom WM6.1, Valhalla GPS server, 3.42.50 Radio.
Internet connection sharing is not working at this point. I've gone through the winmodem and internet connection sharing cab installs, registry edits, etc. None seem to help.
I previously had a ATT tilt 8925 and had no issues whatsoever tethering it to my mac by just pairing the phone, selecting to "Using a direct Higher speed connection to reach your ISP". Starting Internet Sharing on the phone, selecting Bluetooth PAN & the default data connection, then selecting connect. Then selecting "Connect to network" On the mac through the my phone listed in the bluetooth connections. That simple.
Having installed the "Internet Sharing" cab onto the phone. Internet sharing appears to work, but the phone does not advertise this service, like the ATT tilt did on ATT's network.
Click to expand...
Click to collapse
I was wondering if you be gracious enough to share the Internet sharing CAB i only need to get it to work thought the USB cable and on a windows box, and from what im getting you got that far... JUST not working on a mac...
if thats the case, i would be ever so greatful..
Thanks
thetaz01 said:
I was wondering if you be gracious enough to share the Internet sharing CAB i only need to get it to work thought the USB cable and on a windows box, and from what im getting you got that far... JUST not working on a mac...
if thats the case, i would be ever so greatful..
Thanks
Click to expand...
Click to collapse
You can use the link from the previous post here, and just copy the dll's and exe to the Windows directory, and place teh shortcut into the Device\Windows\Start Menu\Programs\ directory.
Eponymous069 said:
You can use the link from the previous post here, and just copy the dll's and exe to the Windows directory, and place teh shortcut into the Device\Windows\Start Menu\Programs\ directory.
Click to expand...
Click to collapse
hey, ok great, i just downloaded the file, Just one question..
The file i downloaded has about a page of Reg Key changes, you didnt mention that in your "thngs to do"
Just want to see if i am to make all those changes or not.
thanks
So, your problem is in getting the internet connection to work and not connecting it to the mac, right? Does your mac recognize the phone as a modem?
If you're using MR1 I think you might need to hard reset and the soft reset right before the Verizon customizations run. You won't be able to run their apps but there won't be software to cripple the phone.
i have the same exact issue i have a new macbook pro and the bluetooth connects however the speed is slower then dial up it works perfectly however on bootcamp apple has to change the drivers
So more results.
I tried all the registry edits, (much easier with CD-Regedit so you can make the changes on your desktop) and now internet sharing does not even allow me to select a connection type, it had worked previously.
The only thing that was missing before I made the registry changes was that when I pair the phone, in the services listed, "Network Access Point" is not one of the listed services. My old phone has this service listed, and this is how I used it, where I started internet sharing on the phone, then selected the bluetooth device (phone) on the mac and selected: "Connect to Network) and it worked flawless.
Back to the drawing board. I'm going to try next to re-flash the MR1 rom and do as Cycomachead suggested and stop verizons customizations from happening.
bryanw17, what were the exact settings you used for dialup on the mac. The modem script used is probably the most important piece.
Number: #777
Username: Phonenumber (or [email protected]????)
Password: (We know this one, not sure if it's legal to post though)
Darn, I wish I could provide more help. It is indeed possible in Leopard, I had it going before I began flashing my phone - and I no longer have a data plan to test, otherwise I'd be using it a lot more!
aparently no one with a new macbook pro can get bluetooth pan to work. I have it connected however the drivers for the new macbook pro do not provide a good connection if you search the mac forums theyve been talking about it on there. I dont use a username n password however because i use the internet sharing app for the moment i am using wmwifirouter to connect online however my xv6800 doesnt charge at the same time for some reason so u can only use it till the battery dies
So some more results.
I installed ICS and all the registry edits. Then the internet Connection Sharing did not function at all. I verified the registry settings, all were fine. So no dice with me.
So back to the drawing board.
I installed a previous rom. DCD 3.2.6, and guess what? From initial flash of the phone and initial setup, no apps installed, no hacking, ICS runs and provides a network connection to my mac perfect. I also instantly notice when I pair it through bluetooth, it allows the option of "Access this device as a network port". And "Network Access point" is listed as an offered service.
I installed newer rom DCD 3.3.4, and the MR1 Rom. Neither have ICS installed initially. I can install the two files: intshare.dll and IntShrUI.exe into the windows directory without any reg edits, and then ICS works on the phone, but then pairing the phone to the Mac, and attempting to discover teh PAN service is unsuccessful. It only is discovered as a Dialup Access device, and not a "Network Access Point".
So, It appears I can get internet Sharing via Bluetooth PAN to function on the phone no matter which rom, but have not figure out how to tell the mac, or trick the mac, into thinking the "Network Access Point" service is available.
I have pulled completed registry dumps with CE-Regedit and compared the differences between the two, which there are quite a few, but not sure how to export these differences with the program so I can apply them to the other roms registry. I guess I might try a fukll backup and then restore to the new(er) rom and cross my fingers.
I'd stay with the 3.2.6 rom. and 3.42.50 Radio, with PRI 2.03, but I can only seem to make the GPS function successfully with the MR1 stock verizon rom.
Anybody want to take the two regs files compare, and see if they can find out where we can make the change to have the phone advertise the service "Network Access Point" when being paired to the mac or PC?
On one last note. I also tried the method of restoring the MR1 official rom, and then not allowing the customizations. ICS will function, but again, not advertising the service: "Network Access Point" when pairing, so it's not recognized as a valid networking method.
Where did you get those files (intshare.dll and IntShrUI.exe) to allow ICS via bluetooth?
Nevermind, I found it on PPCGeeks.
Don't know why DCD disabled the BT DUN on ICS.
I use Missing sync, and I turned on PAN then added my phone and it shoed it as a modem when I added it, but my BT connection is fairly Unrealible compared to the USB teather on Bootcamp
i was under the impression that bt pan has been whacked on macbook pro models starting from early 2008 on. anything earlier than that and it seems to work great. does anyone know why bt pan doesnt work on the newer machines and how to get it to work?
One of the corner cases it seems HP did not design into webOS is the ability to auto negotiate a full 802.11X connection. I managed to fix this though and my touchpad is happily connected to our office wi-fi and I figure anyone else trying this might want to check out the workaround I managed.
When I attempted to configure my touchpad to connect to an office/enterprise access point, I hit a brick wall where after completing all the required steps. It was able to use the current user credentials and get to the access point itself, but failed out with a "warning, no certificate is found for this network, please contact your network administrator" type of message.
Well of course no one in our IT group had ever so much as seen WebOS and ultimately I was left to fend for myself.
The goal here is to successfully transfer the (normally auto-retrieved) 802.11X signing certificate to the touchpad so that it can properly connect to your corporate/enterprise wireless network. On other devices such as android this seems to all be automated, but on the touchpad a significant amount of manual arm-wringing was needed to get it to all work together.
Step 1: Getting a root security certificate for your company.
There are a few guides out there for various operating systems/devices which you can use. Since my office machine was windows 7, thats what I have direct experience with.
Win7 Has a built in certificate management tool, but it is not listed in any of the menus. To get to it, enter certmgr.msc into the run panel and it will open up this handy dandy little tool.
Once you have that tool open, look into the root certificate authority folder and find your company's enterprise certificate. Hopefully it will be fairly easy to spot, i.e. if you work at company with domain X, you should see something like "X Enterprise CA".
Right click this certificate and select "All Tasks->Export" which will bring up a wizard with a few different certificate formats. After much trial and error, I found that the only one the touchpad seemed to natively understand was the "Base-64 encoded X.509". Finish the export with a file name and you can find it in your default user folder.
Step 2: Transfer this file to your touchpad
This one is a no brainer, just connect the touchpad via usb to your machine where you have this file, and drag it over.
Step 3: Importing the new certificate
All you need here is any webos file manager capable of opening a file. I used Gemini File Manager, but several free ones are also available and should work.
Open the file manager app on your touchpad, and run that certificate file. This will open a certificate manager tool on the touchpad and prompt you to trust this new certificate. Once you select to trust it, it will be brought into the system and available to use for 802.11x authentication.
Step 4: Connecting to the network
At this point all you should have to do is connect to the office wireless that was giving you trouble before, and now after giving all your authentication info it should successfully connect and offer full connectivity
It seems a little convoluted but it is awfully nice to have the touchpad be fully on-line and available around the office and you only have to do it the one time, successive connections should all just work.
I've tried this at my University, but it doesn't work for my exact situation. Hopefully it will work for others too. Kudos for figuring it out! As for me, apparently WPA2 Enterprise PEAP MSCHAPV2 is a no go until the WebOS team will update/fix it....
I managed to get connected to my MS corp wireless, but will actually see if I have network connectivity a bit later (and update this thread).
its given me full connectivity here (I'm writing this on my touchpad on the enterprise WiFi right now). Its also worked for several other people here lucky enough to score one as well.
the biggest sticking point was getting the right certificate in the right (touchpad working ) format. Once I managed to get that file simply sending it around helped everyone else here get going in a couple minutes vs a couple hours it took when I was trying to sort it all out.
We use 802.1x at work without server certs. Just peap and mschap v2. I haven't had any luck connecting though. Anyone else been able to?
Looks like PEAP support is a major sticking point.
There's a tutorial here: http://www.webos-internals.org/wiki/Advanced_Wifi
(I changed some of the script as per the thread I got the link from here: http://forums.precentral.net/hp-touchpad/288229-wifi-enterprise-802-1x.html)
I tracked down the ARM wpa_supplicant package here: http://packages.debian.org/squeeze/armel/wpasupplicant/download
And the libreadline.so.6 package here:
http://packages.debian.org/squeeze/armel/libreadline6/download
.DEB packages just have .TAR files inside them so I extracted what I needed using 7Zip and used WebOSQuickInstall to copy the files to the TP.
Even after following the other directions though, I consistantly get an error saying:
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Not having much luck...
what's odd is our network looks like it does have peap set but with this certificate its working on the touchpad just fine.
it uses our exchange login info with a slightly off domain but even that has not thrown it.
The exact network configuration visible in the windows properties for the wireless link here is as follows:
Security: WPA2-Enterprise
Encryption: AES
Network Authentication: PEAP
Validate Server Certificate
Secured Password (EAP-MSCHAPv2) (Automatically use windows login/pass/domain)
Fast Reconnect
I haven't had luck with anything so far.
Is anyone willing to make a patch to fix the MSCHAPv2 problems? I'm willing to donate to your cause if I can my TouchPad to connect to my school's wireless, as it's essentially useless right now.
The network here uses WPA-Enterprise (not WPA2), and PEAP with password authentication only (no cert needed - as far as I'm aware it doesn't issue one to the phone).
I managed to get the TP to say "no network with that name and security method" found when I had the protocol set to IEEE801X, it doesn't do it when I set it to WPA-EAP though.
Essentially, using (what I believe to be) the exact same settings that work with my SGS2, doesn't work with the TouchPad.
It looks like at best the enterprise stuff is kinda half baked. If you need a certificate, webos is capable of *using* one, but not generating it. If its non certificate based, it seems to just fail out entirely.
Have you guys who are having the failures had luck with other devices like laptops etc? if so, what are the settings used to establish that successful connection? It seems like the touchpads are *capable* of mantaining peap/mschapv2 connections, as that is the setup my office uses, but for some reason without the certificate requirement it just is glitching out and won't establish the connection in the first place
eltee said:
It looks like at best the enterprise stuff is kinda half baked. If you need a certificate, webos is capable of *using* one, but not generating it. If its non certificate based, it seems to just fail out entirely.
Have you guys who are having the failures had luck with other devices like laptops etc? if so, what are the settings used to establish that successful connection? It seems like the touchpads are *capable* of mantaining peap/mschapv2 connections, as that is the setup my office uses, but for some reason without the certificate requirement it just is glitching out and won't establish the connection in the first place
Click to expand...
Click to collapse
My Windows7 laptop and my WP7 Samsung Focus both securely connect to the network fine. My TouchPad is the first device I've ever heard of having issues connecting.
Hell, my roommate even has his PS3 and XBOX connected.
Thanks OP! Method works on Swansea University Eduroam.
bump now that we have a 3.03/04 update
anyone know if it worked?
Installed the WiFi Certificate but still no luck.
Any other workarounds out there?
Just updated (manually) to the leaked 3.0.3 version and it's resolved the Enterprise Wifi connection issue.
Confirmed, my WiFi works. Enterprise mschapv2 PEAP without certificate. 3.0.3. Now I can leave my laptop at home and use splashtop if I need anything.. *rock on*
I can also confirm that the certificate issue has been solved in 3.03, but now I can't set a proxy, has anyone been able to?
PEAP/MSCHAPv2 fixed with "official" 3.04 OTA too
PEAP/MSCHAPv2 authentication has stayed fixed with the official 3.04 OTA update.
I've just checked that I can connect to an eduroam connection configured this way at a UK university, which the TouchPad couldn't do before.
professordes said:
PEAP/MSCHAPv2 authentication has stayed fixed with the official 3.04 OTA update.
I've just checked that I can connect to an eduroam connection configured this way at a UK university, which the TouchPad couldn't do before.
Click to expand...
Click to collapse
awesome news, I will be testing mine out today when I get to school.
update: I was able to connect at my school, but I had to uncheck the cert box to get it to work.
Yup, i removed my custom certificate on 3.04 and re-joined the access point. It had some new options about authentication built in and sure enough just worked, no issues.
Looks like the little crazy work-around won't be needed anymore
I've recently purchased a Galaxy Note II, i'm having an issue communicating to the device over wifi on my home network.
Wifi works fine in every other way.
Some examples of the issues I'm having:
Wifi Sync with Winamp won't detect my device unless I enable content sharing with DLNA
Wifi File explorer won't work on this phone, it's as if the phone is refusing connections over port 8000 with no user interaction
Device cannot be pinged (I'm not sure if my Desire HD responded but it never had any other the other issues)
I don't have any privacy guard type apps installed, I am rooted and I did have AdAway installed but I have tried it both with the host file installed and without.
I'm a bit lost here, and googling just returns results from 100's of people who can't connect to WiFi.
Ok, this isn't going to help anyone who comes across the same issue but wifi explorer is now working, and the device is responding to ping requests. Winamp sync still needs the DLNA stuff turned on.
I'd have liked to provide a solution but i've absoloutly no idea why it's now working, sorry.
I cannot connect to a single wifi network. Home/work/anywhere, I've read where you can enable the secret menu and do some trickery through the phone but I have the Verizon Note 2 and you can't just dial a number and get to the secret menu.
Once I did try and download this zip file with some wifi files in it that I had to overwrite on the system partition using ES file explorer (found an article covering this exact problem) but this did not fix my problem.
not to mention i've done a pure 100% factory restore to 4.1.1. to no avail. ran custom roms. no avail. Its getting very frustrating. I am unlimited so I care less than others, but some of my apps are used over the network ie: unified remote for my computer hooked to my bigscreen.
When I use a rom, it just tries to connect for one instance then doesnt do anything. on the factory image it will say authentication error every time.
I've gotten my phone to connect to my home wifi ONCE and it was very crappy connection, would lag while using the cursor on the bigscreen.
Any help would be greatly appreciated.
I'm very familiar with following directions and rooting/romming or even some adb commands. Let me know if there is anything I can do to remedy this situation. Thanks!!!!
Kalvin
Why is Samsung not fixing this issue?
after doing some more research everything i've found points at the problem being Wireless N.
I havent had a chance to test it out on my own yet as I am still at work but That is fine, I can change my wifi at home to G and be ok with that, but in the end that means I will not be able to connect to work/public places ever as long as they are wireless N.
Come on get with the program Sammy!!!!
Kalvin