Database Users

Disable WPA2 in WM 6.1 device

Hello to everybody. I tried to search this forums, but didn't find the solution.
Is it possible to disable WPA2 wifi authentication in windows mobile 6.1 device? I have issues with connecting to WPA2/AES network (device crashes to black screen). Manual setting to WPA/TKIP does not work, because it is overrided with WPA2/AES.

Some information here on the MSDN website:
http://msdn.microsoft.com/en-us/library/aa916274.aspx
There doesn't seem to be anything to disable WPA2 though

Thanks for the links. But after long time googling and reading some technical stuff, I am more and more convinced, that it is hardcoded into wifi drivers and it isn't possible to change it .
Better solution should be use of correct-WPA2-working driver, but I am neither programmer, nor experienced cooker to use driver from different type of WPA2-working device with same wifi chip.
EDIT: I found, that it crashes before showing of login dialog (PEAP auth), so that must be problem with WPA2 pre-authenication.

torrentonly said:
Thanks for the links. But after long time googling and reading some technical stuff, I am more and more convinced, that it is hardcoded into wifi drivers and it isn't possible to change it .
Better solution should be use of correct-WPA2-working driver, but I am neither programmer, nor experienced cooker to use driver from different type of WPA2-working device with same wifi chip.
EDIT: I found, that it crashes before showing of login dialog (PEAP auth), so that must be problem with WPA2 pre-authenication.
Click to expand...
Click to collapse
I have WPA2/AES working on my Kaiser with the (almost) stock 5.2.19212 ROM. I did update the WiFi driver in my kitchen though (TNETW1251.dll version 3.55, dated 10/06/2008). I have never had any issues with WPA2 though, even before I upgraded to WM6.1.
Andy

I have Vox and it crashes with every ROM, original & custom without difference. Mainboard replacement didn't solve this problem, so that must be software issue. Where did you get that updated TNETW1251.dll? Here I only found patched one for ICS.

torrentonly said:
I have Vox and it crashes with every ROM, original & custom without difference. Mainboard replacement didn't solve this problem, so that must be software issue. Where did you get that updated TNETW1251.dll? Here I only found patched one for ICS.
Click to expand...
Click to collapse
I can't remember where I got it from originally - more than likely a post in the Kaiser ROM Development forum. I am not sure its the same driver on the VOX but here it is anyway (just delete the .zip extension).
Andy

Too bad, another driver for same wifi chip doesn't work (doesn't load on startup). Maybe because of different chipset. But thanks anyway.

SEUS problem (I have searched the forum)

Just as the topic says. I saw a couple of people claiming to have used the seus to update and decided to try. I had the stock RA2 and wanted RA3.
When I connect the deivce, seus cannot recognize it. It makes several attempts (with the sound for new device found/unplugged) and then says that it could not recognize it. During this time the screen of the X1 flickers from the coloured stripes to a balck screen and there are multiple ActiveSync icons aperaing on the taskbar (all grey).
I have XP Pro SP3 03/09. Most of the topics I found were from people with Vista.
Any ideas? Now, I'm stuck with the stock RA1 until I find a solution.

I noticed something else. Just after the coloured stripes appear, there is a screen that pops up briefly and says "no image file!". After I plug the usb in, the bar with the 0% appears for a short moment, then the scrren goes black and returns to the coloured stripes. The cycle repeats all the time.
What is that "there is no image file!"???

orelsi said:
Just as the topic says. I saw a couple of people claiming to have used the seus to update and decided to try. I had the stock RA2 and wanted RA3.
When I connect the deivce, seus cannot recognize it. It makes several attempts (with the sound for new device found/unplugged) and then says that it could not recognize it. During this time the screen of the X1 flickers from the coloured stripes to a balck screen and there are multiple ActiveSync icons aperaing on the taskbar (all grey).
I have XP Pro SP3 03/09. Most of the topics I found were from people with Vista.
Any ideas? Now, I'm stuck with the stock RA1 until I find a solution.
Click to expand...
Click to collapse
Create a "real" administrator account, log on to that account, installation shall work fine...should work unless your R3A for your country hasn't been released.
Also, your current account is not admin even thought u mgiht think it is. It's usually the case.

i had the same problem, see this...
http://forum.xda-developers.com/showthread.php?t=514953

