RDC connecting to Win XP Pro Machine from OS X 10.3.2

Bill.

Thanks for the prompt answer.

Yes Terminal Services are on.

I assigned a password to the primary user account in XP. Still no go
with the connection it appears to run but never engage...

Any other suggestions would be great.

Thanks greatly,
Mark.

"Bill Sanderson" <Bill_Sanderson RemoveThis @msn.com.plugh.org> wrote in message news:<O4PXFs$zDHA.2328@TK2MSFTNGP10.phx.gbl>...
 > To make this work, you'll need a username on A, and a password associated
 > with that username (i.e. the username must have a password for you to
 > connect remotely or across a network, by default)
 >
 > Hmm - you say you can do file and print sharing, but not RD.....
 >
 > That would seem to let the firewall off the hook, but maybe not--it could be
 > open to allow file and print on a local subnet, but not other protocols?
 >
 > On the PC A, Start, run, services.msc <enter>
 >
 > Scroll down to Terminal Services. Is it started?
 >
 >
 > "Mark Young" <ma.young RemoveThis @optusnet.com.au> wrote in message
 > news:41fcc581.0312311530.433a9ea4@posting.google.com...
  > > Folks,
  > >
  > > I'm new to RDC so these may seem like really silly questions. I need
  > > the assistance of a RDC guru.
  > >
  > > My setup is as follows I have a
  > >
  > > 12" PB with Airport Extreme connecting to AEBS that is connected to a
  > > cable modem in turn. We will call this "A".
  > >
  > > PC Laptop with Win XP Pro with a 802.11b Wireless LAN card that
  > > connects to the AEBS. We will call this "B".
  > >
  > > I have enabled Windows File Sharing on A, and B happily connects to
  > > it.
  > >
  > > B is on no network. Its name is PCLaptop and the workgroup is
  > > workgroup.
  > >
  > > I've tried connecting with RDC from A using both its name and its IP
  > > address, with the name it states that the client cannot connect, and
  > > with the IP address it just tries but never connects.
 >
  > >
  > > Note also that B has McAfee Firewall, I've disabled it and still no
  > > difference. I have also made sure to enable remote desktop etc on the
  > > properties tag of My Computer.
  > >
  > > I've left the username and passsword blank.
  > >
  > > Any assistance that can be offered would be great.
  > >
  > > Many Thanks in Advance.
  > >
  > > Mark Young<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: RDC connecting to Win XP Pro Machine from OS X 10.3.2 

Bill, did you ever figure this out? I have an iBook that's
doing the same thing.


 >-----Original Message-----
 >Bill.
 >
 >Thanks for the prompt answer.
 >
 >Yes Terminal Services are on.
 >
 >I assigned a password to the primary user account in XP.
Still no go
 >with the connection it appears to run but never engage...
 >
 >Any other suggestions would be great.
 >
 >Thanks greatly,
 >Mark.
 >
 >"Bill Sanderson" <Bill_Sanderson RemoveThis @msn.com.plugh.org> wrote
in message news:<O4PXFs$zDHA.2328@TK2MSFTNGP10.phx.gbl>...
  >> To make this work, you'll need a username on A, and a
password associated
  >> with that username (i.e. the username must have a
password for you to
  >> connect remotely or across a network, by default)
  >>
  >> Hmm - you say you can do file and print sharing, but
not RD.....
  >>
  >> That would seem to let the firewall off the hook, but
maybe not--it could be
  >> open to allow file and print on a local subnet, but not
other protocols?
  >>
  >> On the PC A, Start, run, services.msc <enter>
  >>
  >> Scroll down to Terminal Services. Is it started?
  >>
  >>
  >> "Mark Young" <ma.young RemoveThis @optusnet.com.au> wrote in
message
  >> news:41fcc581.0312311530.433a9ea4@posting.google.com...
   >> > Folks,
   >> >
   >> > I'm new to RDC so these may seem like really silly
questions. I need
   >> > the assistance of a RDC guru.
   >> >
   >> > My setup is as follows I have a
   >> >
   >> > 12" PB with Airport Extreme connecting to AEBS that
is connected to a
   >> > cable modem in turn. We will call this "A".
   >> >
   >> > PC Laptop with Win XP Pro with a 802.11b Wireless LAN
card that
   >> > connects to the AEBS. We will call this "B".
   >> >
   >> > I have enabled Windows File Sharing on A, and B
happily connects to
   >> > it.
   >> >
   >> > B is on no network. Its name is PCLaptop and the
workgroup is
   >> > workgroup.
   >> >
   >> > I've tried connecting with RDC from A using both its
name and its IP
   >> > address, with the name it states that the client
