Okay.. the ordeal continues.. I am still receiving the same problem.. Ive set sockets timeout via the SetSocketOptions but it appears to do nothing with asynchronous sockets. so then i moved onto another solution - which was to create a new thread which would wiat for a certain time period to elapse.. once it does it would manually kill the socket. unfornately this did nothing.. also - i contact the isp and the are not doing anything so that idea is out the door.. any suggestions.. the basic problem is setting a timeout on a socket which is being use in async communications.. any suggestion. im starting to get disperate :( Danny!

[http://groups.google.com/groups?q=VS.NET+Outlook+add+in&hl= en&lr=&ie=UTF-8&oe=UTF-8&selm=%23BDiKy%23qBHA.1860%40tkmsft ngp04&rnum=2](http://groups.google.com/groups?q=VS.NET+Outlook+add+in&hl= en&lr=&ie=UTF-8&oe=UTF-8&selm=%23BDiKy%23qBHA.1860%40tkmsft ngp04&rnum=2)[[^](http://groups.google.com/groups?q=VS.NET+Outlook+add+in&hl= en&lr=&ie=UTF-8&oe=UTF-8&selm=%23BDiKy%23qBHA.1860%40tkmsft ngp04&rnum=2 "New Window")] You will now find yourself in a wonderous, magical place, filled with talking gnomes, mythical squirrels, and, almost as an afterthought, your bookmarks -Shog9 teaching Mel Feik how to bookmark I don't know whether it's just the light but I swear the database server gives me dirty looks everytime I wander past. -Chris Maunder