Gil, But XP Pro comes with a built in TS License. Dave Crozier
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of mrgmhale Sent: 03 August 2007 13:51 To: [email protected] Subject: RE: [NF] Terminal services problem Are you, by chance, hitting a Windows 2003 Server using TS (as opposed to Remote Desktop)? If so, then you are in for an expensive surprise. With Server 2003, unlike Server 2000 and NT4 Server, TS is no longer offered as part of the Server OS on a No Additional Charge basis. We used to get TS under a "Machine Equivalency" basis, until 2003 Server. With 2003 Server you have 180 days from the time you first implement it to license a TS license on either a per machine or per User basis. A 5 pack TS Client license retails for about $750USD. I am certain the 180 day Free Ride is there to get you hooked on TS. I found this out after recommending 2003 Server at a new client location, not realizing the change in the game with M$. It is not my client's fault, so if it turns out they decide to use TS for my app over a thin-net between their multiple locations I am going to absorb the license cost. I did manage to get 2 TS license key codes for free, as M$ had benevolently offered No Charge TS licenses for XP Pro users who purchased XP Pro before 2003 Server was released, but that offer expired at the end of June 30, 2007. I can not begin to tell you in non-violent terms how angry I am with M$ for such a subtle, and underhanded change in licensing. But it is what it is, and as long as I am stuck in a Windows environment these are the kinds of goodies I will end up having to deal with perpetually as M$ tries to skin End Users any which way they can. I hope this is not what you have run into. Did you implement TS/RD about 6 months ago against that particular Server? Gil > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of James E Harvey > Sent: Friday, August 03, 2007 8: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: [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.
