Are Remote Desktop and Terminal Services the same thing, I though they kind of meant the same thing, the RD was the local app, and TS was the server part?
The timeframe you mention is close although this problem started about a week or so ago. We were a Blazenet customer, they were bought out by Comcast, and it's been a difficult time since. James E Harvey Hanover Shoe Farms, Inc. M.I.S./Corresponding Officer Off: 717-637-8931 fax: 717-637-6766 email: [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of mrgmhale Sent: Friday, August 03, 2007 8:54 AM To: profox@leafe.com Subject: RE: [NF] Terminal services problem Actually, if it is RD, not TS, then a call to Comcast may be needed. When Comcast first went into Detroit one of the first things they did was block IPSec for residential subscribers, under the pretense they had to save bandwidth. A residential user could upgrade to a commercial service, at over twice the price, however <g>. I do not know what port RD runs over, but if it is not a typical port used for http, https, ftp, then they may have started to block some port signals as of August 1st. Gil > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Brian Erickson > Sent: Friday, August 03, 2007 8:23 AM > To: [EMAIL PROTECTED] > Subject: RE: [NF] Terminal services problem > > > You should not need to contact Comcast. What exactly is the message that > you are getting?? Is it that you have reached the number of active > connections?? Or that you can not connect at all. Since you getting the > login prompt you are getting to the box in the office. Someone may be on > the box and not letting you connect. > > Brian Erickson > mailto:[EMAIL PROTECTED] > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of James E Harvey > Sent: Friday, August 03, 2007 6:08 AM > To: [EMAIL PROTECTED] > Subject: [NF] Terminal services problem > > All of a sudden my Remote Desktop connection has quit working. It was > working fine up to a week ago? > > I can enter the IP address with the port range number after the colon, get > the login screen, enter the password, and then get a message announcing I > can't connect? The message makes it sound like I don't have access, not > that my username or password is incorrect. > > This is from an XP Pro laptop at home to a Vista Business pc at > the office. > The device we go through at the office is a SMC Gateway where we > set up port > forwarding. > > I've tried deleting and re-entering my port forward rule in the > SMC, but no > go. > > Comcast is my ISP, do I need to contact them (I shudder at the > thought), any > other thoughts??? > > James E Harvey > Hanover Shoe Farms, Inc. > M.I.S./Corresponding Officer > Off: 717-637-8931 > fax: 717-637-6766 > email: [EMAIL PROTECTED] > > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com 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.
