![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
First,
Connecting To news.povray.org...
Then, after quite a while,
Could not open connection to the host, on port 119: Connect failed
That's it
Jim Henderson <nos### [at] nospam com> wrote:
> On Fri, 08 May 2009 13:27:08 -0400, EricG wrote:
>
> > I am trying to connect from my work location, behind a corporate
> > firewall, using Outlook express. I am able to connect to other
> > newsgroups out there (such as Microsoft) without problem.
> >
> > Any suggestions?
>
> From your workstation, what happens if you open a command prompt and
> enter:
>
> telnet news.povray.org 119
>
> ?
>
> Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Fri, 08 May 2009 13:47:08 -0400, EricG wrote:
> First,
>
> Connecting To news.povray.org...
>
> Then, after quite a while,
>
> Could not open connection to the host, on port 119: Connect failed
>
> That's it
Sounds like your firewall is blocking the port, then. For the other news
servers, do you connect on port 119 or on the secure NNTP port (in the
500's, I forget exactly which)?
Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
I tried the same telnet command with msnews.microsoft.com, and it worked just
fine. I can't detect any difference in the way the two newsgroups are set up
in Outlook express. They are both using port 119.
Can a firewall filter certain NGs out (maybe that have ".org" in them instead of
".com")?
Eric
Jim Henderson <nos### [at] nospam com> wrote:
>
> Sounds like your firewall is blocking the port, then. For the other news
> servers, do you connect on port 119 or on the secure NNTP port (in the
> 500's, I forget exactly which)?
>
> Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Fri, 08 May 2009 14:38:24 -0400, EricG wrote:
> I tried the same telnet command with msnews.microsoft.com, and it worked
> just fine. I can't detect any difference in the way the two newsgroups
> are set up in Outlook express. They are both using port 119.
If you can't telnet to the port on the server, it's not an Outlook
configuration issue - it's a communications issue. So as long as you've
spelled the server's name correctly (and it is news.povray.org, so it
seems that that can be ruled out), there isn't anything you can change in
Outlook that will correct the problem.
Think of it like driving a car to an island. If there's exactly one
route on the roads to get to the island (over a bridge) and the bridge
isn't open, the type of (non-amphibious) car you're driving won't matter,
because the fundamental problem is that the bridge is closed.
So the first step is to get the bridge opened.
> Can a firewall filter certain NGs out (maybe that have ".org" in them
> instead of ".com")?
Possibly; you'd have to ask your firewall administrator.
Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Thanks for your inputs. I'll try talking to the help desk to see if they have
anything to add. It shouldn't be this hard...
As long as I can use the web interface, I guess it doesn't matter that much.
Eric
Jim Henderson <nos### [at] nospam com> wrote:
> On Fri, 08 May 2009 14:38:24 -0400, EricG wrote:
>
> > I tried the same telnet command with msnews.microsoft.com, and it worked
> > just fine. I can't detect any difference in the way the two newsgroups
> > are set up in Outlook express. They are both using port 119.
>
> If you can't telnet to the port on the server, it's not an Outlook
> configuration issue - it's a communications issue. So as long as you've
> spelled the server's name correctly (and it is news.povray.org, so it
> seems that that can be ruled out), there isn't anything you can change in
> Outlook that will correct the problem.
>
> Think of it like driving a car to an island. If there's exactly one
> route on the roads to get to the island (over a bridge) and the bridge
> isn't open, the type of (non-amphibious) car you're driving won't matter,
> because the fundamental problem is that the bridge is closed.
>
> So the first step is to get the bridge opened.
>
> > Can a firewall filter certain NGs out (maybe that have ".org" in them
> > instead of ".com")?
>
> Possibly; you'd have to ask your firewall administrator.
>
> Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Fri, 08 May 2009 15:05:52 -0400, EricG wrote:
> Thanks for your inputs. I'll try talking to the help desk to see if
> they have anything to add. It shouldn't be this hard...
Glad to help out, Eric. :-)
Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Jim Henderson <nos### [at] nospam com> wrote:
> > Can a firewall filter certain NGs out (maybe that have ".org" in them
> > instead of ".com")?
>
> Possibly; you'd have to ask your firewall administrator.
If even telnet to the port won't work, it cannot be a NG-specific filter, can
it?
So looks like the whole NG server is deliberately filtered out (or, more likely,
not deliberately "filtered in").
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Sat, 09 May 2009 08:18:45 -0400, clipka wrote:
> Jim Henderson <nos### [at] nospam com> wrote:
>> > Can a firewall filter certain NGs out (maybe that have ".org" in them
>> > instead of ".com")?
>>
>> Possibly; you'd have to ask your firewall administrator.
>
> If even telnet to the port won't work, it cannot be a NG-specific
> filter, can it?
>
> So looks like the whole NG server is deliberately filtered out (or, more
> likely, not deliberately "filtered in").
Not group-specific, the entire server is blocked, either intentionally or
not.
I took Eric's post to mean "news server" because he mentioned ".org" vs.
".com" - that would be server-based rather than group-based, since the
group doesn't have the server's name or DNS entry in it.
Thinking about it a little more, I wonder what would happen if he used
the server's IP address rather than the DNS name.
Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Jim Henderson wrote:
> Thinking about it a little more, I wonder what would happen if he used
> the server's IP address rather than the DNS name.
Nothing different: the firewall doesn't even get to see the name. By the time
the packet reaches the firewall, the IP address has already been determined
(done by a DNS lookup on the client PC). Most likely the firewall admins have
specifically added a rule to allow access to the Microsoft news groups. It's not
uncommon for corporate firewalls to not allow access to NNTP in general.
-- Chris
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Mon, 11 May 2009 16:46:48 +1000, Chris Cason wrote:
> Jim Henderson wrote:
>> Thinking about it a little more, I wonder what would happen if he used
>> the server's IP address rather than the DNS name.
>
> Nothing different: the firewall doesn't even get to see the name. By the
> time the packet reaches the firewall, the IP address has already been
> determined (done by a DNS lookup on the client PC). Most likely the
> firewall admins have specifically added a rule to allow access to the
> Microsoft news groups. It's not uncommon for corporate firewalls to not
> allow access to NNTP in general.
In general I'd agree, but I have seen some weird things done with
firewalls in the past.
Or it could be something odd being done at the DNS level to deny specific
domains.
But you're probably right - it's probably a blanket exclusion with a
specific inclusion for the MS newsgroups server - that would be the
easiest to implement. :-)
Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |