Nope, haven;t tried ethereal, but will get an authorit to do so. This is a Corp WAN environment, not a home LAN. Can’'t touch 5269 from anywhere else except for google. it is setup like that on the f/w. will see if I can get that port completely opened to any connections. Just a really strange thing…
Ok. the network guys have ‘‘opened’’ port 5269, but I cannot telnet to that port on the server. Would the redirect at the FW from the public ip, tothe internal IP have anythign to do with this???
it seems that your network guys didn’'t add the NAT information @“the network guys have ‘‘opened’’ port 5269, but I cannot telnet to that port on the server.”.
This is what we found out. first the network fw was not allowing connections correctly. we got that ironed out, and the other issue that that there is a fifth server at google. It would seem that there is a server on the 72. A network that was attempting to pass the hash back. that is the server that was NOTin the fw rules and thus it was failing.
With that knowledge, we have now fixed the issue, and can now connect to accounts with Google.