Chad
Mon Sep 22 16:23:22 CDT 2003
Good catch, Marina!
Hey Rich - is your post correct, or is that a typo? Outbound 110 will not
work if the local port is set to fixed 110. The local port needs to be All
Ports and the remote port needs to be fixed 110.
--
Chad A. Gross - SBS Rocks!
Lerman's Law of Technology: Any technical problem can be overcome
given enough time and money. Corollary: You are never given enough
time or money.
In news:UeJbb.107730$506.110031@typhoon.bart.nl,
Marina Roos <marina@roos.nodontwantspam.nl.com> posted:
> Just thought I saw something:
>
> Chad said:
>>>> work :^) The remote port
>>>>> should be set to fixed (110) and the local port set
>> to either
>>>>> Dynamic or All Ports. If the pcaket filter is set to Dynamic for
>>>>> local ports, try changing it to All Ports on the
>> local side and see
>>>>> if that helps.
>
> And Rich answered:
>>>> I've checked and the only other filter I have for port
>>>> 110 is the POP inbound filter that is created by SBS.
>> I
>>>> checked the port and it's 110 local, but the remote is
>>>> set to all ports.
>
> Doesn't look like Rich did what Chad told him to do.
>
> Marina
>
>
>
> "Rich Hurley" <rhurley@creativeconsulting.org> schreef in bericht
> news:b30101c38146$d6da9950$a601280a@phx.gbl...
>> Hi Chad,
>>
>> yes, I have, but I am using FQDN, not IP addresses. I'm
>> only using one as a test right now. I still can't do the
>> telnet domainname.com (or ip address) 110 on the server
>> without recieving a timeout.
>>
>>> -----Original Message-----
>>> Hi Rich -
>>>
>>> Well it sounds like ISA is set up OK. Have you checked
>> the KB article that
>>> Franz included in his post?
>>>
>>> --
>>> Chad A Gross - SBS Rocks!
>>>
>>> Lerman's Law of Technology: Any technical problem can
>> be overcome
>>> given enough time and money. Corollary: You are never
>> given enough
>>> time or money.
>>>
>>>
>>>
>>> Rich Hurley wrote:
>>>> Hi Chad,
>>>>
>>>> I've checked and the only other filter I have for port
>>>> 110 is the POP inbound filter that is created by SBS.
>> I
>>>> checked the port and it's 110 local, but the remote is
>>>> set to all ports.
>>>>
>>>> Rich
>>>>
>>>>> -----Original Message-----
>>>>> Hi Rich -
>>>>>
>>>>> Do you have any other filters on there for port 110?
>>>> And just double check
>>>>> that on the packet filter you created, you don't have
>> both your
>>>>> local and remote ports set to fixed - 110 (because it won't work
>>>>> :^) The remote port should be set to fixed (110) and the local
>>>>> port set
>> to either
>>>>> Dynamic or All Ports. If the pcaket filter is set to Dynamic for
>>>>> local ports, try changing it to All Ports on the
>> local side and see
>>>>> if that helps.
>>>>>
>>>>> --
>>>>> Chad A Gross - SBS Rocks!
>>>>>
>>>>> Lerman's Law of Technology: Any technical problem
>> can be overcome
>>>>> given enough time and money. Corollary: You are
>> never given enough
>>>>> time or money.
>>>>>
>>>>>
>>>>>
>>>>> Rich Hurley wrote:
>>>>>> I double checked the filter and it looks good. The
>> arrow
>>>>>> shows that it's enabled as does the property page.
>> There
>>>>>> isn't much to change with the filter. I've stopped
>> the
>>>>>> services and restarted them, but still no luck.
>> Seems
>>>>>> like it should be a pretty easy fix.
>>>>>>
>>>>>> Rich
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> Stop and start the www and firewall. Or you did not
>> make it
>>>>>>> perfectly. Packet filters is differnet from
>> protocol rules.
>>>>>>> Workstations with the firewall client use protocol rules. The
>>>>>>> server uses packet filters. Make sure your packet
>> filter looks
>>>>>>> exactly like Chad's suggestion and it has a good
>> sign on it. You
>>>>>>> can have filters created but unless they have an up arrow they
>>>>>>> are not turned on.
>>>>>>>
>>>>>>>
>>>>
>>
http://www.smallbizserver.net/sbs2000/ISA_for_Dummies.asp
>>>> x
>>>>>>>
>>>>>>> "Rich Hurley" <rhurley@creativeconsulting.org>
>> wrote:
>>>>>>>
>>>>>>>> I created a new filter as suggested with port 110,
>> but I
>>>>>>>> sitll cannot telnet it from the server. The wierd
>> part
>>>>>>>> is, I can successfully telnet from a clint. What
>> sense
>>>>>>>> does that make?
>>>>>>>>
>>>>>>>> Rich
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> Just follow Chad's instructions. It works first
>> time every time
>>>>>>>>> if you follow the filter creation. Just open a
>> telnet session
>>>>>>>>> from the command prompt to confirm.
>>>>>>>>>
http://support.microsoft.com/default.aspx?
>> scid=kb;en-
>>>>>>>>> us;196748&Product=sbs
>>>>>>>>>
>>>>>>>>> "Rich Hurley" <rhurley@creativeconsulting.org>
>> wrote:
>>>>>>>>>
>>>>>>>>>> I do have 2 nic cards and have ran the ICW
>> without having
>>>>>>>>>> the filter setup automatically.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> endless repost.
>>>>>>>>>>>
>>>>>>>>>>> Chad has mentioned a solution a few times in
>> the past few
>>>>>>>>>>> months. Sometimes runing the Internet
>> Connection Wizard does
>>>>>>>>>>> not set up a filter in ISA. A quick check I
>> always do is to go
>>>>>>>>>>> to the command prompt at the server and type
>> telnet. Type set
>>>>>>>>>>> local_echo and enter. open pop.server.com 110
>> enter. User
>>>>>>>>>>> mailboxname enter. Pass password. Doing this confirms many
>>>>>>>>>>> things quickly. First it confirms that your
>> server has good
>>>>>>>>>>> filters to allow the server to talk
>>>>>> to
>>>>>>>> a
>>>>>>>>>> pop server.
>>>>>>>>>>> Second is that it allows you to confirm user
>> names and
>>>>>>>>>>> passwords.
>>>>>>>>>>>
>>>>>>>>>>> Hi Mark -
>>>>>>>>>>>
>>>>>>>>>>> I'm assuming you're using ISA? Make sure you
>> have a packet
>>>>>>>>>>> filter defined
>>>>>>>>>>> that allows POP3 traffic outbound. Open ISA Management and
>>>>>>>>>>> navigate to:
>>>>>>>>>>>
>>>>>>>>>>> Servers & Arrays
>>>>>>>>>>> <servername>
>>>>>>>>>>> Access Policy
>>>>>>>>>>> IP Packet Filters
>>>>>>>>>>>
>>>>>>>>>>> Review the list of filters and see if there is
>> a filter
>>>>>>>>>>> allowing traffic
>>>>>>>>>>> outbound on port 110. If so, verify that it is enabled. If
>>>>>>>>>>> you don't have
>>>>>>>>>>> a filter allowing outbound Pop3, you'll need to create one -
>>>>>>>>>>>
>>>>>>>>>>> Actions | New | Filter
>>>>>>>>>>>
>>>>>>>>>>> Mode: Allow packet transmission
>>>>>>>>>>> Filter Type: Custom
>>>>>>>>>>> IP Protocol: TCP
>>>>>>>>>>> Direction: Outbound
>>>>>>>>>>> Local Port: Dynamic
>>>>>>>>>>> Remote Port: Fixed Port (110)
>>>>>>>>>>>
>>>>>>>>>>> "Rich Hurley" <rhurley@creativeconsulting.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I've just setup my exchange server, which is actually just
>>>>>>>>>>>> forwarding to my pop account and I am
>> recieving an error
>>>>>>>>>>>> in doing so. The error is 10065. It is
>> having problems
>>>>>>>>>>>> connecting or authenticating my pop server.
>>>>>>>>>>>>
>>>>>>>>>>>> Any ideas would be appreciated.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> Rich
>>>>>>>>>>>
>>>>>>>>>>> Jim B. SBS MVP
>>>>>>>>>>> .
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Jim B. SBS MVP
>>>>>>>>> .
>>>>>>>>>
>>>>>>>
>>>>>>> Jim B. SBS MVP
>>>>>>> .
>>>>>
>>>>>
>>>>> .
>>>
>>>
>>> .