Business- 75/30
Plus all our other field offices (east africa, latin , central america) all can access webmail , OWA OA without a hitch Jean-Paul Natola Date: Tue, 24 Sep 2013 12:51:58 -0400 Subject: Re: [NTSysADM] Connectivity issue From: [email protected] To: [email protected] FiOS business or home? They definitely filter outbound port 25 for home users. On Tue, Sep 24, 2013 at 12:39 PM, J- P <[email protected]> wrote: Now I'm really stumped- Just out of curiousity I decided to telnet from Nairobi to smtp.live.com port 25 , and wouldn't you know it let me right in, i then decided to try a few more smtp servers here in the states and sure as heck it went right in. The Only conclusion is that FIOS is blocking it from here NY. I wish I had another client on FIOS to confirm this, but at this point I have to rule out the Nairobi ISP as I am able to telnet , RDP, SSL and establish Citirx session from there to the states. Jean-Paul Natola > From: [email protected] > Date: Tue, 24 Sep 2013 12:24:46 -0400 > Subject: Re: [NTSysADM] Connectivity issue > To: [email protected] > > On Tue, Sep 24, 2013 at 11:05 AM, J- P <[email protected]> wrote: > > Ok, So running netmon on both ends revealed what you said, there is no trace > > of the web request coming to the server- if I ping back and forth i see the > > traffic- > > Sounds like someone is filtering TCP/443 (HTTPS/SSL) inbound to the > Nairobi office. > > > So i guess I'm pretty much %$&^%& - Since the office is in Nairobi I'm sure > > there are a few ISP's between them and NY, and they will all just point to > > the other. > > You might try contacting the Internet provider for the Nairobi > office. They're the one entity you have any influence over. If > *they* are the one doing the blocking, you might be able to do > something about it. For example, some ISPs block common services, and > will unblock them if you upgrade your Internet connection to a higher > tier of service. Or they might at least know what's going on. > > Other things you can try include: > > (1) Use a VPN for everything. You've already discovered this. > > (2) Use non-standard port numbers. Instead of running your > HTTPS/SSL listener on TCP/443, run it on some other port. > > -- Ben > >