poetryrocksalot said:
Create a "real" administrator account, log on to that account, installation shall work fine...should work unless your R3A for your country hasn't been released.
Also, your current account is not admin even thought u mgiht think it is. It's usually the case.
Click to expand...
Click to collapse
I am the administrator.
Sapa13 said:
i had the same problem, see this...
http://forum.xda-developers.com/showthread.php?t=514953
Click to expand...
Click to collapse
Thank you for this, but I want to use SEUS for the update.

I had the same problem on my PC using Vista, however when I used my other PC that has XP it worked fine.
Obviuosly I don't know which you are working, but if you can give both a try...

orelsi said:
I am the administrator.
Thank you for this, but I want to use SEUS for the update.
Click to expand...
Click to collapse
http://www.computerperformance.co.uk/vista/vista_administrator_activate.htm
1. Logon to Vista using your normal username and password.
2. Click on the Start button
3. Click on Start Search.
4. Type, cmd.
5. Right-click cmd, select 'Run as administrator' from the shortcut menu.
6. In the black 'DOS box', type the following at the command line:
Net help user
7. The idea of the last command is just to observe the options for Net User. In particular, examine the syntax to set the password.
8. The next instruction is the crucial command. I have chosen password = p£ssworD, you may want to choose different characters.
9. Net user administrator p£ssw0rd
10. Net user administrator /active:yes
11. Check the message : The command completed successfully
12. Switch User, or logoff
13. Logon as Administrator Password p£ssw0rD (Your password may be different!)
Trap1: There should be no space between the word 'active' and the colon.
/active :yes is wrong.
/active:yes is correct.
Trap2: You need a forward slash before /active
Net user administrator active:yes is wrong
Net user administrator /active:yes is correct
Thanks to Rob Hilton for pointing out this trap.
Trapx: Pay close attention to the command, it should be active, not activate.
I thank Ben O'Sullivan for correcting this activate --> active error.
Well, I also thought that I was the administrator until I realised that I was not... I am not sure if this is the case for you but maybe check again?
EDIT: Nevermind, you got an XP, I think it's most likely that you got a lot of software that conflicts with activesync and it's probably impossible to find the culprit
I would just update it with some else's computer..

the "no image file" warning upon boot is because there is an SD card in the phone, but no image on the SD card that can be used to update the phone

orelsi said:
I am the administrator.
Thank you for this, but I want to use SEUS for the update.
Click to expand...
Click to collapse
Report your current ROM. It is possible that your phone is in USB to PC mode instead of ActiveSync mode. It is also possible that your ROM has not been officially released.

kirkie said:
I had the same problem on my PC using Vista, however when I used my other PC that has XP it worked fine.
Obviuosly I don't know which you are working, but if you can give both a try...
Click to expand...
Click to collapse
I said in the OP that I got XP Pro SP3
poetryrocksalot said:
I think it's most likely that you got a lot of software that conflicts with activesync and it's probably impossible to find the culprit
Click to expand...
Click to collapse
I formated the SD. Reinstalled the ActiveSync. Did a hard reset. No change.
ActiveSync is working fne when I connect the phone to the PC. It doesn't work when I try to update it via SEUS.
I t really is getting frustrating . Today I needed my GPS, but when I took the phone I had forgotten that I formatted the card earlier..........
ferjan said:
the "no image file" warning upon boot is because there is an SD card in the phone, but no image on the SD card that can be used to update the phone
Click to expand...
Click to collapse
I formatted the card FAT32. That should solve any issues. In order there to be an image for the update the SEUS should connect to the SD and copy that image in the first place.
poetryrocksalot said:
Report your current ROM. It is possible that your phone is in USB to PC mode instead of ActiveSync mode. It is also possible that your ROM has not been officially released.
Click to expand...
Click to collapse
The phone is in ActiveSync mode. As I said when the SEUS is trying to identify the phone there are multiple ActiveSync icons appearing on the taskbar. All of them are innactive (grey).
I use the official RA2. Updated through SEUS.
I know there is a stupid little issue that I am overlooking. It is something obvious every time. I can't find it this time though....

What I meant was that the ROM for you country/language has not been released. And I meant pc software that conflicts with active sync, if this is not the case then obviously R3A is not release.

