Quark on port 1024 no longer functions after update...
Morning all. Well, stupid me did a Microsoft critical update to my Quark License Server yesterday which sits on top of a Windows 2003 Server Enterprise box. The client systems had now updates done to them.
Morning all.
Well, stupid me did a Microsoft critical update to my Quark License Server yesterday which sits on top of a Windows 2003 Server Enterprise box. The client systems had now updates done to them.
After I did the updates Quark Licensing no longer worked off of port 1024. I'm assuming Microsoft has decided to now use that port for their own purposes. I called into Quark tech to get their read and I was right as we changed port setup for server and one client and that worked. But I have over a couple of hundred of client systems to change along with firewall edits.
Can anyone tell me what Microsoft has done with port 1024 and if I really need the service that Microsoft has issued for that port. If I don't need it then how do I kill it from using that port.
Thanks in advance to all.
Well, stupid me did a Microsoft critical update to my Quark License Server yesterday which sits on top of a Windows 2003 Server Enterprise box. The client systems had now updates done to them.
After I did the updates Quark Licensing no longer worked off of port 1024. I'm assuming Microsoft has decided to now use that port for their own purposes. I called into Quark tech to get their read and I was right as we changed port setup for server and one client and that worked. But I have over a couple of hundred of client systems to change along with firewall edits.
Can anyone tell me what Microsoft has done with port 1024 and if I really need the service that Microsoft has issued for that port. If I don't need it then how do I kill it from using that port.
Thanks in advance to all.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
