Looks like it is the client. Not the server setting -- Errrr. That makes it work. And time after the env setting on the desktop. Still testing
Sent from my iPhone On Aug 11, 2010, at 6:32 PM, patrick zandi <[email protected]> wrote: > put in the startup script ./arsystem > > > ARTCPPORT = 44444 > export ARTCPPORT > > -- Works Great.. > Thanks for all the help.. LOL.... > > On Wed, Aug 11, 2010 at 5:47 PM, patrick zandi <[email protected]> wrote: > what about putting in the following on the server.. in the ENV settings > set ARCTCPPORT = 44444 > will that force the clients connecting to work correctly.. > > > > On Wed, Aug 11, 2010 at 4:26 PM, patrick zandi <[email protected]> wrote: > Oh, and if you happen to have two usertools up and are logged into bother > servers at the same time.. It works. > just to throw a little interesting fact in.. > --- > Can I put in a Setting into the SERVER that will say use default port XXXX > when the stinkin client wants to work.. > > On Wed, Aug 11, 2010 at 4:09 PM, patrick zandi <[email protected]> wrote: > (Purplexing Problem): have an AL on an SRM form that is working fine. however > trying to isolate the issue of why it will not work on desktops. > I suspect networking /NAT PAT or something similar.. Want to make sure I > thought of everything to debug. > > #1 desktop is not run or managed by same shop as the Remedy servers or > Clients. > #2 Activelink fires and opens on ANOTHER remedy server a form and gets data. > #3 /etc/hosts has all the routes possible to both servers > #4 we have debugged client and it shows ETHER when it tries to get to the > second remedy server. > #5 we Sniffed the packet and it makes a Single UDP RPC 111 call to the second > server (Huh?) why not TCP I have no idea.. > #6 Server is running on a SPECIFIC port only. > #7 Desktop client runs the job, RPC timeout after fires. > #8 Mid-tier Works fine. > #9 We do not controll the desktop or the GPO or the network behind the > desktop. > > So I have debugged the client -- getting ether, I have debugged the desktop > / I see a single packet goes out, and in about 12 seconds a second.. and then > timeout. > I suspect a firewall, or a NAT/PAT issue because it does not have our short > name DNS... it is on another network. > > Anything Else you all can think of to debug exactly the problem is.. we are > planning on contacting the network-less shop, but it is a royal pain... > Just checking... > Thanks. > > -- > Patrick Zandi > > > > -- > Patrick Zandi > > > > -- > Patrick Zandi > > > > -- > Patrick Zandi _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
