J
Jeff Ledbetter
Guest
Hi. I can’t remember the details and I may be thinking of another issue, but I remember having to switch my host name from ‘localhost’ to the actual host name to work around an appserver connection issue. I know.. not very helpful. Jeff Ledbetter www.roundtable-software.com email: jeff.ledbetter@roundtable-software.com skype: jeff.ledbetter From: tbergman [mailto:bounce-tbergman@community.progress.com] Sent: Sunday, March 1, 2015 10:52 AM To: TU.OE.General@community.progress.com Subject: [Technical Users - OE General] Server 2012 R2 - Appserver connections using Nameserver not working Server 2012 R2 - Appserver connections using Nameserver not working Thread created by tbergman Progress 11.3.2 64 Bit Last night we upgraded a development server from Server 2008 R2 to Server 2012 R2. When done, databases started fine, appservers started fine, everything looked OK except we couldn't connect to any of the AppServers. After a little testing, and a look at our only other Server 2012 server, we realized that we used the -DirectConnect for all our AppServer startups on the other server. This server used the NameServer. The NameServer was working fine in Server 2008, the log files show that it starts normally and services register with it properly, we just can't use it to connect to anything. Now, I don't really care that much since my current preference is to use -DirectConnect anyway, but I'm wondering is anyone knows the reason for this? Same server, different OS. The connections fail when on the local machine so it's not firewall related. Thanks, Tom Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...