> From: Bill Haskett > ...In the Server profile > service, > type in "udcs:31439". Seems to work fine.
As Bill's mv.NET vendor and support provider, and as a geek who had some fun poking at UO.NET for this one, I'll clarify and summarize what seems to be good info for any UO.NET or mv.NET site: Bill is connecting from mv.NET to Unidata with UO.NET. He has two machines behind a firewall, both listening on the same socket. If he connects from outside the firewall to 31438, the default port, there's no way to tell which Unidata server should get the connection. So for one of the systems he's connecting in on 31439 and letting firewall port mapping re-route that to 31438 on the intended target. To get mv.NET to connect to servers, for Telnet there is a port#, and for a UO.NET connection there is the uvcs or udcs service name. To use an alternate port, use udcs:port, or uvcs:port. If that were not possible for some reason, for example if someone has a UO.NET client that's hardcoded to the default, then I believe the same task could be accomplished by adding a port-tunnelling tier on the client side, so that outbound 31438 can actually go out the door as 31439, and then get re-converted on the server side. What we've learned here (is there confirmation?) is that Universe allows for an alternate uvcs port, where it seems Unidata does not. Another point: With UniObjects the OpenSession method has a few overloads, with and without the port# param. If you're using mv.NET (should be same with U2.NET) then it does use the correct overload depending on what you put into the profile. HTH Tony Gravagno Nebula Research and Development TG@ remove.pleaseNebula-RnD.com Nebula R&D sells mv.NET worldwide and provides related development services remove.pleaseNebula-RnD.com/blog Visit PickWiki.com! Contribute! http://Twitter.com/TonyGravagno _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
