Unsolved
This post is more than 5 years old
294 Posts
0
5654
April 2nd, 2012 06:00
Connection port assignment
One of my colleagues is currently looking at this issue with EMC but I was wondering if anyone had seen anything similar. Windows clients were seeing errors "61320:winworkr: cannot bind socket to connection port in configured port range on system clientname - the requested range is not valid in context"
Problem was resolved by:
Amending server service port range from 7937-9936 50000 51000 to 7937-9936
Amending client connection port range from 0-0 to 10001-30000
(Also making some host server amendments to remove missing reverse lookups)
Restarting Networker server and clients (the Networker had been running slowly and this problem was resolved on restart)
I would interpret the error message as saying there were problems assigning a ports to backup data but it would follow that 0-0 implies a greater port range than 10001-30000
Has anyone seen a similar problem or have any idea why this may have occurred? There will be firewalls involved in this environment.
Bebo2k
544 Posts
0
April 2nd, 2012 20:00
Hi David,
I saw this error message before with some VSS savesets like VSS USER DATA , VSS SYSTEM BOOT , etc.... and it has been fixed by re-register the VSS dll files and then reboot the machine. then problem has been fixed and did not occur again, That what i can remember about that issue.
Hope this helps you.
Thanks,
Ahmed Bahaa
DavidHampson-rY
294 Posts
0
April 3rd, 2012 02:00
Thanks Ahmed, the reboot of the client had resolved the issue for us, but I am curious why the use of 0-0 for connection ports was not working correctly...
johannesgao
1 Message
0
April 11th, 2014 03:00
Hi, I met this issue and did not do any change. just restart this client is fine. I do not know why?
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
April 11th, 2014 04:00
After reboot it will be hard to know why as initial condition leading to problem might be gone. For example, older versions of Altiris client may lock port and not release it. This eventually leads to all ports used and suddenly other programs (including NetWorker) are running out of necessary port range for their own operations.