We are trying to recover from ISPs closing down port 135. We have an dedicated Exchange Server at a hosting company. 20 of our 23 people scattered around the country can not use the full functionality of Outlook/Exchange because of this problem.
We are a classic case study of how a company has suceeded in business by using most of the functionality of Outlook/Exchange. We built our 3 year old company's communications, task management, and database using the Exchange Platform, including extensive use of custom 'forms' that track hundreds of tasks and our workflow. The ISP's closing out port 135 has brought us to our knees. We are scambling just trying to stay on schedule with our committments to our clients. I have no hope that the ISPs will turn open up 135 again, so I also need an alternative way to connect to the *full* functionality we had before, or be forced to migrate completely off exchange and rebuild our entire infrastructure using another platform. We have tried to implement a VPN solution, but now realize that unless we run the connection on our client and have a full internet connection at the same time, this will not work for us. We do not know how to do this. We must have full access to the internet and exchange at the same time because of the nature of our service we provide. Any ideas? Regards, Hank _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