cannot connect, and
   >> > with the IP address it just tries but never connects.
  >>
   >> >
   >> > Note also that B has McAfee Firewall, I've disabled
it and still no
   >> > difference. I have also made sure to enable remote
desktop etc on the
   >> > properties tag of My Computer.
   >> >
   >> > I've left the username and passsword blank.
   >> >
   >> > Any assistance that can be offered would be great.
   >> >
   >> > Many Thanks in Advance.
   >> >
   >> > Mark Young
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: RDC connecting to Win XP Pro Machine from OS X 10.3.2 

"same thing" in this case covers a multitude of issues. (i.e. anything
preventing communication with the target host on port 3389, via RDP) This
can be anything from firewalls, proxies, to system policy settings on the XP
host preventing RDP from running--although I think there'd be other
indicators in that case.

No--I really couldn't think of the salient question to ask, I'm afraid.

Can you ping?

Do you have a telnet utility?
If so, what happens if you telnet to port 3389 at the target host IP?

On the XP host, drop to a cmd prompt and type in qwinsta.exe <enter>

Do you see something like this?

SESSIONNAME USERNAME ID STATE TYPE DEVICE
 >console Bills 0 Active wdcon
rdp-tcp 65536 Listen rdpwd

"Campy" <anonymous.DeleteThis@discussions.microsoft.com> wrote in message
news:05a301c3da3f$b001f920$a401280a@phx.gbl...
 > Bill, did you ever figure this out? I have an iBook that's
 > doing the same thing.
 >
 >
  >>-----Original Message-----
  >>Bill.
  >>
  >>Thanks for the prompt answer.
  >>
  >>Yes Terminal Services are on.
  >>
  >>I assigned a password to the primary user account in XP.
 > Still no go
  >>with the connection it appears to run but never engage...
  >>
  >>Any other suggestions would be great.
  >>
  >>Thanks greatly,
  >>Mark.
  >>
  >>"Bill Sanderson" <Bill_Sanderson.DeleteThis@msn.com.plugh.org> wrote
 > in message news:<O4PXFs$zDHA.2328@TK2MSFTNGP10.phx.gbl>...
   >>> To make this work, you'll need a username on A, and a
 > password associated
   >>> with that username (i.e. the username must have a
 > password for you to
   >>> connect remotely or across a network, by default)
   >>>
   >>> Hmm - you say you can do file and print sharing, but
 > not RD.....
   >>>
   >>> That would seem to let the firewall off the hook, but
 > maybe not--it could be
   >>> open to allow file and print on a local subnet, but not
 > other protocols?
   >>>
   >>> On the PC A, Start, run, services.msc <enter>
   >>>
   >>> Scroll down to Terminal Services. Is it started?
   >>>
   >>>
   >>> "Mark Young" <ma.young.DeleteThis@optusnet.com.au> wrote in
 > message
   >>> news:41fcc581.0312311530.433a9ea4@posting.google.com...
   >>> > Folks,
   >>> >
   >>> > I'm new to RDC so these may seem like really silly
 > questions. I need
   >>> > the assistance of a RDC guru.
   >>> >
   >>> > My setup is as follows I have a
   >>> >
   >>> > 12" PB with Airport Extreme connecting to AEBS that
 > is connected to a
   >>> > cable modem in turn. We will call this "A".
   >>> >
   >>> > PC Laptop with Win XP Pro with a 802.11b Wireless LAN
 > card that
   >>> > connects to the AEBS. We will call this "B".
   >>> >
   >>> > I have enabled Windows File Sharing on A, and B
 > happily connects to
   >>> > it.
   >>> >
   >>> > B is on no network. Its name is PCLaptop and the
 > workgroup is
   >>> > workgroup.
   >>> >
   >>> > I've tried connecting with RDC from A using both its
 > name and its IP
   >>> > address, with the name it states that the client
 > cannot connect, and
   >>> > with the IP address it just tries but never connects.
   >>>
   >>> >
   >>> > Note also that B has McAfee Firewall, I've disabled
 > it and still no
   >>> > difference. I have also made sure to enable remote
 > desktop etc on the
   >>> > properties tag of My Computer.
   >>> >
   >>> > I've left the username and passsword blank.
   >>> >
   >>> > Any assistance that can be offered would be great.
   >>> >
   >>> > Many Thanks in Advance.
   >>> >
   >>> > Mark Young
  >>.
  >><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: RDC connecting to Win XP Pro Machine from OS X 10.3.2 

Hi Bill,

