D
Dan Jenkins
I have been using Outlook for Mac for the past 2 years and have had my
share of problems, but none that I couldn't figure out on my own. This
one has got me good. I have been told by a Comcast tech rep that they
have closed access to TCP/IP port 135 and others in response to the
MSBlaster and other Viruses that are using the port to gain access to
MS computers and servers. Since closing these ports, my Mac clients
that use Comcast for internet have been unable to connect to our
Exchange server. When trying to connect they get the login name and
password screen and then the program hangs for a minute before it says
that your exhange server is unavailable. I have reconfigured the
exchange server to use a different TCP/IP port, but I don't know how
to configure the Mac clients to use that port to gain access. If
anyone is having similer problems with Comcast or has any suggestions,
please reply.
share of problems, but none that I couldn't figure out on my own. This
one has got me good. I have been told by a Comcast tech rep that they
have closed access to TCP/IP port 135 and others in response to the
MSBlaster and other Viruses that are using the port to gain access to
MS computers and servers. Since closing these ports, my Mac clients
that use Comcast for internet have been unable to connect to our
Exchange server. When trying to connect they get the login name and
password screen and then the program hangs for a minute before it says
that your exhange server is unavailable. I have reconfigured the
exchange server to use a different TCP/IP port, but I don't know how
to configure the Mac clients to use that port to gain access. If
anyone is having similer problems with Comcast or has any suggestions,
please reply.