identd hijacking - mIRC Discussion Forums

If someone connects to mIRC's identd server before the server can, mIRC will turn it off too soon and not reply to the real one

[06:11:58] * Connecting to 216.115.95.70 (6667)
-
* Identd request from 204.***.***.***
* Identd replied: 1149, 6667 : USERID : UNIX : goplat
-
[06:13:32] Closing Link: (Authentication Timeout)

i don't think there's a way to solve that because the network you might be connecting to may use another ip to connect to your ident server.

One way to go about that is to enable the ident server all the time.

Hm. Maybe mIRC should close the ident server when it gets 001 from all the servers that are in a "Connecting" state.

Quote:

Originally posted by "pegasus21" i don't think there's a way to solve that because the network you might be connecting to may use another ip to connect to your ident server.

Quote:

Originally posted by "IDENT rfc"
QUERY/RESPONSE FORMAT

The server accepts simple text query requests of the form:

<port-on-server> , <port-on-client>

The response is of the form

<port-on-server> , <port-on-client> : <resp-type> : <add-info>

mIRC knows both the port of the client connecting and the port of the server and can (and should) only reply to a request which supplies the correct port pair

I don't use the mIRC identd, but leave it on all the time and use a seperate identd server software for Windows and it works everytime. Try the one I use from: http://identd.dyndns.org/identd/