Unauthorized connection from

[Cabby37]

we get this error and only half of the people can connect then at time everyone can connet then it starts this again i need some Help here PLEASE

[w00t]

While I have never encountered anything like that, it is almost a config problem for sure.

[Cabby37]

well it is funny that some can connet and some can not i am not very good at ircd but i do understand scripting i do not see problems in the ircd.conf file is there another place too look

[w00t]

Can you please put in the whole error?

[Cabby37]

[20:57] -420.coldfuzion.org- *** Notice -- Unauthorized connection from BigSmooth[66.168.39.0].

[Jason]

Make sure you have a allow block that lets in *@* without a password, and that any special allow lines you have that may have passwords have the option nopasscont (probably wrong, check docs)

[Cabby37]

let me look through my logs > [7:07am] -420.coldfuzion.org- *** Looking up your hostname...
[09:08] <Cabby37> ————————————————————
[09:08] <Cabby37> [7:07am] -420.coldfuzion.org- *** Couldn't resolve your hostname; using your IP address instead
[09:08] <Cabby37> ————————————————————
[09:08] <Cabby37> [7:07am] Closing Link: CRY0TECH[4.15.23.54] (You are not authorized to connect to this server)
[09:08] <Cabby37> ————————————————————
[09:08] <Cabby37> [7:07am] * Disconnected


that is the whole thing

[aquanight]

Check:

Your allow blocks

Remember - allow blocks are scanned upside down. If you have a passworded allow block first, you may want allow::options::nopasscont.

Your ban user blocks (?)

Your ban ip blocks (?)

Other ban * blocks (?)

[Jason]

Also make sure that you have *@* for the IP address, not something invalid (while a invalid hostname means IP ONLY auth, iirc a invalid IP doesnt mean a hostname only auth)

[AngryWolf]

To aquanight: don't give more work to Cabby37 than needed. Ban * blocks don't result in a message "you are not authorized to connect to this server", therefore it isn't necessary to check them.

To Jason: No, believe me, IP addresses don't work in allow::hostname, even if the client's hostname cannot be resolved (neither says the documentation). For example, a simple allow block with 'INVALID' as a userip mask and '*@192.168.0.1' as a hostname mask doesn't let me in if I try to connect from 192.168.0.1.

To Cabby37: a connection becomes unauthorized when it can't match any of the allow configuration blocks. I know it's not easy to configure the allow blocks, but I'm sure you can do that by carefully reading the documentation. (That's all I can help, because I can't see your allow blocks and don't know what you want to have configured.) If you still need help, provide us some details.

[Cabby37]

Thanks all i got my leaf fixed