Location one has a server running winnt terminalk server connecting to the internet via DSL with a static IP and NAT addresses on the inside to allow all his thin clients to talk to each other as well as pop their terminal sessions form the server.No problem here.
Location 2: has three terminals, these are connecting to the internet via ISDN (all tha they can get at this location). The terminals get their sessions across 3389 and the login fine, BUT here come the silly part when they submit a print job, it goes out port 6464 tcp and makes its way to the server at location one (like it is supposed to) and then it is spooled at the server, and pushed back the exact opposite path (I told you it was stupid!!)
BUT the print job never comes back . . .
Cisco has debugged the ISDN router at location two, everything is rock solid there, the DSL router has been checked and rechecked, no problem.
The Server is showing that when the spooled print job tries to head back to location two, it seems to grab whatever random port is there, the debug shows at one time it tried to go across 1059 the next time it was 1062 etc. etc.
We were instructed that the server would push the print job back across 6464 but the thin client software looks like the virtual port (on the server) is unable to “map” its capabilities of being virtual LP_40 to 6464 therefore the print job just goes off to LA LA land.
I have had three cisco ccie look at this as well as the Cisco certified DSL guy on bothsides. Also I checked with the ISP provider and they have ALL ports open by default, as does ISDN provisioner, so it is not a blocked port.
To further illustrate, I can sit at home or work and create a tcp/ip printerer and use their IP address andit will spool to the server and pop out at location 2, now that tells me that TCP services for printing are working.
