Nathan,
If you are using a portmapper, then that port should be open in the
firewall. If you are using private ports, all the appropriate cross
bounder addresses must also be opened through the firewall.
Regards,
Chad Whilding
Senior Developer
CSC
3560 Pentagon Blvd., Beavercreek, OH 45431-1706
North American Public Sector | p: +1-937.320-7827 | f: | cwhild...@csc.com
| www.csc.com
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
any order or other contract unless pursuant to explicit written agreement
or government initiative expressly permitting the use of e-mail for such
purpose.
From: Nathan Brandt <nathanrbra...@gmail.com>
To: arslist@ARSLIST.ORG
Date: 04/09/2013 11:24 PM
Subject: Re: Issues in DSO 7.6.04 SP2 Linux->Windows
Sent by: "Action Request System discussion list(ARSList)"
<arslist@ARSLIST.ORG>
**
Thanks guys for all the help. I am still trying to figure it out.
One more question.
When servers are geographically dispersed, how does this work? Typically
only mid tier port would be exposed for outside, if at all.
If servers are behind firewalls, do we have to go with Placeholder Server
which has a public IP?
~ Nathan
On Tue, Apr 9, 2013 at 6:32 PM, Chad M Whilding <cwhild...@csc.com> wrote:
** Nathan,
If there is no conflict between your /etc/hosts and DNS, then double check
the ar.cfg.
There is also an IP-Name parameter that can be used for a server with
multiple names. There are also some DSO specific name parameters.
Double check that none of these are conflicting.
Regards,
Chad Whilding
Senior Developer
CSC
3560 Pentagon Blvd., Beavercreek, OH 45431-1706
North American Public Sector | p: +1-937.320-7827 | f: | cwhild...@csc.com
| www.csc.com
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
any order or other contract unless pursuant to explicit written agreement
or government initiative expressly permitting the use of e-mail for such
purpose.
From: Nathan Brandt <nathanrbra...@gmail.com>
To: arslist@ARSLIST.ORG
Date: 04/09/2013 01:13 AM
Subject: Issues in DSO 7.6.04 SP2 Linux->Windows
Sent by: "Action Request System discussion list(ARSList)" <
arslist@ARSLIST.ORG>
**
We are trying to setup DSO between 2 AR servers.
One is on RHEL 5.3, 7.6.04 SP2 and other is on Win 2k 8, 7.6.04 SP2
We enabled DSO on both the servers. Machines are in same network and
accessible from one another using machine name (same as AR Server name).
After making all configuration changes, we observe following
1. From Developer Studio, if we connect to Windows ARS, we are able to
connect to
Linux Server in one of the distributed mappings. Even here, there is
small glitch, we need to specify IP address of Linux machine. It doesn't
work with AR Server Name of Linux machine.
2. But from Developer Studio, if we connect to Linux ARS, no matter what
we put we are not able to establish connection to Windows ARS server.
When configuring DSO on both, we have used machine names (same as AR
Server Alias Name) (and not FQDN) of the remote AR Server.
Any clues what might be going wrong?
~ Nathan
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
