Remy Blaettler wrote:
There are no switches in the network and it's all in the same ip address range. The only thing we got are 2 simple hubs.
In fact, all these hubs are unmanaged switches today
We have VM Ware installed on that server, will disable that and check again.
I had a lot of timing related networking problems with VMWare servers.
E.g. the opening of MS Jet databases was several times slower than on a normal file server, e.g. 5 minutes instead of few seconds.
It seems FlexLM, as a security related application, is very sensible to this kind of timing problems, as normally they may represent an intent of reverse engineering or sniffing, just like in the promiscuous mode, the VM virtual switch works in a similar manner.
What I discovered, is that the Client is making TCP IP connections to port 27000 on different IP's in our network, but mainly on port 1030 to the Flex License Server.
The 1030 port may be used by many programs according to the "who comes first" principle.
The most important it the 27000 port where the server is listening.
Why is the client trying to contact other IP's on port 27000?
Probably it's unable to find the license server (or get a valid response from it) and it starts to broadcast.
And yes, the license server runs on 27000 and I told the client to connect to 27000:192.168.0.6.
Attention, the default address format for FlexLM is email@example.com.
So there should be no issue with the name resolving.
At least, one thing is sure...
[Edited at 2010-12-10 11:17 GMT]