Question Locked

Citrix PS on W2K Server running TS, problem mapping drives

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Win 2000 Server SP4, Terminal Services
Citrix Server Presentation Server 4.0

Client for MS networks
Client for Netware 4.91 SP3
IP preferred protocol
NWLink IPX/SPX/NetBIOS compatible
TCP/IP, static IP
Enable NetBIOS over TCP/IP
File and Print sharing enabled

There's a firewall that sits between this Citrix server and the target/destination server. The firewall is configured to allow 137-139 from my network to the target server. ICMP is allowed from any source to the target server.

Not suprisingly, I can ping the target from my Citrix server. And on the target we can see the pings coming and going. However...

I log on to our Citrix server with admin rights and try to map a shared drive that resides on the target server. The operation times out with a "Network Name cannot be found" error.

On the firewall we can see (in chron order) target port 524 denied, then 137 goes thru, then 139 goes thru, then 445 denied. However, on the target server itself we don't see *any* packets coming from the Citrix server.

Any idea why we're not successful? What is port 524 used for/by? Netware?

Eventually I want regular users who log on to the Citrix server to be able to map this drive.

Any help will be appreciated... ab

3 replies

by jcalexandres

Port 524 isdefinitely used by NDS, so if you need to see the Novell directory services you need to allow TCP and UDP, you also will need to open 445 since it is a port Microsoft uses for file sharing, so this is the reason you can't see the shares.

Good luck!

by abuto

Thanks for the response... I should've mentioned that other non-Citrix, non-W2K servers are okay. They're also running Novell clients (I don't know what version). We can see port 445 denied, but no 524 at all, yet they have no problem connecting to the share (137 and 139 are allowed).

I'll request 524 TCP and UDP be allowed; it sounds like that's the problem. Enterprise-wide policy is to block port 445, so I won't be able to unblock that.

Is there a reason that a Windows 2000 Server behaves differently than a regular Win XP Pro workstation when trying to connect to a shared folder on a Windows Server 2003? (It won't matter for the problem at hand, but just curious)... ab

This discussion is closed to new replies.