View Full Version : Exchange Email Service and Virgin 20MB
cityhunter
16-09-2009, 23:23
Hoping someone can help!
Ive posted this here as its a problem with Virgins Internet service. Looks like Virgin are blocking the service.
Heres a little background....
Up until 6 weeks ago I was using a free exchange email service without any issues, then approx 4 weeks ago i was having errors which didnt affect sending and recieving from exchange. Now I am unable to connect to exchange at all, with the error message "The name cannot be resolved. The connections to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
The exchange server address is win.alol.net.br. I have contact the email provider and they have done 3 days worth of testing and come back to Virgin Media being the problem, I confirmed this by using the laptop with 4 different service provider all without issue.
Any help on this would be appreciated or if anyone can confirm if indeed they are blocking?
Thanks
cityhunter
homealone
16-09-2009, 23:49
any help?
http://forum.xda-developers.com/showthread.php?t=517693&page=3
otherwise checkout gmx.com which seems to be fine for most mail aggregation?
cityhunter
16-09-2009, 23:55
any help?
http://forum.xda-developers.com/showthread.php?t=517693&page=3
Sorry Gaz, tried this and everything else, im an It engineer and used the alol service since it went live and none of the things in this tread help. Damn Virgin!
homealone
17-09-2009, 00:07
Sorry Gaz, tried this and everything else, im an It engineer and used the alol service since it went live and none of the things in this tread help. Damn Virgin!
I'm not sure what isn't working, to the best of my knowledge VM don't 'block' any email services - I use the GMX aggregator as well as gmail, with no problems???
I'd suspect the exchange interface, personally, but as I don't use Outlook - having disabled it in my Office 2007 installation, I cannot be sure ;)
I tried a telnet session to the exchange server for you on my VM connection, it appeared to be OK.
$ telnet alol.net.br 25
Trying 200.169.217.117...
Connected to alol.net.br.
Escape character is '^]'.
220 WIN.alol.net.br Microsoft ESMTP MAIL Service ready at Thu, 17 Sep 2009 04:22:29 -0300
helo
250 WIN.alol.net.br Hello [86.*.*.57]
Why you're getting the message about name resolution issues is a mystery, but it would appear that VM aren't blocking access to the mail exchange, well certainly not on port 25.
Do you use a specific protocol such as IMAP or something.
cllp1975
17-09-2009, 08:36
By any chance are you using the Windows 7 Beta? If so, there's a workaround for this. Let me know if you need it....
Ignitionnet
17-09-2009, 11:45
VM do block some ports which might cause strife with Exchange.
Port Purpose
135 DCOM Service Control Manager
136 PROFILE Naming System
137 NetBIOS Name Service
138 NetBIOS Datagram Service
139 NetBIOS Session Service
445 Microsoft Directory Services
1433 Microsoft SQL Server
1434 Microsoft SQL Monitor
135 especially will be problematic, it's the port MAPI clients connect to in order to obtain information on the two random ports they should connect to for information store and directory access. If this is blocked outbound game over.
cityhunter
17-09-2009, 11:52
I tried a telnet session to the exchange server for you on my VM connection, it appeared to be OK.
$ telnet alol.net.br 25
Trying 200.169.217.117...
Connected to alol.net.br.
Escape character is '^]'.
220 WIN.alol.net.br Microsoft ESMTP MAIL Service ready at Thu, 17 Sep 2009 04:22:29 -0300
helo
250 WIN.alol.net.br Hello [86.*.*.57]
Why you're getting the message about name resolution issues is a mystery, but it would appear that VM aren't blocking access to the mail exchange, well certainly not on port 25.
Do you use a specific protocol such as IMAP or something.
Hi Toto,
Exchange uses ports 135 and 139.
Regards
---------- Post added at 11:52 ---------- Previous post was at 11:51 ----------
VM do block some ports which might cause strife with Exchange.
Port Purpose
135 DCOM Service Control Manager
136 PROFILE Naming System
137 NetBIOS Name Service
138 NetBIOS Datagram Service
139 NetBIOS Session Service
445 Microsoft Directory Services
1433 Microsoft SQL Server
1434 Microsoft SQL Monitor
Any chance theres a way round this?? ie complain etc
cllp1975
17-09-2009, 11:55
Try this - works for me - Dead easy - type in the DOMAIN NAME forward slash and your user name in the user name box....
So example:
myexchangeserver.net\myuser
cityhunter
17-09-2009, 11:57
Sorry clip,
Thats for name resolution and wont/doesnt work. The issue is that i cannot contact the server as virgin block exchange ports i think.
Ignitionnet
17-09-2009, 11:58
Any chance theres a way round this?? ie complain etc
Either a VPN to avoid the port blocking or use another ISP. If VM are blocking outbound port 135 from you they aren't going to change it due to your making a complaint. The port blocking is built into the modem's configuration file, and they won't change the config file for a single customer.
The only solution while keeping a cable connection would be to switch to ntl:Telewest Business.
cllp1975
17-09-2009, 12:00
Very weird - I was on 20meg till yesterday, and this solution worked for me. I'm now on 50meg and um... it still works.
cityhunter
17-09-2009, 12:00
Either a VPN to avoid the port blocking or use another ISP. If VM are blocking outbound port 135 from you they aren't going to change it due to your making a complaint. The port blocking is built into the modem's configuration file, and they won't change the config file for a single customer.
The only solution while keeping a cable connection would be to switch to ntl:Telewest Business.
Thanks for the heads up, free vpn doesnt seem to work, i can contact the server but have name resolution issues.
Funny thing is that all this used to work :(
cllp1975
17-09-2009, 12:01
Is it your exchange or a hosted exchange? If it's yours, there may be a tweak on the server to fix this.
Hi Toto,
Exchange uses ports 135 and 139.
Regards
---------- Post added at 11:52 ---------- Previous post was at 11:51 ----------
Any chance theres a way round this?? ie complain etc
Well its been in place for years to be honest, so why its only now working in your case, IF it is the reason for the problem, is very odd.
And no, if these blocks are still in place VM won't remove them, unless they do so globally across its network. They were originally put in place to prevent the spread of certain viruses that exploit those ports, and the case for blocking them was supported by MS at the time if memory serves (ex NTL network at that time).
EDIT:
Just tested your exchange server using those two ports, both timed out, sorry.
cityhunter
17-09-2009, 12:08
Thanks for all your help guys, i suppose there nothing more i can do:mad:
Thanks for all your help guys, i suppose there nothing more i can do:mad:
You're welcome, wish it was better news....as mentioned though,can the exchange server be configured to allow connections on a different port?
cityhunter
17-09-2009, 12:22
You're welcome, wish it was better news....as mentioned though,can the exchange server be configured to allow connections on a different port?
Its a free service so i doubt they will. Ill just access it via imap in oulook and use exchange on my handset.
Im still really baffled why it used to work and now doesn't. The only changes the isp have made is the server used to be 200.169.217.120 now it is 200.169.217.117
Its a free service so i doubt they will. Ill just access it via imap in oulook and use exchange on my handset.
Im still really baffled why it used to work and now doesn't. The only changes the isp have made is the server used to be 200.169.217.120 now it is 200.169.217.117
What IP address does the domain name resolve to at your end, the old one or the new one. If it's the old one, do an ipconfig /flushdns and try again.
Only other thing is, I tried a tracert to win.alol.net.br and it times out on everything after hop 13:
Pinging win.alol.net.br [200.169.217.117] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 200.169.217.117:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Documents and Settings\Jonathan>tracert win.alol.net.br
Tracing route to win.alol.net.br [200.169.217.117]
over a maximum of 30 hops:
1 4 ms 1 ms 3 ms unknown [192.168.1.1]
2 10 ms 9 ms 8 ms 10.225.80.1
3 11 ms 7 ms 8 ms nott-cam-1a-v107.network.virginmedia.net [81.109
.167.29]
4 9 ms 10 ms 7 ms nott-t3core-1a-ae2-0.network.virginmedia.net [19
5.182.174.213]
5 12 ms 11 ms 9 ms lee-bb-a-as0-0.network.virginmedia.net [213.105.
174.169]
6 11 ms 10 ms 10 ms lee-bb-b-ae0-0.network.virginmedia.net [62.253.1
87.186]
7 17 ms 22 ms 18 ms 62.252.224.238
8 17 ms 15 ms 18 ms xe-5-3-0.xcr1.lnd.cw.net [195.2.21.209]
9 98 ms 86 ms 89 ms ge-11-0-0.xcr1.nyk.cw.net [195.2.25.18]
10 89 ms 87 ms 85 ms brasiltelecom.nyk.cw.net [195.2.17.46]
11 251 ms 307 ms 304 ms BrT-A12-0-0-1-bhels300.brasiltelecom.net.br [201
.10.241.250]
12 315 ms 304 ms 309 ms BrT-A12-0-0-1-bhels300.brasiltelecom.net.br [201
.10.241.250]
13 318 ms 311 ms 307 ms webmail.alol.com.br [200.169.217.130]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Rouing table problem on the node at hop 13?
cityhunter
17-09-2009, 13:07
Just checked and below are the results, a little different from yours: -
C:\Users\Cityhunter>nslookup win.alol.net.br
Server: UnKnown
Address: 192.168.1.1
Non-authoritative answer:
Name: win.alol.net.br
Address: 200.169.217.117
C:\Users\Cityhunter>tracert win.alol.net.br
Tracing route to win.alol.net.br [200.169.217.117]
over a maximum of 30 hops:
1 8 ms 17 ms 7 ms 10.147.208.1
2 9 ms 7 ms 7 ms 10.147.208.1
3 9 ms 8 ms 7 ms leed-t3core-1a-ge-300-1428.network.virginmedia.n
et [80.0.54.213]
4 8 ms 7 ms 9 ms lee-bb-a-as9-0.network.virginmedia.net [213.105.
175.65]
5 8 ms 25 ms 9 ms lee-bb-b-ae0-0.network.virginmedia.net [62.253.1
87.186]
6 17 ms 16 ms 15 ms 62.252.224.238
7 16 ms 75 ms 17 ms xe-11-0-0-xcr1.lnd.cw.net [195.2.10.245]
8 104 ms 87 ms 87 ms ge-11-0-0.xcr1.nyk.cw.net [195.2.25.18]
9 95 ms 95 ms 95 ms brasiltelecom.nyk.cw.net [195.2.17.46]
10 223 ms 223 ms 223 ms BrT-A12-0-0-1-bhels300.brasiltelecom.net.br [201
.10.241.250]
11 223 ms 223 ms 223 ms BrT-A12-0-0-1-bhels300.brasiltelecom.net.br [201
.10.241.250]
12 241 ms 229 ms 225 ms pop3.alol.com.br [200.169.217.130]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\Users\Cityhunter>
I got the same results as yoiu when I ran it last night. The last hop is different in our two trace routes, everything else is the same. By the time the difference shows up the network is well outside of virgins control, like i said before, i suspect dodgy routing somewhere.
There has been a lot of routing issues between the UK and America lately, perhaps there is something on the way giving out dodgy routing updates.
Ignitionnet
17-09-2009, 14:20
Checking the routing at CWC London:
200.169.192.0/18 (1 entry, 1 announced)
*BGP Preference: 170/-81
Next hop type: Indirect
Next-hop reference count: 465408
Next hop type: Router, Next hop index: 262495
Next hop: 195.2.25.121 via ge-1/0/0.0, selected
Next hop: 195.2.25.1 via ge-5/0/0.0
It's being received as a /18 from Brazil Telecom - if you can get as far as hop 12 there is no way a routing issue will prevent you from reaching the destination.
The issue doesn't seem to relate to routing, probably relates to port blocking or the server itself.
Checking the routing at CWC London:
200.169.192.0/18 (1 entry, 1 announced)
*BGP Preference: 170/-81
Next hop type: Indirect
Next-hop reference count: 465408
Next hop type: Router, Next hop index: 262495
Next hop: 195.2.25.121 via ge-1/0/0.0, selected
Next hop: 195.2.25.1 via ge-5/0/0.0
It's being received as a /18 from Brazil Telecom - if you can get as far as hop 12 there is no way a routing issue will prevent you from reaching the destination.
The issue doesn't seem to relate to routing, probably relates to port blocking or the server itself.
Why am I getting different trace route results to the OP?
BTW, that's not a disagreement or "your wrong" of any sort, just trying to understand ;)
sdsl2009
17-09-2009, 14:38
I would suggest the server itself, as I've had my Exchange server running here for 4 years without any problems at all.
I connect to it with Blackberry / Windows Mobile and the usual web access.
First post - registered especially to reply :-)
Ignitionnet
17-09-2009, 14:46
Why am I getting different trace route results to the OP?
BTW, that's not a disagreement or "your wrong" of any sort, just trying to understand ;)
You aren't, IP addresses from lee-bb-b where your route and OPs converge are the same just the reverse DNS on the last hop that responds is different ;)
---------- Post added at 14:46 ---------- Previous post was at 14:44 ----------
I would suggest the server itself, as I've had my Exchange server running here for 4 years without any problems at all.
I connect to it with Blackberry / Windows Mobile and the usual web access.
First post - registered especially to reply :-)
You're connecting via web access though, not MAPI, web access is just straight HTTPS on port 443 :)
cityhunter
17-09-2009, 17:43
Yey, a little bit off success which leans more towards Virgin being at fault, when using hotspot shield I was getting an issue where it would see exchange (unlike when connected through virgin) but an error saying could not resolve name. When using the full name resolution of /o=ALOL/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=xxxxxxxx it works.
Lao recieved this from alol
From: Monitor ALOL
Sent: 17 September 2009 18:38
To: x
Subject: RES: Connectivity Issue
Hi!
You can’t ping or tracerouting to our server because the server firewall are block to do this.
Excellent that it worked for you.
ALOL.Net.br
vBulletin® v3.8.11, Copyright ©2000-2024, vBulletin Solutions Inc.