I guess I could have been more descriptive. I'm able to
connect to the XP machine via file sharing, when I use the
RDC it apears to be up and running but I'm unable to see
anything; it's also using between 70-80% of the processor
on the iBook. I was able to test the connection to the XP
machine from my iMac using RDC at home last night and it
worked fine. Are there any config files or settings that
may need to be deleted? I did delete the RDC prefs, and
recent servers files but I couldn't find anything else
relating to RDC. I also watched the log files while trying
the connection from the iBook looking for some clues but
no luck. Stumped.

Campy


 >-----Original Message-----
 >"same thing" in this case covers a multitude of issues.
(i.e. anything
 >preventing communication with the target host on port
3389, via RDP) This
 >can be anything from firewalls, proxies, to system policy
settings on the XP
 >host preventing RDP from running--although I think
there'd be other
 >indicators in that case.
 >
 >No--I really couldn't think of the salient question to
ask, I'm afraid.
 >
 >Can you ping?
 >
 >Do you have a telnet utility?
 >If so, what happens if you telnet to port 3389 at the
target host IP?
 >
 >On the XP host, drop to a cmd prompt and type in
qwinsta.exe <enter>
 >
 >Do you see something like this?
 >
 > SESSIONNAME USERNAME ID STATE
TYPE DEVICE
  >>console Bills 0 Active
wdcon
 > rdp-tcp 65536 Listen
rdpwd
 >
 >"Campy" <anonymous RemoveThis @discussions.microsoft.com> wrote in
message
 >news:05a301c3da3f$b001f920$a401280a@phx.gbl...
  >> Bill, did you ever figure this out? I have an iBook
that's
  >> doing the same thing.
  >>
  >>
   >>>-----Original Message-----
   >>>Bill.
   >>>
   >>>Thanks for the prompt answer.
   >>>
   >>>Yes Terminal Services are on.
   >>>
   >>>I assigned a password to the primary user account in XP.
  >> Still no go
   >>>with the connection it appears to run but never
engage...
   >>>
   >>>Any other suggestions would be great.
   >>>
   >>>Thanks greatly,
   >>>Mark.
   >>>
   >>>"Bill Sanderson" <Bill_Sanderson RemoveThis @msn.com.plugh.org>
wrote
  >> in message
news:<O4PXFs$zDHA.2328@TK2MSFTNGP10.phx.gbl>...
   >>>> To make this work, you'll need a username on A, and a
  >> password associated
   >>>> with that username (i.e. the username must have a
  >> password for you to
   >>>> connect remotely or across a network, by default)
   >>>>
   >>>> Hmm - you say you can do file and print sharing, but
  >> not RD.....
   >>>>
   >>>> That would seem to let the firewall off the hook, but
  >> maybe not--it could be
   >>>> open to allow file and print on a local subnet, but
not
  >> other protocols?
   >>>>
   >>>> On the PC A, Start, run, services.msc <enter>
   >>>>
   >>>> Scroll down to Terminal Services. Is it started?
   >>>>
   >>>>
   >>>> "Mark Young" <ma.young RemoveThis @optusnet.com.au> wrote in
  >> message
   >>>>
news:41fcc581.0312311530.433a9ea4@posting.google.com...
   >>>> > Folks,
   >>>> >
   >>>> > I'm new to RDC so these may seem like really silly
  >> questions. I need
   >>>> > the assistance of a RDC guru.
   >>>> >
   >>>> > My setup is as follows I have a
   >>>> >
   >>>> > 12" PB with Airport Extreme connecting to AEBS that
  >> is connected to a
   >>>> > cable modem in turn. We will call this "A".
   >>>> >
   >>>> > PC Laptop with Win XP Pro with a 802.11b Wireless
LAN
  >> card that
   >>>> > connects to the AEBS. We will call this "B".
   >>>> >
   >>>> > I have enabled Windows File Sharing on A, and B
  >> happily connects to
   >>>> > it.
   >>>> >
   >>>> > B is on no network. Its name is PCLaptop and the
  >> workgroup is
   >>>> > workgroup.
   >>>> >
   >>>> > I've tried connecting with RDC from A using both its
  >> name and its IP
   >>>> > address, with the name it states that the client
  >> cannot connect, and
   >>>> > with the IP address it just tries but never
connects.
   >>>>
   >>>> >
   >>>> > Note also that B has McAfee Firewall, I've disabled
  >> it and still no
   >>>> > difference. I have also made sure to enable remote
  >> desktop etc on the
   >>>> > properties tag of My Computer.
   >>>> >
   >>>> > I've left the username and passsword blank.
   >>>> >
   >>>> > Any assistance that can be offered would be great.
   >>>> >
   >>>> > Many Thanks in Advance.
   >>>> >
   >>>> > Mark Young
   >>>.
   >>>
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: RDC connecting to Win XP Pro Machine from OS X 10.3.2