Am I the only person who cannot access the FTP right now?
Works fine here..
if you use "peerguardian" or other IP Blockers.. you have to allow it as its blocked..
Thanks; yeah I realized when I got home that it was probably just my work's proxy server.
Could you please give me the path to change my setting to allow me to get contacted with the FTP server. Thanks
Related
Okay.. I have read and read and my eyes are bleeding!
In WM5, I could specify the smtp port in Pocket Outlook by adding the port number to the end of the smtp server (i.e. smtp.blahblah.com:27)
For some reason when I set this in WM6 (Black 1.2) it still tries to connect to port 25. I have verified this behavior as I admin the mailserver I am trying to connect to.
So.. Am I missing something or is this broken in WM6?
Regards
try using cwmx.com as your smtp server. you are on cingular right?
spiritofseth said:
try using cwmx.com as your smtp server. you are on cingular right?
Click to expand...
Click to collapse
Actually, I know I can use Cingular's smtp server but I would rather use my own as it's more secure and I can debug any delivery errors.
dbaser said:
Actually, I know I can use Cingular's smtp server but I would rather use my own as it's more secure and I can debug any delivery errors.
Click to expand...
Click to collapse
I had a similar problem and it was not WM6 but rather the ISP connection. Using a non standard SMTP port (gmail) through WIFI works fine specifying the addressort in the account config. The same with T-mobile service gets blocked.
In my case it is not a WM6 issue.
mfabre said:
I had a similar problem and it was not WM6 but rather the ISP connection. Using a non standard SMTP port (gmail) through WIFI works fine specifying the addressort in the account config. The same with T-mobile service gets blocked.
In my case it is not a WM6 issue.
Click to expand...
Click to collapse
Well.. It worked last week in WM5 flawlessly. And when I set the port to 27 I see the phone connect on the SMTP server to port 25 as if it just disregards the port number and connects to 25 no matter what.
Really strange. Perhaps is the ROM release? I am using VSWM from 03/20. I just tested again and my authenticated SMTP to smtp.gmail.com on port 587 are going out without problems.
Let us know if you find the problem.
Just tested using WiFi and it tried port 25 even tho 27 is specified. Naturally my ISP blocks 25 so it borks out. Something is amiss here... maybe a registry setting? Maybe someone can check HKLM\Software\Microsoft\Inbox\Svc\ and see if there is a SMTP setting. Or maybe the mailtrans.dll has 25 hard-coded in the ROM I am using?
*shrug*
dbaser said:
Maybe someone can check HKLM\Software\Microsoft\Inbox\Svc\ and see if there is a SMTP setting.
Click to expand...
Click to collapse
No SMTP key in mine. In fact, I did search the registry for the gmail smtp information and could not find it. It seems to be stored somewhere else.
Ugh!
So... I deleted and recreated the email account...
And it WORKS now!!! I say WTF ever
Thanks for all the input peeps... much appreciated.
-db
Change to SMTP Port number REQUIRES a new account in WM6
I scoured the next beforehand and discovered that you can't simply tack on a ":XXX" port number to your SMTP server. it actually requires that you delete the account and re-create it with the port number string.
I figured this out once before, but then of course, forgot it and when setting up my email on my new Dutty 6.1 rom (r0xors!), learned the hard way again.
Hope this helps,
-Humbert
HHumbert said:
it actually requires that you delete the account and re-create it with the port number string.
Click to expand...
Click to collapse
Thanks Humbert! This did the trick for me on my Polaris and for my colleague on his Tytn II.
Regards, Wouter
deechte said:
Thanks Humbert! This did the trick for me on my Polaris and for my colleague on his Tytn II.
Regards, Wouter
Click to expand...
Click to collapse
Cool. Glad to have helped out.
-Humbert
there's no need to erase the account, just go to the email settings on pocket outlook and ad ":xx" the outgoing server. example "mysmtp.com:27"
worked fot me in my htc touch.
I have been trying to get my 8525 to do OTA Push Mail from our corporate Exchange 2003 SP2 server here where I work. I am the admin so I have access to the Exchange server and all settings are correct on the server itself to deal with OMA.
I can use the web browser of my 8525 and actually browse to our server and view both OWA and OMA directly, but when I configure the server through Activesync it always comes back with error code 80072ee7 (server name not resolved) error.
I am running vp3g's official v3 AT&T rom, and radio 1.48 if that matters. But here's where I think my problem lies and maybe someone with more experience regarding this can correct me if I'm wrong. We are running our OWA site on a high port number above 50000. We also have the OWA site under a subdirectory of the server. When I configure the server in Activesync, I enter the servername, port number and path to the OWA site, but once AS fails and I look at the server setting I find that it has dumped any path information and only keeps the server name and port number info.
So am I correct in assuming that M$ direct push only works with a server where the OWA site exists off the root directory of the IIS server? Or can it support paths into the site?
Actually push email relies on the Microsoft-Server-Activesync web application, and has little to do with OWA/OMA. I seem to recall that specifying port numbers and/or directory paths won't work though... May I ask why you're running the Exchange web services in such an unusual manner? Are you hosting other sites in that same IIS server as well?
kltye said:
Actually push email relies on the Microsoft-Server-Activesync web application, and has little to do with OWA/OMA. I seem to recall that specifying port numbers and/or directory paths won't work though... May I ask why you're running the Exchange web services in such an unusual manner? Are you hosting other sites in that same IIS server as well?
Click to expand...
Click to collapse
Actually that's the way it was set up before I started with the company. We have outside sales people that use the site and they felt it would be slightly more secure if it wasn't sitting on port 80 like most web sites. The boss won't let me change the port number at this time.
So activesync on the 8525 won't allow a port number? I thought it would because it keeps that in the server config info it'll dump any path info, but I figured out the path was not needed after a little tweaking. I just can't do anything about the port at this time.
I'm with kltye... don't think push has much (if anything) to do with OWA/OMA. It runs over port 443 (https). I believe it actually starts on port 80 (http) then switches to 443, but I'll spare you the ugly details on that one. Only need to know that for firewall config purposes.
Drop the port # and path and see how that goes.
Codevyper said:
Actually that's the way it was set up before I started with the company. We have outside sales people that use the site and they felt it would be slightly more secure if it wasn't sitting on port 80 like most web sites. The boss won't let me change the port number at this time.
So activesync on the 8525 won't allow a port number? I thought it would because it keeps that in the server config info it'll dump any path info, but I figured out the path was not needed after a little tweaking. I just can't do anything about the port at this time.
Click to expand...
Click to collapse
Security through obscurity eh?
I'm with vp3g as well: doesn't the https site run over 443? If it doesn't, maybe you can create a new Website and use the same settings as the original Exchange-Activesync web app, but have it listen on 443 for https. Are you able (i.e. "have permission") to open up port 443 on your corporate firewall?
Just did a quick perusal of my Exchange Server... appears as though push is an extension of OMA. If you don't have a Microsoft-Server-ActiveSync virtual directory off the Default Web Site (or some site listening on ports 80 & 443), you may be hosed.
Possibly related, but do you have a trusted SSL cert installed on the server? Without that, you might have a problem connecting.
vp3G said:
Just did a quick perusal of my Exchange Server... appears as though push is an extension of OMA. If you don't have a Microsoft-Server-ActiveSync virtual directory off the Default Web Site (or some site listening on ports 80 & 443), you may be hosed.
Click to expand...
Click to collapse
Yeah that's what I figured. I have the ActiveSync virtual directory within the Default Website along with OMA, but the server is listening on ports 60000 & 443 rather than the typical port 80.
You would think there would be a registry hack for AS on the mobile device whereby you could specify a non-standard port for syncing.
TaurusBullba, to answer your question. We don't have a cert (yet) for the Exchange server. That however doesn't matter for normal http connections, only if I attempt to use port 443 as the connect point for AS. Before the year is out, we'll more than likely acquire a cert for that server as well as our http server, but at the moment. I got nothing.
Inline........
Codevyper said:
Yeah that's what I figured. I have the ActiveSync virtual directory within the Default Website along with OMA, but the server is listening on ports 60000 & 443 rather than the typical port 80.
60000 is probably the killer as I noted earlier that push starts on 80 and jumps to 443.
You would think there would be a registry hack for AS on the mobile device whereby you could specify a non-standard port for syncing.
I think it was built around 80/443 to avoid client-side firewall issues.
TaurusBullba, to answer your question. We don't have a cert (yet) for the Exchange server. That however doesn't matter for normal http connections, only if I attempt to use port 443 as the connect point for AS. Before the year is out, we'll more than likely acquire a cert for that server as well as our http server, but at the moment. I got nothing.
You can do a "self-signed" certificate (i.e., generated by Windows Server) at zero cost. Downside is that it must be exported, copied to the device and installed.
Click to expand...
Click to collapse
vp3G said:
Inline........
Click to expand...
Click to collapse
Thanks for the help everyone. We will be building a new Exchange server later this year and I'll push to throw the site back on 80 at that time. In the meantime, I'll try the self-signed cert and see if that gets me in. Thanks everyone for your help! This site is a great resource for WinMo newbies like myself. BTW vp3g... lovin your AT&T v3 ROM. Solid and no problems overall!
BTW, I don't think ActiveSync starts off with port 80 - I was running a personal Exchange server off my cable connection whose incoming port 80 is blocked and everything worked fine using only 443. Good luck with the setup!
I am currently using WM6 and am trying to get EMail through our Exchange server setup; however, my Dash s620 will not properly save the server's address.
The address for our OWA is (ex) mail.email.com:8888/exchange
and this address works fine in Internet Explorer etc, but when I enter this into the phone it removes the /exchange and only saves up to :8888, which then gives me "Error synchronizing" when trying to connect. Our Exchange server does have Exchange ActiveSync enabled along with Direct Push enabled.
Any ideas?
Thanks in advance
I think that you have to check your ActiveSync settings on Exchange. I know that Microsoft have a lot of KB's about that.
It does the same thing on mine, erases exchange, but mine is cool. Are you sure you are putting in the Domain?
jt76542 said:
It does the same thing on mine, erases exchange, but mine is cool. Are you sure you are putting in the Domain?
Click to expand...
Click to collapse
Yeah I've tried every which way I could think of for the login credentials.
I'll sift through some more MS articles tomorrow afternoon, see if I can't find anything... baffled though, really.
K this is going to be a huge PITA I can tell.
I adjusted the Virtual Directory for the default web site in Exchange System manager to point directly to /exchange, eliminating the need for anything after the :8888. It works fine in IE etc, quickly brings up a login prompt. Using the phone's IE and going to the http://mail.email.com:8888 works fine, prompts a login accordingly...
I configured a coworkers Blackberry to use our OWA and it works fine, but I'm not sure if it uses Push Email (Exchange ActiveSync).
What is it about the Dash that won't mesh? The server is not using SSL so I couldn't see it being a certificate issue (maybe it still is?). Is there anyone around who manages an Exchange Server and could perhaps shed some light on common settings that need to be adjusted for Exchange ActiveSync?
Such a nuisance
ActiveSync on the phone reports "The server could not be reached. Please verify the server name." Support code: 0x80072EE7
It reports back with this no matter how I enter the address (which again, works fine in IE). Devil phone
8888 is definetly not standard for publishing ActiveSync.
the software will connect to either MailServer:80 if the SSL checkbox is cleared or MailServer:443 if the checkbox is checked.
don't think you'll get ActiveSync connect to something else.
Why don't you change your port back to 80?
you are already exposing your server to internet without any form of protection (no SSL so your password can be sniffed over the network) and having port 8888 buys you nothing in terms of security since any port scanner will report the port as opened and eventually get the HTTP banner from the IIS Server.
So, get back to a standard config and you'll love your DASH again.
UM
Hi all new here and got question regarding my new TP2, Im trying to setup my TP2 to sync with exchange but can not get it to work. I already inputted the username, password, domain, and also the OWA access information. My work's OWA address goes like this www.myjobaddress.com/extension , But after trying to sync it and when I check again it would just show www.myjobaddress.com without the "extension."
Is there a step-by-step guide somewhere? Is there anything else I need to do?
Thanks all in advance
yeah your server name in activesync shouldnt have the "extension". An Exchange server is an exchange server - with a FQDN: owa is a website residing at an addresss - sometimes with path after server name, not always, depends on the admin and the complexity of the setup.
i know that my owa address is waay diff than my activesync, etc server name.
Your admin or 3rd party provider should be able to give you a little config util that will setup your device properly, usually downloadable from a formatted txt msg. Or if you have access to your personal exchange control panel you should be able to get it from there - at the very least the correct info.
Hope this helps a little...
From what I've seen the OWA setup follows the standard as such webmail.company.com
It's been the same format in all the jobs I've had that had OWA access.
The other thing you can do is use Google Chrome, enter your OWA address then once it connects, on the new page that opens you can see the URL. It'll start with the format above.
The other thing you'll need is the domain name. And at times, that domain isn't the same as the company name. So you need to ask your Exchange admin.
All of this of course assumes your company is on Exchange 5.5 or 2007. If not you're not going to be able to get push email.
Thanks for the replies guys....I was able to get it to work. What I did was explicitly input this address "http://www.comanyname.com/exchange"
then just re-entered my username, password and domain. I had username in this format earlier "domain\username", I just removed the "domain" and entered just the username and it started syncing.
Thanks again guys
I am constantly getting emails from XDA that someone is trying to log into my account. Some douche with the ip: 93.218.42.61 is trying to access my profile.
What to do with this?
hahaha they have a default IIS7 running... and it looks like a pptp server(vpn)
Code:
Nmap scan report for p5DDA2A3D.dip.t-dialin.net (93.218.42.61)
Host is up (0.036s latency).
Not shown: 998 filtered ports
PORT STATE SERVICE
443/tcp open https
1723/tcp open pptp
And they are german because the 404 page is in german.
https://93.218.42.61/asdfasdfs
prolly a robot being used as a proxy.