Hello. I am replacing some WinTerm thin clients with Windows XP Pro workstations at a branch office using leased line WAN. The WinTerms used an ICA client so I installed the current version on the XP systems. The servers at the main office are Windows NT 4.0 and I want to establish sessions on a Windows NT Terminal Server running MetaFrame 1.8. I have set all the networking parameters to match the existing WinTerms. But I can not connect--can not find the server. I admit I do not understand how the WinTerms connect. You turn them on and a Windows CE system initiates a session. So I don't see the local side of any IP stuff until the system has already aquired a login over the WAN. The XP systems have static IPs just like the WinTerms; same IP network, subnet, and gateway. After the XPs boot, I can see the local network but can not ping or contact the server side. The WAN routers were installed without the owner aquiring the password so the routing setup is a blackbox to me right now. Is there any network parameter I might be missing for this setup? The basic settings are the exact same for both WinTerm and XP systems. The XPs were setup as domain members at the main office before I took them to the branch. Could that be masking WAN communication with the server? Is there some difference in how these systems authenticate that could cause this? Since I can not reach the other side with pings, is this completely a networking problem rather than OS/Client? There isn't any problems with the physical lines as the main office can ping the branch office print servers and the WinTerms connect fine. Assuming I can find a way to view the routing tables, what ports do I need for connectivity? If this is a beginner question, I apologize. I would RTFM if I could find a FM. Getting harder and harder to find info on NT. I really think that if I could ping the other side, I could connect--but if it is a router problem, how do the WinTerms get thru?