poetryrocksalot said:
What I meant was that the ROM for you country/language has not been released. And I meant pc software that conflicts with active sync, if this is not the case then obviously R3A is not release.
Click to expand...
Click to collapse
That shouldn't conflict with SEUS recognizing my device though, right?
Here comes another day of experimenting to find the answer .

hello m8 i had once this problem when i a hardspl and then i wanted to update from seus.
what i did? i run the stockspl -> flashed a stock rom >then update froms seus.
it happened to me 2 times when i tried to flash custom roms or official roms via flash mode. the problem was solved both times
i dunno if that helps but u could try.

lunaticxgr said:
hello m8 i had once this problem when i a hardspl and then i wanted to update from seus.
what i did? i run the stockspl -> flashed a stock rom >then update froms seus.
it happened to me 2 times when i tried to flash custom roms or official roms via flash mode. the problem was solved both times
i dunno if that helps but u could try.
Click to expand...
Click to collapse
The thing is, I never flashed custom ROMs on this device. All the different ROMs I tried were flashed on another X1. The only thing I have done is hard reseting 10+ times and updating to RA2 via SEUS one time. That's it.
I guess it could work, but I will do it as a last resort. There is something wrong with my phone and I want to know what or at least how to fix it.

Like I said, your R3A has not been released. I will keep saying this until you tell me that you know 100% that the R3A for your Xperia has been released.

I too had the same issue. I also couldn't install the bootloader to load a custom ROM either. Skipping several hours of swearing, soft boots and repeatedly trying the same thing, I discovered the problem was with Kaspersky.
After disabling Kaspersky, I was able to load the Generic UK R3A off the SD card. Never got around to trying SEUS again, but have a go at disabling any internet security software you have.

I guess it's windows vista software issues (NOT POCKET PC SOFTWARE).

I have Windows XP on my laptop and whilst i could flash my x1 fine with the older SEUS client, since they upgraded to the new fancy looking client i face exactly the same problems. The x1 goes in USB mode and SEUS is starting/terminating several activesync processes in the background and then it fails.

Clear the Checkbox
I have Windows Vista Business running on my laptop.
I also have the problem of SEUS cannot indentify my X1 (but sometimes, it did recongize though very low succesful rate).
After clear the Checkbox : USB Connection allowed, in the Vista Mobile Devicecenter (before connecting the USB cable to X1), the SEUS can identify my X1 and I have tried it twice successfully.
Hop it can help.

minglee said:
I have Windows Vista Business running on my laptop.
I also have the problem of SEUS cannot indentify my X1 (but sometimes, it did recongize though very low succesful rate).
After clear the Checkbox : USB Connection allowed, in the Vista Mobile Devicecenter (before connecting the USB cable to X1), the SEUS can identify my X1 and I have tried it twice successfully.
Hop it can help.
Click to expand...
Click to collapse
Confirmed this trick. Just yesterday I was trying to update my X1 to R3A, but SEUS couldn't recognize my phone is connected. I've tried to activate built-in windows Administrator account, because it helped me when I was updating to R2A. But this time it didn't work. I was pretty confused, but after few minutes of searching on forum I found suggestion about uncheck that "USB Connection allowed" option. I did it, connected the phone and SEUS recognized it in a second. Tried 3 times and it worked like a charm.
I am running on Vista Home Premium 32bit.

Wifi connection problems.

I am trying to connect to my university's wireless.
We have two different wireless ssid's that i can connect to with my laptop.
The first, called UBC is unsecured, but when you connect, it takes you to a web page where you enter your username/password.
The second, called ubcsecure, can authenticate with either WPA2 or WPA ( it shows up as WPA2-Enterprise).
The encryption method is AES for WPA2, and TKIP for WPA.
EAP type: PEAP v0 , Authentication protocol is MS-CHAP-V2
there is an option for mutual authentication using a certification server:
secure.wireless.ubc.ca
I am unable to connect to either using the stock HTC magic ROM, the HoFo community rom, and most recently, myHero 1.0.1
I have tried editing /system/etc/wifi/wpa_supplicant.conf to include
network={
ssid="ubcsecure"
proto=WPA
key_mgmt=WPA-EAP
pairwise=TKIP
group=TKIP
eap=PEAP
identity="[email protected]"
password="password"
phase1="peaplabel=0"
phase2="auth=MSCHAPV2"
}
Any ideas as to how to connect?

