Maybe stop server service, unplug the cable from the .122 port, start FMServer, then reconnect the cable.
"In general, my children refused to eat anything that hadn’t danced on TV." ~Erma Bombeck
First - is this causing you an issue or are you just not wanting to allow FMS access on the second IP address ?
If so, then I would use the firewall to restrict access on the second interface.
Second - I wouldn't unplug and start server. You are not going to want to do this every time you start server, so that's a short term solution.
Third - What is your subnet on the two interface cards. Are they both on the same 192.168.1.x / 255.255.255.0 network range ? If so, what is the purpose of the second network card ?
If it's for redundancy purposes - then I would look into binding the two cards so that they appear as one card / one IP address.
I have the feeling it is causing an issue that on the client side it slows down from time to time.
Why to to have more band width, it is not a second card it is one card with to 1 Gb ports.
The subnet is on both the same.
Understand - it's a singe card with two network ports on it.
I suggest that you look at 'Link Aggregation' to make the two network ports appear as one.
This gives you several advantages, including:
1) One IP address on the server
3) Double the bandwidth
You may need to configure the switch to handle this setup properly depending on the switch.
With your current setup - I doubt you are getting the desired effect and possibly making things worse.
I think Kamar's suggestion is one of the correct solutions if supported by your network card.
But also, if the second port is not used for any purpose, to disable it in the interface for your network/network card.
Thank you very much for your input.
thanks for the input.