OK, it looks like it may be an issue with Kaskpersky. Even when you turn Kaspersky off, it may not really be off.
Here's what I just sent the client. We'll see if this works. http://www.edugeek.net/forums/windows/32016-remote-desktop-blocked-kaspersky.html --- On Tue, 7/28/09, Stephen Russell <[email protected]> wrote: > From: Stephen Russell <[email protected]> > Subject: Re: [NF] Issue with connecting via remote desktop > To: "ProFox Email List" <[email protected]> > Date: Tuesday, July 28, 2009, 4:01 PM > On Tue, Jul 28, 2009 at 2:28 PM, > Michael Madigan<[email protected]> > wrote: > > We're not using VPN at all. > ---------- > > Are they inside the firewall or outside the firewall? > > If you say there is no firewall, which I am sure the answer > is going > to be. Are they on the premises or out in the field? > > If they are out in the field what is the IP addy they are > hitting? I > don't want the xxx.xx.... I want to know what that device > is. Is it > the web server or the DC? > > If you tell me it is the router you get from DSL/Cable I > don't know > your next step. > > -- > Stephen Russell > Sr. Production Systems Programmer > SQL Server DBA > Web and Winform Development > Independent Contractor > Memphis TN > > 901.246-0159 > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
