No, I really haven't noticed it specifically happening on one server and not the next. When it was occuring, it would happen no matter where I was connected. But, like I said in an earlier post connecting with an IP instead of the host name and using port 7000 instead of default 6667 stopped the error for the second time. I am sure I will be back when it happens again, and I will let you guys know what fixed it then! hehe
Thanks ParaBrat for your help!
Darvocet (Dalnet)
#Darvocet :tongue:
