Man, I think you have a very nasty bug in workers management.
If I use de server (176.9.42.247), and I have one worker working (my client connected to it and mining), and I change its name, then hell breaks loose. The old worker will still be available and new worker name wont be usable anymore (anything I send trough it isnt recorded), even if I change it later, create a new worker with this new name after I freed the name. More, any worker which was somehow in contact with this scheme wont be usable anymore. Check user 41599, worker with extension _h3m5.
If I use de server (176.9.42.247), and I have one worker working (my client connected to it and mining), and I change its name, then hell breaks loose. The old worker will still be available and new worker name wont be usable anymore (anything I send trough it isnt recorded), even if I change it later, create a new worker with this new name after I freed the name. More, any worker which was somehow in contact with this scheme wont be usable anymore. Check user 41599, worker with extension _h3m5.
Old workers will still be available and still work because the server caches them. Similarly, BAD worker logins are cached. You obviously renamed your worker but tried to connect before renaming it, causing it to get added to the bad worker list. The server caches bad logins to prevent somebody from flooding the server with bad logins and forcing constant MySQL lookups to bog the server down. Old mining software used to reconnect with no delay when a connection failed, which resulted in flooding the pool server -and- database server due to the worker lookups.
If you were using the DE Stratum server (which can be connected to by ANY stratum supporting client by just pointing them at de.btcguild.com), this problem would only persist for about a minute before the bad worker cache was cleared. I don't recall how often the getwork pool clears its worker cache. At this point the getwork pool is barely supported, and simply left online while people upgrade to stratum mining clients.
Either way, this only occurs because you were trying to connect to the pool using invalid credentials initially, THEN renamed the worker later, leaving the old name in the bad worker cache.
