Outlook (Office 10 Pro) stops sending/receiving email when I disable Ports 135-139 TCP, 445-1434 TCP on my router

When I disable "Windows Service, Remote Management, Ports 135-139 TCP, 445-1434 TCP" on my DSL router, Outlook fails sending/receiving GMAIL. Google is adamant that the GMAIL service is not doing a reverse lookup or using IE's SSL service. I am trying to lock down my Development LAN (NetBIOS/SMB/RPC) and do not want this traffic broadcast to my ISP's designated subnet.

Thanks!!

Tim Reamer

June 29th, 2015 4:25pm

If you've setup Gmail with Outlook as described here https://support.google.com/mail/troubleshooter/1668960?hl=en#ts=1665018,1665137,2769074, (and I don't see how you could not, I don't think these are configurable settings) it seems like you'd be using port 993 for incoming and 465 or 587 for outgoing. Based on what you've said above, you're blocking all of those, hence the problem. Is selectively disabling ports other than those an option?
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2015 6:14pm

Thank you for the reply. The Centurylink DSL Modem doesn't let you selectively disable "some" of the ports in the firewall settings. I do have the OUTLOOK setting configured as described. Do you know what PORT is the offender? I can use the TELNET config access into the modem to set individual ports (not supported by Centurylink; and virtually the same as configuring a Cisco Router about 10 years ago.

Thanks!!

Tim

June 30th, 2015 10:42am

No problem. When you say which port is the offender, you mean as far as making it NOT work, correct? That is, you're going to go in using telnet and enable those? If that's the case, I'd try enabling mail ports 993 (incoming) and 465 (outgoing).

Also, I'm curious - is it indeed a DSL modem or a router (you said one then the other). If it's a DSL modem, might I suggest picking up a cheap router (look on Slickdeals.net for good deals). This way, you can make your setup DSL modem -> router -> computer and gain the added protection of NAT by default. You'll also be able to avoid using archaic and possibly dangerous telnet commands to do simple things like opening a port! Lastly, you'll gain features like UPnP (useful to applications in securely and dynamically opening ports on the router) and the ability to add multiple computers/tablets/phones/etc to the connection. Just my $0.02 if you're indeed using a DSL modem.

All the best!



Free Windows Admin Tool Kit Click here and download it now
June 30th, 2015 4:34pm

JustAnotherVBDev,

     Thank you for the reply. The DSL modem is fairly advanced, supports NAT, UPNP, and firewall services. "Windows Services" (TCP Ports 135-139 TCP, 445-1434) are all grouped together as 1 selection in the firewall settings. When disabled outbound GMAIL stops sending / receiving; when enabled outbound it works again. As you indicated, I have the correct GMAIL ports set up (995/465 both SSL). What I haven't been able to figure out is which WinServ port is causing the issue when disabled outbound. For what it's worth, I worked at AT&T for 17 years, and used the internet before it was the internet (AutoDin). I am a networking guy, just need a nudge in the right direction.

Tim

June 30th, 2015 7:37pm

No problem. When you say which port is the offender, you mean as far as making it NOT work, correct? That is, you're going to go in using telnet and enable those? If that's the case, I'd try enabling mail ports 993 (incoming) and 465 (outgoing).

Also, I'm curious - is it indeed a DSL modem or a router (you said one then the other). If it's a DSL modem, might I suggest picking up a cheap router (look on Slickdeals.net for good deals). This way, you can make your setup DSL modem -> router -> computer and gain the added protection of NAT by default. You'll also be able to avoid using archaic and possibly dangerous telnet commands to do simple things like opening a port! Lastly, you'll gain features like UPnP (useful to applications in securely and dynamically opening ports on the router) and the ability to add multiple computers/tablets/phones/etc to the connection. Just my $0.02 if you're indeed using a DSL modem.

All the best!



Free Windows Admin Tool Kit Click here and download it now
June 30th, 2015 8:32pm

No problem. When you say which port is the offender, you mean as far as making it NOT work, correct? That is, you're going to go in using telnet and enable those? If that's the case, I'd try enabling mail ports 993 (incoming) and 465 (outgoing).

Also, I'm curious - is it indeed a DSL modem or a router (you said one then the other). If it's a DSL modem, might I suggest picking up a cheap router (look on Slickdeals.net for good deals). This way, you can make your setup DSL modem -> router -> computer and gain the added protection of NAT by default. You'll also be able to avoid using archaic and possibly dangerous telnet commands to do simple things like opening a port! Lastly, you'll gain features like UPnP (useful to applications in securely and dynamically opening ports on the router) and the ability to add multiple computers/tablets/phones/etc to the connection. Just my $0.02 if you're indeed using a DSL modem.

All the best!



June 30th, 2015 8:32pm

Ah ok, seems like a decent enough router. And my apologies, it's hard to gauge someone's experience level on a public forum :) Seems like you are probably intimately familiar with the ins and outs of networking.

To confirm, per our discussion, have you tried to enable 993 & 465 selectively using telnet? Also, is there any concept of rule priority/order? If so, please try putting both enable rules before the Windows Services firewall rule, and if that doesn't work, then put them (both) after. It could be that you're creating the hole, and then a later rule is closing it again.

Free Windows Admin Tool Kit Click here and download it now
July 1st, 2015 9:30am

Ah ok, seems like a decent enough router. And my apologies, it's hard to gauge someone's experience level on a public forum :) Seems like you are probably intimately familiar with the ins and outs of networking.

To confirm, per our discussion, have you tried to enable 993 & 465 selectively using telnet? Also, is there any concept of rule priority/order? If so, please try putting both enable rules before the Windows Services firewall rule, and if that doesn't work, then put them (both) after. It could be that you're creating the hole, and then a later rule is closing it again.

July 1st, 2015 1:28pm

JustAnotherVBDev,

     Thank you for the reply and suggestions. I've tinkered with the ACL's in the DSL modem as proposed, and GMAIL still doesn't work after the mods. I am going to turn on/off each one of the "Windows Services" ports one at a time to see which one is the offender; then determine what liability there is leaving it open only as an "outbound" port. It is too bad that things have to be so complicated. I know that if I installed ELM or PINE on my Linux box this would be a non-issue... Again - Thanks for the guidance.

Tim

Free Windows Admin Tool Kit Click here and download it now
July 8th, 2015 12:03pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics