I have a user in our organization who attempts to connect to Windchill via the web interface. The connection is established, he's able to put in his username and password, but as soon as he does the next page it tries to load spits out a DNS failure, even though it was able to create a connection to authenticate his password.
Any idea what's going on? I'm somewhat unfamiliar with how the Windchill server processes requests but in terms of host-client connectivity it should be pretty simple. If he uses RDP and accesses the resource from the server itself, the page will load properly after he puts in his password. It's just when he does it locally that he gets a failure. I checked the DNS mapping and it's correctly pointed to the IP of the server.
I could test it myself but I don't have a Windchill account within the server so I can't get past the password entry prompt.
