<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/winidentd/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/winidentd/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/winidentd/bugs/</id><updated>2003-04-09T16:36:08Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>Ident service fails to respond</title><link href="https://sourceforge.net/p/winidentd/bugs/2/" rel="alternate"/><published>2003-04-09T16:36:08Z</published><updated>2003-04-09T16:36:08Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netbe04a20acb63014780b072b4c6b9165a7bf7dc4b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When a fast browser such as Mozilla 1.3 or IE6 is&lt;br /&gt;
hitting the squid proxy, and squid is doing an ident&lt;br /&gt;
lookup for every get/post/connect request, some ident&lt;br /&gt;
queries will fail. It appears that this ident service&lt;br /&gt;
either rejects the connection, or simply doesnt respond&lt;br /&gt;
to that particular ident request.&lt;/p&gt;
&lt;p&gt;The only systems that seem to exhibit this symptom are&lt;br /&gt;
the fastest boxes we have - P4 2Ghz systems.&lt;/p&gt;
&lt;p&gt;The clients are NT4sp6a, and Win2K all running NetWare&lt;br /&gt;
client 4.83sp1.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Identd service stops after portscan</title><link href="https://sourceforge.net/p/winidentd/bugs/1/" rel="alternate"/><published>2003-04-09T15:56:44Z</published><updated>2003-04-09T15:56:44Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net9366987f6dec72af0c373e6a34603599fd7cee83</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;If a system running this Identd service is portscanned&lt;br /&gt;
by a tool such as nmap (using default options), the&lt;br /&gt;
service stops. As far as I can tell, there are no&lt;br /&gt;
errors generated on the client side, the service just&lt;br /&gt;
unloads from memory.&lt;/p&gt;
&lt;p&gt;The clients are NT6sp6 and Win2K sp2 systems, running&lt;br /&gt;
the current Novell client (4.83sp1).&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>