To make your life easier in the future I suggest using port 80 instead. Port 80 is the port that HTML (www.yoursite.com) goes over so it's almost a 'universal' port number. By using port 80 instead of 7000 then if you switch your hosting service to a different company in the future then you'll know that you don't have to go through this all over again with asking them to open up a different port number.

Hi

I have had port 119 enabled on my dedicated server but i still get
Connecting to server, server says: 502 Permission Denied - Permission Denied -- http://www.highwinds-software.com/ (Tornado v1.0.6.380)

Info for uk.media.tv.misc at news.ntlworld.com:

Connecting to server, server says: 502 Permission Denied - Permission Denied -- http://www.highwinds-software.com/ (Tornado v1.0.6.380)

Info for alt.binaries.movies.divx at news.ntlworld.com:

This happens whenever i try to connect to the news.ntlworld.com (free server)
Or when i try to connect to my paid newshosting server

Any thoughts on this please?

Do you get such errors even if you login manually?

Sorry, can you elaborate, not quite sure what ya mean by login manually?

When you say free, do you mean the service which you get with your broadband provider on your home pc? If so, they probably perform an IP check and when it is not coming from a non-NTL line (which your ded server won't), it won't connect. The first time I got this hack I tried using the free BT service I got (and failed).

If you are getting this with a paid service (e.g. giganews, teranews etc), then I would guess the most common reason is username & password issues. Can you log in with these on a normal newsreader? The fact you are getting permission denied errors means the port is problably enabled correctly, or you wouldn't have got this far. What paid service have you gone for?

I am using newshosting, have been for about a year now, i copied and pasted the login details so theres no mistyping..... The only server i have managed to connect to is the free Microsoft 1

Manually with, for example, a news client. I was thinking of the 502-message, that may indicate missing username/password.

ah right, yeah im downloading with grabit as we speak lol

For aesthetic reasons, I prefer not to have the "Re :" in the subject line created by incoming Usenet threads/posts even if it is a reply. vBulletin doesn't use such formatting and any reply post leaving our system via the gateway will get the "Re: " pre-appended to the subject line for Usenet compatability.

If you likewise wish to remove the incoming "Re: " from the subject line, find the following line in gateway.php:

After the above line, simply insert the following:

If you wish to change your entire message database to remove any prior "Re: " in both threads and posts, just look for my prior post #396 in this thread which indicates the two mySQL queries to do so. Once done, all your threads/posts will be in this same format.

Again, this is only an aesthetic choice for me and shouldn't be considered a bug fix. I hope others might find it useful. If anyone sees any code conflict here, please advise.

Regards. -- Rik

ps: I'm not a PHP programmer so anything I say must be taken at your own risk. Backup your database first. But I've been using this change for several weeks now and all appears working fine.

After the above coding, NNTP_GW attempts to match the incoming post to vb threads "by reference" or "by subject." I'd prefer to make that a single lookup by subject at a future time as threading is already mangled if you are using a killfile that breaks thread sequences. Note, for example, that if the first message in a thread was deleted by your killfile, message #2 will now start a new thread without any "Re: " in it.

How about a single line?