When users log into our Terminal Server via RDP / VPN, there Terminal Server login script maps a drive (X:) to a local C: share.
The login script mapping syntax is as follows:
'net use x: \\%clientname%\TSImages'.
TSIMages is the Share Point on the users local C:\ drive. We've installed new Windows XP Security Patches & now the share will not map when the users log into their Termincal Server Session. Turning OFF the Windows Firewall on the users workstaion allows the share to map in the Terminal Server Session. What would be blocking the drive mapping in the Firewall?