License server connection woes
March 17, 2009 5:07 AM Subscribe
I am having trouble accessing from my desktop the reprise license manager running on my server. Everything was working fine till it failed suddenly yesterday.
The gory details
I turned off iptables and SElinux on the server.
netstat -apln on the server shows
Running nmap on my desktop and pointing it at the server shows
However, when I run tecplot, I get a network connection error. At this point, I am completely lost on how to proceed. I would appreciate any help at this point. I have access to the server but not to the switches in between.
The gory details
I turned off iptables and SElinux on the server.
netstat -apln on the server shows
tcp 0 0 0.0.0.0:5054 0.0.0.0:* LISTEN 21391/rlm
tcp 0 0 0.0.0.0:1055 0.0.0.0:* LISTEN 2754/lmgrd
tcp 0 0 0.0.0.0:50455 0.0.0.0:* LISTEN 21391/rlm
Running nmap on my desktop and pointing it at the server shows
Discovered open port 27001/tcp on 194...
Discovered open port 536/tcp on 194...
Discovered open port 5054/tcp on 194...
Discovered open port 50455/tcp on 194...
However, when I run tecplot, I get a network connection error. At this point, I am completely lost on how to proceed. I would appreciate any help at this point. I have access to the server but not to the switches in between.
Response by poster: We have eliminated the license server as the source of the problem. We can run tecplot on the server, and it works just fine. The problem starts when we try to access the license manager from any other machine.
I feel that the networking guys messed something up by accident but I cannot figure out what forensic tools I can use at this point.
posted by hariya at 7:23 AM on March 17, 2009
I feel that the networking guys messed something up by accident but I cannot figure out what forensic tools I can use at this point.
posted by hariya at 7:23 AM on March 17, 2009
Might be a spurious typo, but you have "Discovered open port 27001/tcp on 194..." on your nmap output. 194.* network IPs aren't typically used on an internal LAN. Could there be some sort of silly DNS/addressing issue?
posted by chengjih at 7:37 AM on March 17, 2009
posted by chengjih at 7:37 AM on March 17, 2009
Response by poster: The IP address is correct. 194... is assigned to Cyprus which is where I am. The server and the desktop are both in the same subnet.
I guess my question should be "The server shows the port is open and listening, and nmap on my desktop shows the port on the server is open but I cannot access the license manager. What other tests can I run to eliminate different issues?"
For example, how can I check for some sort of silly DNS/addressing issue, as chengjih suggests, and eliminate it for sure.
posted by hariya at 7:50 AM on March 17, 2009
I guess my question should be "The server shows the port is open and listening, and nmap on my desktop shows the port on the server is open but I cannot access the license manager. What other tests can I run to eliminate different issues?"
For example, how can I check for some sort of silly DNS/addressing issue, as chengjih suggests, and eliminate it for sure.
posted by hariya at 7:50 AM on March 17, 2009
Best answer: Make sure you have the same subnet mask, default route & broadcast address (you can use ifconfig -a.) The netmask should look something like 255.255.255.0 and should be the same.
You should be able to do something like 'telnet hostname portnumber' - and you should get something back (cntrl ] exits) (for example if you 'telnet hostname 25' you will get the smtp stuff.) - if you get hanging (no prompt or txt etc) you might have firewall type issue.
If you are on a sun box you can use (from another terminal) 'snoop hostname' and see what the traffic is doing (tcpdump -i "interface" on a linux box is a similar if much worse tool - I have a solaris box around just for snoop!)
But my money is on a subnet mask problem.
posted by lamby at 8:37 AM on March 17, 2009
You should be able to do something like 'telnet hostname portnumber' - and you should get something back (cntrl ] exits) (for example if you 'telnet hostname 25' you will get the smtp stuff.) - if you get hanging (no prompt or txt etc) you might have firewall type issue.
If you are on a sun box you can use (from another terminal) 'snoop hostname' and see what the traffic is doing (tcpdump -i "interface" on a linux box is a similar if much worse tool - I have a solaris box around just for snoop!)
But my money is on a subnet mask problem.
posted by lamby at 8:37 AM on March 17, 2009
Response by poster: Just to close this thread.
I ran tcpdump on my desktop and saw that it was trying to connect to the server at port 5053. I changed the license file to make sure rlm is on 5053 instead of 50455 and the problem was resolved.
Thanks for that idea, lamby.
posted by hariya at 5:14 AM on March 18, 2009
I ran tcpdump on my desktop and saw that it was trying to connect to the server at port 5053. I changed the license file to make sure rlm is on 5053 instead of 50455 and the problem was resolved.
Thanks for that idea, lamby.
posted by hariya at 5:14 AM on March 18, 2009
This thread is closed to new comments.
posted by knave at 7:16 AM on March 17, 2009