Originally posted by Gandalf Parker: As to routers, whether or not that properly handles reverse lookups isnt under the control of the IRC server. Its at the router end
If someone (like myself) was connecting just fine to a server, for weeks, and then suddenly I (and many others) cannot, the fault lies on the other end ...
Are you allowing TCP/113 in and do you allow ident in your IRC client? Many IRC servers do ident, if there's no response they may decide to "ban" you (not you in particular, but rather clients who has 113 blocked, or not responding to ident).
Originally posted by alexti: Are you allowing TCP/113 in and do you allow ident in your IRC client? Many IRC servers do ident, if there's no response they may decide to "ban" you (not you in particular, but rather clients who has 113 blocked, or not responding to ident).
Ident is on. I'll have to check on the port ...
EDIT: I added TCP/113 to the router table and that fixed the problem! Thanks! In my defense, it was working fine until IRCnet must have updated their end to start checking.
[ March 02, 2004, 01:16: Message edited by: Arryn ]