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
Thanks Roy,
This may have identified the problem. The IP address listed is not the IP address we conventionally associate with this server.
The IP address listed is shown by IPCONFIG as the address belonging to the "Ethernet Adapter TSM" and is the 7.7.*.* range. The address we would normally use is in the10.200.*.* range and is associated with "Ethernet Adapter Ethernet0".
While I'm satisfied running with -DirectConnect, how would I change the IP address for the NameServer so the AppServers would show with the correct IP address?
Thanks,
Tom
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
Flag this post as spam/abuse.
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
Flag this post as spam/abuse.
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
Flag this post as spam/abuse.
Flag this post as spam/abuse.
Notice: All email and instant messages (including attachments) sent to
or from Franklin Templeton Investments (FTI) personnel may be retained,
monitored and/or reviewed by FTI and its agents, or authorized
law enforcement personnel, without further notice or consent.
.
The server was upgrades to Server 2012 in-place. It was Server 2008. It has the same file systems, Progress installation, properties files, users etc. The only change was the OS version.
Our connection parameters did point to the nameserver on port 5163. The appserver ports should have been assigned by the nameserver. When we switched to DirectConnect in order to get things working, we did change to the AppServer ports. DirectConnect works fine. It's still a mystery why the NameServer wouldn't work.
Hi Tom,
lets go back to basics:
1) does the NameServer start?
2) what does the nsman -name <nameServer> -query say?
3) if nsman -query works, are the AppServers shown as connected?
4) if nsman -query works, are the IP addresses for the AppServers correct?
All that being said, the big difference between DirectConnect and NameServer is the use of UDP instead of TCP. Maybe Windows 2012 R2 disables UDP by default? Maybe there is UDP bug? I did find an article where remote desktop using UDP was a very unstable.
Let me know what you find, Roy
Thanks Roy,
This may have identified the problem. The IP address listed is not the IP address we conventionally associate with this server.
The IP address listed is shown by IPCONFIG as the address belonging to the "Ethernet Adapter TSM" and is the 7.7.*.* range. The address we would normally use is in the10.200.*.* range and is associated with "Ethernet Adapter Ethernet0".
While I'm satisfied running with -DirectConnect, how would I change the IP address for the NameServer so the AppServers would show with the correct IP address?
Thanks,
Tom