Data wipe.
Try to reset your phone's basic settings.
It could rebuild the information necessary to acquire the specific IP from their connection.
Manually entering the data couldn't hurt either. This is something that usually I would consider consulting the school about. Privatized internet connections could cause a number of issues for those seeking to utilize Wi-Fi.
The NAT settings might be too strict to support a handheld device.

Me too!
have you found any other solution??
i m here in ubc as well with my htc magic 1.5
when i'm trying to connect to ubc,, it keeps requiring the ip but doesnt connet
and ubcsecure doesnt even show up!
is really frustrating not being able to use internet in universityyy..
i thought by activating the wpa enterprise will work for the ubcsercure, i guess not??
will any of the heros rom work??

Im having this problem too.. anyone find a fix?

I have no idea why but ubcsecure seems to be working using JesterBlur ROM. http://forum.xda-developers.com/showthread.php?t=567122

it works on the Dream? or sapphire? I don't think it matters but... be interesting to know

Dream. Theres a version for the Sapphire. Maybe give it a shot? ubcsecure still working here.

Ask for working setting
absolutcamper said:
Dream. Theres a version for the Sapphire. Maybe give it a shot? ubcsecure still working here.
Click to expand...
Click to collapse
Did you use the UI setting or you edit the "wpa_supplicant.conf" file manually?
would you please send us your "wpa_supplicant.conf" file or its ubcsecure part? it would be the great help to have a working setting.
Cheers,
Ali

I used the UI that came up during first boot. How can I get to that file?

the wpa_supplicant is in /data/misc/wifi. But considering how it works using the ui settings, i dont think changing the config file will work...but please still post it.
I also tried replacing the wlan.ko from the jesterblur rom... and doesnt seem to be compatible with magic which is apparently normal because there is a patch for magic users that fixes wifi apparently. I will try the wlan.ko from the fix soon probably to see if it works.

Hi guys,
I'm at UBC with the same problem (I can't even connect to the regular UBC network). I went to the UBC help desk and they basically told me that they don't support android at all. The funny thing is I can connect to the fatport network with no problems but cannot connect to ubc, ubcsecure or eduroam networks on campus. I'm currently runnning on Cyanongen 4.2.4 (waiting for 32a kernel to upgrade to 4.2.5) on a rogers htc magic.
Anyway, the point of this post. If anyones interested in meeting up at UBC to find a solution to this problem it'd be great. I'm hoping we can eventually create a package of some sort that'll fix any android phone but lets focus on fixing the current prob first.
Also @fnkaze - aren't the dream and sapphire the same thing?

Er, i think the dream is the G1 and the sapphire is the G2 aka the rogers magic... well i think the dream has a differnt wifi driver? maybe.. thats the problem
I think the reason why they dont support android is because the stock rogers rom doesnt have native wpa2 support i think.... but the custom roms should have it.. the hero rom does have it... at home my wpa2 wifi works fine
I can also connect to fatport, i think the eduroam is also using the same thing...tho ive heard eduroam seems to work on the rogers rom at different univeristies..
I still have yet to try the jester rom wifi driver tho, ill try it soon...

Thanks for the clarification. And the reason eduroam works at other universities is because the WPA encryption settings are based on the uni's actual/main wireless network. So at different universites the authentication protocols might be a bit different.
What phone do you have? The dream or the magic? The jester rom doesn't work on my magic.

i have the magic, but i think it should work on the magic, they also have a seperate patch to get Wifi working for the it.. so im assuming its possible..

