cant connect using remote desktop from win 32 to win 64 on home network

i googled this= no help, so im asking here
here are my stats
1 pc=win 7 32 other pc=win7 64
verizon home network =192.168-1.x
both pc's have norton 360
i want to connect to the win64 pc. i added the subnet and my IP that
i want to allow into norton 360 on the win64 pc. i enabled connect
remote desktop on the win 64 pc. i can ping it. if i use vnc
professional i can connect. i want to use windows remote desktop
because its part of windows and vnc professional cost money. ( i am a
unemployed help desk manager/tech who cant find a friggin job in NJ
after sending out 60 resumes so $ is tight)
when i mstsc in and type in the remote IP or name from my pc, i get
cant connect error. im out of ideas as to why i cant connect via
remote desktop. i googled and didnt find an answer.
thanks for a clue

<MetalStorm©> wrote in message
news:...
> i googled this= no help, so im asking here
> here are my stats
> 1 pc=win 7 32 other pc=win7 64
> verizon home network =192.168-1.x
> both pc's have norton 360
> i want to connect to the win64 pc. i added the subnet and my IP that
> i want to allow into norton 360 on the win64 pc. i enabled connect
> remote desktop on the win 64 pc. i can ping it. if i use vnc
> professional i can connect. i want to use windows remote desktop
> because its part of windows and vnc professional cost money. ( i am a
> unemployed help desk manager/tech who cant find a friggin job in NJ
> after sending out 60 resumes so $ is tight)
> when i mstsc in and type in the remote IP or name from my pc, i get
> cant connect error. im out of ideas as to why i cant connect via
> remote desktop. i googled and didnt find an answer.
> thanks for a clue

Is remote desktop turn on in the remote PC? When you made the firewall mods,
you said all traffic form the local (192.168.1.x) subnet? Or just certain
ports? RDP uses different ports than VNC and PING (ICMP). If you are
controlling at the port level you need to open 3389 for RDP.

On 1/25/2012 7:16 PM, MetalStorm© wrote:
> i googled this= no help, so im asking here
> here are my stats
> 1 pc=win 7 32 other pc=win7 64
> verizon home network =192.168-1.x
> both pc's have norton 360
> i want to connect to the win64 pc. i added the subnet and my IP that
> i want to allow into norton 360 on the win64 pc. i enabled connect
> remote desktop on the win 64 pc. i can ping it. if i use vnc
> professional i can connect. i want to use windows remote desktop
> because its part of windows and vnc professional cost money. ( i am a
> unemployed help desk manager/tech who cant find a friggin job in NJ
> after sending out 60 resumes so $ is tight)
> when i mstsc in and type in the remote IP or name from my pc, i get
> cant connect error. im out of ideas as to why i cant connect via
> remote desktop. i googled and didnt find an answer.
> thanks for a clue

RDP services are only available on specific editions of Windows 7,
namely Enterprise, Professional, and Ultimate. It doesn't matter if it's
32- or 64-bit. All editions of Windows include an RDP client software,
but only those 3 editions include the RDP service. ( http://is.gd/lYM4HS )

If you're looking for a cheap VNC solution (free), try TightVNC. (
http://is.gd/k8Nv6P )

Yousuf Khan

"Yousuf Khan" <> wrote in message news:fd-...
> On 1/25/2012 7:16 PM, MetalStorm© wrote:
>> i googled this= no help, so im asking here
>> here are my stats
>> 1 pc=win 7 32 other pc=win7 64
>> verizon home network =192.168-1.x
>> both pc's have norton 360
>> i want to connect to the win64 pc. i added the subnet and my IP that
>> i want to allow into norton 360 on the win64 pc. i enabled connect
>> remote desktop on the win 64 pc. i can ping it. if i use vnc
>> professional i can connect. i want to use windows remote desktop
>> because its part of windows and vnc professional cost money. ( i am a
>> unemployed help desk manager/tech who cant find a friggin job in NJ
>> after sending out 60 resumes so $ is tight)
>> when i mstsc in and type in the remote IP or name from my pc, i get
>> cant connect error. im out of ideas as to why i cant connect via
>> remote desktop. i googled and didnt find an answer.
>> thanks for a clue
>
> RDP services are only available on specific editions of Windows 7, namely Enterprise, Professional, and Ultimate. It
> doesn't matter if it's 32- or 64-bit. All editions of Windows include an RDP client software, but only those 3
> editions include the RDP service. ( http://is.gd/lYM4HS )
>
> If you're looking for a cheap VNC solution (free), try TightVNC. ( http://is.gd/k8Nv6P )
>
> Yousuf Khan
>
>

Even though you gave a viable response, he won't see it; he posted in his rant that he's deleting this group from his PC
ASA he sent the post. That was an hour before your reply.
Too bad for him. I know my patience level is kinda on the low side, but I don't believe I would rant like he did after
only a day and a half, aside from the fact that he got a reply about an hour and a half after his original post.

Thanks for the info; I'm sure someone somewhere along the line will find it useful, even if MetalStorm doesn't :-)
--
SC Tom

P.S. I have used TightVNC both at work and at home and found it very easy to set up and use.

MetalStorm© wrote:

> i googled this= no help, so im asking here
> here are my stats
> 1 pc=win 7 32 other pc=win7 64
> verizon home network =192.168-1.x
> both pc's have norton 360
> i want to connect to the win64 pc. i added the subnet and my IP that
> i want to allow into norton 360 on the win64 pc. i enabled connect
> remote desktop on the win 64 pc. i can ping it. if i use vnc
> professional i can connect. i want to use windows remote desktop
> because its part of windows and vnc professional cost money. ( i am a
> unemployed help desk manager/tech who cant find a friggin job in NJ
> after sending out 60 resumes so $ is tight)
> when i mstsc in and type in the remote IP or name from my pc, i get
> cant connect error. im out of ideas as to why i cant connect via
> remote desktop. i googled and didnt find an answer.
> thanks for a clue

To any further potential respondents, don't bother replying to this
thread. Go look at the, um, super-intelligence exhibited by this same
poster in his "what a bunch of a-holes" thread posted 2 days later.

Oh yes, this guy really knows how to engender help from others. I
shudder to think what kind of "help" he gave at his old helpdesk job.
Tis no surprise why he got canned.

VanguardLH <> wrote in
news:jfv8h3$o7l$:


> Oh yes, this guy really knows how to engender help from
> others. I shudder to think what kind of "help" he gave at
> his old helpdesk job. Tis no surprise why he got canned.

Probably the same help I get from help-desk support....none.

99% of the poeple that are level 1 phone support are inept.