How would I test ports in this situation?

We have a client that wants to install SBS2003 and use Exchange. They are
in a shared office environment where the landlord controls all of the
internet access.

This user has their own LinkSys router/firewall, and they're able to use
Outlook currently without any problems. They have a static IP provided by
the landlord (at least it hasn't changed in the past 1.5 years).

I'd like to make sure that they can use Exchange in this environment without
any involvement from the landlord. I've opened up ports 6001, 6004, 25, 110,
and 135 on their LinkSys, but I can't telnet to them.

Does an application actually have to be running on their computer for me to
be able to telnet to it? For example, since I can't telnet to port 135, I
don't know if that's because they don't have Exchange sitting there
listening on that port, or if the landlord has blocked that (and most other)
ports.

How can I tell if it's the landlord blocking those ports, or if it's just
because we don't have any apps on the inside actually listening on those
ports?

Can you telnet the port 25 and 110 in the LAN?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"TurboPing" <(E-Mail Removed)> wrote in message
news:ux3s%238A%(E-Mail Removed)...
> We have a client that wants to install SBS2003 and use Exchange. They are
> in a shared office environment where the landlord controls all of the
> internet access.
>
> This user has their own LinkSys router/firewall, and they're able to use
> Outlook currently without any problems. They have a static IP provided by
> the landlord (at least it hasn't changed in the past 1.5 years).
>
> I'd like to make sure that they can use Exchange in this environment
> without any involvement from the landlord. I've opened up ports 6001,
> 6004, 25, 110, and 135 on their LinkSys, but I can't telnet to them.
>
> Does an application actually have to be running on their computer for me
> to be able to telnet to it? For example, since I can't telnet to port
> 135, I don't know if that's because they don't have Exchange sitting there
> listening on that port, or if the landlord has blocked that (and most
> other) ports.
>
> How can I tell if it's the landlord blocking those ports, or if it's just
> because we don't have any apps on the inside actually listening on those
> ports?
>
>

He multi-posted this in who-knows how many groups.
I already gave a detailed and somewhat long response to it in
microsoft.public.networking.firewall


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"Robert L. (MS-MVP)" <(E-Mail Removed)> wrote in message
news:%23TvAfpK%(E-Mail Removed)...
> Can you telnet the port 25 and 110 in the LAN?
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "TurboPing" <(E-Mail Removed)> wrote in message
> news:ux3s%238A%(E-Mail Removed)...
>> We have a client that wants to install SBS2003 and use Exchange. They
>> are in a shared office environment where the landlord controls all of the
>> internet access.
>>
>> This user has their own LinkSys router/firewall, and they're able to use
>> Outlook currently without any problems. They have a static IP provided
>> by the landlord (at least it hasn't changed in the past 1.5 years).
>>
>> I'd like to make sure that they can use Exchange in this environment
>> without any involvement from the landlord. I've opened up ports 6001,
>> 6004, 25, 110, and 135 on their LinkSys, but I can't telnet to them.
>>
>> Does an application actually have to be running on their computer for me
>> to be able to telnet to it? For example, since I can't telnet to port
>> 135, I don't know if that's because they don't have Exchange sitting
>> there listening on that port, or if the landlord has blocked that (and
>> most other) ports.
>>
>> How can I tell if it's the landlord blocking those ports, or if it's just
>> because we don't have any apps on the inside actually listening on those
>> ports?
>>
>>
>

"TurboPing" <(E-Mail Removed)> wrote:

> I'd like to make sure that they can use Exchange in this environment
> without any involvement from the landlord. I've opened up ports 6001,
> 6004, 25, 110, and 135 on their LinkSys, but I can't telnet to them.
>
What do you mean by "opened" ? You redirected these ports ? If yes, on which
machine ?

You need to have somme app listening on these ports on the machine where
they are redirected to be able to telnet to them.

ThePro

Thanks, Phillip. I only posted this in one other group here, not being sure
which one was correct. And for those reading this, yes, Phillip gave a good
response in microsoft.public.networking.firewall. Thanks again, Phillip.


"Phillip Windell" <(E-Mail Removed)> wrote in message
news:e3yfCzK%(E-Mail Removed)...
> He multi-posted this in who-knows how many groups.
> I already gave a detailed and somewhat long response to it in
> microsoft.public.networking.firewall
>
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or
> Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
> "Robert L. (MS-MVP)" <(E-Mail Removed)> wrote in message
> news:%23TvAfpK%(E-Mail Removed)...
>> Can you telnet the port 25 and 110 in the LAN?
>>
>> --
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting on
>> http://www.ChicagoTech.net
>> How to Setup Windows, Network, VPN & Remote Access on
>> http://www.HowToNetworking.com
>> "TurboPing" <(E-Mail Removed)> wrote in message
>> news:ux3s%238A%(E-Mail Removed)...
>>> We have a client that wants to install SBS2003 and use Exchange. They
>>> are in a shared office environment where the landlord controls all of
>>> the internet access.
>>>
>>> This user has their own LinkSys router/firewall, and they're able to use
>>> Outlook currently without any problems. They have a static IP provided
>>> by the landlord (at least it hasn't changed in the past 1.5 years).
>>>
>>> I'd like to make sure that they can use Exchange in this environment
>>> without any involvement from the landlord. I've opened up ports 6001,
>>> 6004, 25, 110, and 135 on their LinkSys, but I can't telnet to them.
>>>
>>> Does an application actually have to be running on their computer for me
>>> to be able to telnet to it? For example, since I can't telnet to port
>>> 135, I don't know if that's because they don't have Exchange sitting
>>> there listening on that port, or if the landlord has blocked that (and
>>> most other) ports.
>>>
>>> How can I tell if it's the landlord blocking those ports, or if it's
>>> just because we don't have any apps on the inside actually listening on
>>> those ports?
>>>
>>>
>>
>
>

Aahh.... you *really* hit the nail on the head with your statement about
needing an app running to listen on those ports. Since I don't have the
application actually loaded, do you know of an "application/port simulator?"


"ThePro" <(E-Mail Removed)> wrote in message
news:AEDA4061-CEF9-40B5-B7BA-(E-Mail Removed)...
> "TurboPing" <(E-Mail Removed)> wrote:
>
>> I'd like to make sure that they can use Exchange in this environment
>> without any involvement from the landlord. I've opened up ports 6001,
>> 6004, 25, 110, and 135 on their LinkSys, but I can't telnet to them.
>>
> What do you mean by "opened" ? You redirected these ports ? If yes, on
> which
> machine ?
>
> You need to have somme app listening on these ports on the machine where
> they are redirected to be able to telnet to them.
>
> ThePro
>

Install a ftp server on the machine (there are some freeware) and change the
default listening port 21 to any port you want to test.

ThePro

"TurboPing" <(E-Mail Removed)> wrote:
> Aahh.... you *really* hit the nail on the head with your statement about
> needing an app running to listen on those ports. Since I don't have the
> application actually loaded, do you know of an "application/port
> simulator?"
>
>
> "ThePro" <(E-Mail Removed)> wrote in message
> news:AEDA4061-CEF9-40B5-B7BA-(E-Mail Removed)...
>> "TurboPing" <(E-Mail Removed)> wrote:
>>
>>> I'd like to make sure that they can use Exchange in this environment
>>> without any involvement from the landlord. I've opened up ports 6001,
>>> 6004, 25, 110, and 135 on their LinkSys, but I can't telnet to them.
>>>
>> What do you mean by "opened" ? You redirected these ports ? If yes, on
>> which
>> machine ?
>>
>> You need to have somme app listening on these ports on the machine where
>> they are redirected to be able to telnet to them.
>>
>> ThePro
>>
>

Excellent... and so obvious, too... Thank you for a great suggestion.


"ThePro" <(E-Mail Removed)> wrote in message
news:10FD59A5-CB33-4DED-B92C-(E-Mail Removed)...
> Install a ftp server on the machine (there are some freeware) and change
> the default listening port 21 to any port you want to test.
>
> ThePro
>
> "TurboPing" <(E-Mail Removed)> wrote:
>> Aahh.... you *really* hit the nail on the head with your statement about
>> needing an app running to listen on those ports. Since I don't have the
>> application actually loaded, do you know of an "application/port
>> simulator?"
>>
>>
>> "ThePro" <(E-Mail Removed)> wrote in message
>> news:AEDA4061-CEF9-40B5-B7BA-(E-Mail Removed)...
>>> "TurboPing" <(E-Mail Removed)> wrote:
>>>
>>>> I'd like to make sure that they can use Exchange in this environment
>>>> without any involvement from the landlord. I've opened up ports 6001,
>>>> 6004, 25, 110, and 135 on their LinkSys, but I can't telnet to them.
>>>>
>>> What do you mean by "opened" ? You redirected these ports ? If yes, on
>>> which
>>> machine ?
>>>
>>> You need to have somme app listening on these ports on the machine where
>>> they are redirected to be able to telnet to them.
>>>
>>> ThePro
>>>
>>
>