Recent content by JimPletcher

This seems to be my problem. With domain policy controllinf the Windows firewall, how do I allow remote desktop? The only settings I can find are for IP addresses & ranges.

Windows 2003 Small Business Server with six PCs in the domain. Until recently one user had been able to connect through the hardware firewall from home to her office desktop PC. Suddenly she can't! I installed a (temporary) non-domain PC this morning, and Remote Desktop works like a champ from...

Two Firewalls (ZyWALL 10ii and 2) moved from one client to another. Both had successfully passed Remote Desktop (port 3389) at their previous locations. Reconfigured for the new locations with WAN to LAN firewall rule to pass port 3389 to from Any to Any and SUA NAT to direct port 3389 to...

Ouch! No I didn't force an update (until just now). Thanks for reminding me. Apparently, everything is still OK though.

Removed the added subnet and users can still map to the remote XP. It appears as though my dorking through the Group Policy settings did something I'm not aware of - even though the only change I (conciously) made is stated above.

As mentioned earlier: Ping is OK. Can't map by IP address. Error message states "The network path . . . . could not be found." UPDATE: Mucking about with Group Policy settings (added another subnet to firewall File Sharing exceptions), and now users can map the drives again. I just removed the...

Never could ping across the VPN by hostname (sorry if I didn't nmake that clear). Have tried "using different user name" - no change. It acts like a firewall thing, but I can't find anything. Users on the same subnet CAN map to this PC.

As far as I know, the firewall policy has not changed - although this would be a logical suspect. The domain controls the local firewall, and the policy is set to allow "local subnet" and 10.10.20.0/24 (the other subnet). There have been no MANUAL changes made to any of the systems. I don't...

Thanks for the response. Ping is OK. Cant map by name or IP address. Error message states "The network path . . . . could not be found."

I originally posted this on the VPN forum, but it appears to be a Microsoft specific situation. Two locations connected via VPN routers. Had been able to map drives in both directions. As of last week we can only map drives in one direction. Now unable to map to remote XP Pro machine. No...

The VPN is established via VPN router/firewalls which have not changed in any way. I even swapped out both as a test - no change. This looks more and more like a Microsoft condition.

Only one (local) PC is mapped to this XP.

The VPN works fine. EXCEPT that we can not map to the remote XP shares.

Can't map by either IP or name. Never have been able to browse over the VPN. I should have mentioned that the mapped drives aren't on the server, but on a remote Windows XP machine. Mapping from the XP to the server is fine. Users on the same subnet can map to the shares. Last week userd from...

Two locations connected via VPN routers. Had been able to map drives in both directions. As of last week we can only map drives in one direction Anyone have any ideas?