Ah, Joe, I have to actually "Answer" the question for it to register
as answered. You see, with troubleshooting problems, I use "Clarify
Question" because the nature of computer troubleshooting requires
back-and-forth correspondence, something that cannot be provided by a
single answer. If the troubleshooting eventually works out, then I
post the prior correspondence as an answer.
I'm glad I could be of help. Below is the text of our prior discussion.
- supermacman-ga
*********************************************
Hello,
Can you ping the Windows machine from your Mac? (Do you know how to do
this? If not, say so and I will provide step-by-step instructions)
As well, is your Windows machine running XPHome or XPPro? According to
the link you posted, it only works with XP Pro machines.
- supermacman-ga
--------------------------------------------------------------------------------
Clarification of Question by ext237-ga on 06 Apr 2004 17:19 PDT
Hi supermacman!
Yes, I can ping the PC using it's IP addy. And I'm using XP Pro.
Remote Desktop is turned on, XP Firewall is turned off, and the router
is on the same LAN (only two machines, the Mac and PC). VNC is
painfully slow.
I also have ZoneAlarm on the PC, but remove it from memory when trying
to connect to the PC with the Mac.
The Mac is OSX.3.3 -- Let me know if there's anything else I can provide!
THANKS again for the help!
--------------------------------------------------------------------------------
Request for Question Clarification by supermacman-ga on 06 Apr 2004 20:05 PDT
Suggestions:
1) http://support.microsoft.com/default.aspx?scid=kb;en-us;306759
According to this MS knowledge base article, the Mac client only
supports RDC connections on port 3389. Perhaps the Windows XP machine
at home is set to a different port. You can check the registry key (as
detailed in the directions in the KB article) to see if the port is
set to something other than 3389.
2) Connecting your Mac directly to your Windows machine, then manually
setting IP addresses.
Procedure:
a) Manually enter IP addresses into the XP Networking setup panel
(i.e. 10.10.10.10). Make sure to use designated local addresses
(10.x.x.x, 192.128.x.x, etc.)
b) Manually enter a corresponding address into the Mac Network pane of
System Preferences (i.e. 10.10.10.11)
c) Very important: Make sure both have the same subnet mask. You can
leave other fields blank (router, DNS, gateway).
d) You can use a standard patch cable to connect your XP box and your
G5; the Mac Ethernet port automatically compensates for wiring
problems.
e) Check that your Mac has no other IP addresses. (It should only have
one.) It could be possible that your Mac has setup multiple network
configurations in such a way that it sends Internet traffic to the
router but tries to establish RDC connections via an isolated subnet.
To do this, refer to "Network Configurations" below.
Try connecting now. If you are able to connect, then your router may
be the problem; I would suggest retrying the setup with IP addresses
similar to the ones given out by the router.
3) Bring your Windows XP box to work and try connecting. (Try this as
a last resort.)
Some of my suggestions may seem unlikely to work; I tend to do this
when troubleshooting. But computers are unpredictable beasts, so try
everything; you never know what might happen!
I hope this helps - look forward to hearing back from you.
- supermacman-ga
Network configurations (for Panther, Mac OS X 10.3.x.
(I put this in a separate section because I don't want to insult your
intelligence if you how to do this)
a) Open System Preferences: Network.
b) Click on the drop-down tab labelled "Show:" and choose "Network Status".
c) Read the entries listed. Does it have multiple addresses?
--------------------------------------------------------------------------------
Request for Question Clarification by supermacman-ga on 06 Apr 2004 20:09 PDT
Here are more suggestions.
1) Using the WinXP machine's IP address, run Network Utility and do a
Port Scan on your machine. You can check if Port 3389 (or any other
ports) are open. Port scan is not 100% reliable, so it may miss open
ports (particularly if they have high numbers. You can get around this
by telling the program to scan for a limited range of ports; i.e. 3300
to 3400.
2) Can you remove Zone Alarm? There are two reasons for this:
a) If you can remove it from memory, then so can a malicious program.
Perhaps the program is designed to be resistant to such attacks; you
may need to remove it. Besides, you can always reinstall the program.
b) Your router provides a substantial level of protection already,
through NAT (http://www.cable-modems.org/articles/internet_sharing/software_firewall.htm).
From this page, I quote:
---
NAT makes the machines on the local network behind the gateway machine
more secure essentially because the client computers on the local
network use IP addresses that are reserved for use on internal
networks only. Those IP addresses will not show up on the internet.
---
Therefore, ZoneAlarm is somewhat unnecessary.
Again, lots of suggestions, but I have my fingers crossed that at
least one will work =)
- supermacman-ga
Clarification of Question by ext237-ga on 09 Apr 2004 06:45 PDT
supermacman: All of your suggestions were very helpful, and helped
resolve some issues that prevented me from logging into the WinXP box.
But there was yet one more issue that I stumbled on, just for future
note.
In the "services" pane of the WindowsXP Pro Management tool, there is
a listing called "Terminal Services". All services can be "Automatic"
(automatically starts when needed), "Manual" (requires manual
starting), and "Disabled". If Terminal Services is "disabled" or
"manual", it will not start up when another RDC client attempts to
establish a connection.
I set "Terminal Services" service to "Automatic", and ta-da! With
your suggestions and this service change, I was able to log in to the
PC.
RDC is very responsive when viewing on the Mac G5 (1.8ghz), but only
if you turn off the "extras" like animations, etc.
********************************************* |