So yeah, Concordia University in Montreal has the same WPA2-Enterprise and this is how I got WIFI to work on my Magic (with HoFo's Sense UI ROM, would still probably work with a rooted 1.5/1.6 ROM)
In fact it will probably work with any rooted Dream or Magic
Remember you need your phone to be rooted for this to work, you will also need to have the drivers installed for your phone from the Android SDK.
- Go into recovery mode
- mount the /data/ folder
Code:
adb shell mount /data
- With ADB Pull the /data/misc/wifi/wpa_supplicant.conf file to your computer (in this example it will go to the tools folder where you have your androidsdk)
Code:
adb pull /data/misc/wifi/wpa_supplicant.conf .
- Make a backup of your conf file in case you mess something up
- Edit it and add in the configuration settings given by your University for Linux wpa_supplicant.conf files, so in your case
Code:
network={
ssid="ubcsecure"
proto=WPA
key_mgmt=WPA-EAP
pairwise=TKIP
group=TKIP
eap=PEAP
identity="[email protected]"
password="password"
phase1="peaplabel=0"
phase2="auth=MSCHAPV2"
}
- With ADB Push the wpa_supplicant.conf from your computer to the /data/misc/wifi/ folder
Code:
adb push wpa_supplicant.conf /data/misc/wifi/
mydewji13 said:
UBC help desk and they basically told me that they don't support android at all.
Also @fnkaze - aren't the dream and sapphire the same thing?
Click to expand...
Click to collapse
Honestly that person at the helpdesk probably doesn't even know what Android is. If they says they don't support Android at all, well using their logic any Linux distro using wpa_supplicant.conf isn't supported which OBVIOUSLY isn't the case.
And no the Dream and Magic are far from being the same device.

Thanks!
I'll try this solution and see if it works. Will post back to let you know how it goes.

Hi,
Ok, I just finished installing the sdk, fixing udev to recognize my phone etc...
The problem I'm having is that everytime I run:
Code:
adb shell mount /data
I get the following error:
Code:
mount: cannot read /etc/fstab: No such file or directory
Help?!?!

NVM after reading the adb -help i tried this:
Code:
adb pull /data/misc/wifi/wpa_supplicant.conf /home/myuser

Ok something really wierd happened...I pushed a new wpa supplicant file and the rebooted the phone and it stopped seeing wireless networks! But ubcsecure showed up as a known network. If I long press it an 'forget it' I can see networks again, but still cant connect to any ubc network?
WTF>?

Is there anyway I could use by ubuntu wpa_supplicant settings? Anyone know where the file is on Karmic? b/c I cant find it at all

Android USB Debugging / Sorry! The application settings (process com.... issues

Hi,
Ive checked the forums but i cannot seem to find a thread that answers my question. Maybe this has not been asked or people have incorrectly titled their threads.
Ive just updated to the latest radio (no issues).
Changed my ROM to Chuckys GTX lite (no issues). Also used DUTTY Creme V4
I have then booted Google's android, using Darkstones 7/8/10 build of Froyo.
It boots into Android fine but upon start up i always get the message:
'sim card changed' then 'sorry! The application settings (process com.android.settings) has stopped unexpectedley. please try again'
which i then click force close
Im also having trouble finding the correct software to use USB mode to transfer my files to the phone in Android - I think i now have to use HTC Sync but HTC's site asks for a serial,.... which obviously i cannot download. I just seem to default to 'USB Debugging' which does nothing for me.
An help would be appreciated
Thanks

i also can not connect my HD2 with this build via USB...
any idea?

Currently using ChuckyDroidROM and the FroyoStone 07.08.2010 build, installed "Automount" from the Android Market, disabled "USB Debugging" and set Automount to enabled, and it works perfectly fine now, Windows XP, Windows 7 and Ubuntu 10.04 all see the microSD card and can access it perfectly

iiNFAMOUS CHRiS said:
Currently using ChuckyDroidROM and the FroyoStone 07.08.2010 build, installed "Automount" from the Android Market, disabled "USB Debugging" and set Automount to enabled, and it works perfectly fine now, Windows XP, Windows 7 and Ubuntu 10.04 all see the microSD card and can access it perfectly
Click to expand...
Click to collapse
Amazing, thank you very much, been serching for something like this for hours. You have made my day!!
has anyone else had the error in my OP, I dont know if its having any effect on the OS but its good piece of mind to know what it is.
Cheers

thanks a lot...gonna try right now...

great...it works...

now I can access my SD card, but when I paste something and then disconnect the USB cable, nothing appears in File Explorer... For example: I tried to make new folder "music"and to put there some music files. I did that, but then I couldn't find the folder... Any suggestions?

muscular said:
now I can access my SD card, but when I paste something and then disconnect the USB cable, nothing appears in File Explorer... For example: I tried to make new folder "music"and to put there some music files. I did that, but then I couldn't find the folder... Any suggestions?
Click to expand...
Click to collapse
Be careful about transferring files to your sdcard via android...
there's a reason DarkStone probably disabled it...
I was on older builds that supported this and ended up messing up the filesystem of the card... nothing a "repair without formatting" can't handle, but still takes some time to figure out...

Im running HSPL3, ChuckyROM GTX Lite, JMZ DualBoot and Android 2,1 i believe... The Desire one w. sense...
Everything works perfectly, but theres no connection trough the USB only charging.
Tried to turn op USB debugging and install Automount (No luck)
Alså tried to change the connect to pc setting fra just chargin to all of the other options... Still no luck
Anyone have any ideas?

I'm having same issue as OP.
Went from Desire v5 to Froyo darkstone (7/8), and no data connection, and same error "Sorry! The application Settings (process com.android .settings) has stopped ..etc when I try to accept the "Sim card changed " notification.
When I try to play with APN settings, it just constanlty says : Connection failed due to incorrect APN settings on Mobile Network screen.
There was a warning with this build about limited or no data, but didnt think it would not work at all, I had a cracking down rate with Desire V5, but would like to carry on running this Froyo build.
Any help?

To OP:
Just seen the following in the build thread:
Update:
a) APN settings crash, I will fix this asap.
Last edited by DarkStone1337; 8th August 2010 at 12:03 AM..
Re-EDIT!
Check this: worked for me..... http://forum.xda-developers.com/showpost.php?p=7514490&postcount=1179

Lol, I deleted the apn settings before the backup step. Lost my o2 internet now. Anyone had the issue of the mobile phone signal icon dropping every min it so. It will show full or half etc signal then the next min will show no signal bars then after another min or so full or half etc again. I can still make calls when the phone shows no signal though. This is with chucky gtx lite and darkstone latest froyo build. Same was with duty Rom also.
Another issue I've found is the screen going sort of black and white inverted and really bright. Anyone else got this if just me, I have to reboot the phone to fix. It's only happened twice though in a week.
Sent from my HTC Hd2 Android
using XDA App

USB Connection Sharing Broken

Hey everybody.
Since updating to the OTA 1.25.405 update, USB internet connection sharing seems to be broken. It used to work before the update.
Phone gets registered as a USB 3G modem
Connecting works, getting an IP (192.168.100.100) works.
... but the default gateway (192.168.100.254) is unreachable when using the connection, so actually retrieving data is not possible.
I'm running the stock HTC Rom on a rooted wildfire - see attached file for software details.
Is anyone else experiencing this behavior?

Have you tried on several OS yet ?
It works for me, as we figured out on IRC yesterday, but not 100% sure of my ROM. Systeminfo shows Puzzle ROM but i am sure i used the RUU from shipped-rom then a backup of my data.

Yep, same behaviour on several OS'es. Device registers fine, but default gateway does not respond.

Forceflow said:
Hey everybody.
Since updating to the OTA 1.25.405 update, USB internet connection sharing seems to be broken. It used to work before the update.
Phone gets registered as a USB 3G modem
Connecting works, getting an IP (192.168.100.100) works.
... but the default gateway (192.168.100.254) is unreachable when using the connection, so actually retrieving data is not possible.
I'm running the stock HTC Rom on a rooted wildfire - see attached file for software details.
Is anyone else experiencing this behavior?
Click to expand...
Click to collapse
This happened to me after an OTA upgrade
I am doing a factory reset tonight and will post the result if it makes things work again (albeit losing my data)

The same problem with USB connection sharing
http://cleanimport.xda/index.php?threads/802404/ - Here I describe exactly the same problem I also have a rooted (unrevoked) wildfire with the original rom with update 1.
What I discovered about it is that the problem does not exist until first restart after a hard reset (factory defaults). I am in the Polish gsm provider Play.
Please help us as I believe there is more of us.
Greetz,
Bronek

Wildfire problem with USB sharing / tethering solved
shipped-roms.com/shipped/Buzz/RUU_Buzz_HTC_WWE_1.37.405.1_Radio_13.53.55.24H_3.35.19.25_release_151892_signed.exe
THe problem existed in 1.25.405.1 ROM . It does not exist after installing the 1.37.405.1 to which I give link above. It is a later version of original ROM. It includes Polish, Romanian, English and STH cyrylic alphabet.
I installed it from an WinXP machine with drivers from the SD card. I encountered problems trying to do it from Win7 originally.
Greetz!
EDIT: Though I experienced some problems with accessing the app market after flashing 1.37.405.1.

same problem here
the same story, after update to 1.25.405.1 sharing stopped working
funny - among many failed attempts to connect, one time was successful!