Hi All,
Some months ago I bought a Metal-52SHPacn device and just kept it in storage until recently. I connected it and was trying to configure the device as an AP but could not get any client to see it, much less connect to it. After about a week of it being on , when I tried to access the device it is not responding. I have since been trying to get Netinstall to work on my laptop but i keep get an error: bind () failed: An Attempt was made to access a socket in a way forbidden by its access permission. (10013).
I googled at tried several suggestions but all to no avail. I have firewall disabled, only one interface enabled, I tried different Windows ver compatibility, but not seems to work. Suggestions. TIA
Re: Netinstall does seem to work- RBMetalg-52SHPacn Intl
"bind failed" error means that the program doesn't have the necessary rights on your Windows PC to open the raw ports it needs OR that the specific port number is already used by some other program.
Make sure you are running netinstall tool as administrator (right click -> run as admin).
If bind fails even then, some other program on your PC must be already using some of the necessary ports (dhcp-server / tftp-server / mt-netinstall).
In this case please open a command prompt with "run as administrator", run
netstat -nab
and post the result.
(If you have a public IP address directly on the PC you may want to redact it in the results for your privacy).
Ah yeah, one more thing. Do you have some overzealous security software installed, maybe?
Make sure you are running netinstall tool as administrator (right click -> run as admin).
If bind fails even then, some other program on your PC must be already using some of the necessary ports (dhcp-server / tftp-server / mt-netinstall).
In this case please open a command prompt with "run as administrator", run
netstat -nab
and post the result.
(If you have a public IP address directly on the PC you may want to redact it in the results for your privacy).
Ah yeah, one more thing. Do you have some overzealous security software installed, maybe?
Re: Netinstall does seem to work- RBMetalg-52SHPacn Intl
Ran the "netstat -nab" Command but it doesn't give me the option to copy the results. What port number does netinstall use? Had ran netinstall as admin.
Re: Netinstall does seem to work- RBMetalg-52SHPacn Intl
To copy the data from a Windows console, right click the title bar for a menu.
Select Edit -> Select All.
The whole window will get reverse colors.
Press Enter.
Colors will turn normal and the text will be in clipboard.
Paste to notepad and review.
What to look for:
When you run "netstat -nab" you will see plenty of results following a similar format as below.
Focus on the port numbers in the Local Address column (135 and 445 in the snip above).
In order for netinstall to work, there must be no existing entry for UDP port 67 (DHCP/BOOTP server), 69 (TFTP server) or 5000 (MT Netinstall server), so netinstall can take these ports for its own use.
If you'll find one - and most probably you will - one or two lines right below the port entry should announce what program is using it.
The line in brackets ([svchost.exe] above) is the actual program executable, if there's line without brackets above that's the id/name of a relevant Windows Service.
"Can not obtain ownership information" usually means the port is opened by a kernel-side component (445 in the example is the SMB / Windows Filesharing driver).
Select Edit -> Select All.
The whole window will get reverse colors.
Press Enter.
Colors will turn normal and the text will be in clipboard.
Paste to notepad and review.
What to look for:
When you run "netstat -nab" you will see plenty of results following a similar format as below.
Code: Select all
C:\windows\system32>netstat -nab
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
RpcSs
[svchost.exe]
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
Can not obtain ownership information
(...)In order for netinstall to work, there must be no existing entry for UDP port 67 (DHCP/BOOTP server), 69 (TFTP server) or 5000 (MT Netinstall server), so netinstall can take these ports for its own use.
If you'll find one - and most probably you will - one or two lines right below the port entry should announce what program is using it.
The line in brackets ([svchost.exe] above) is the actual program executable, if there's line without brackets above that's the id/name of a relevant Windows Service.
"Can not obtain ownership information" usually means the port is opened by a kernel-side component (445 in the example is the SMB / Windows Filesharing driver).
Re: Netinstall does seem to work- RBMetalg-52SHPacn Intl
Thanks for your input. I tried the Netinstall from a third PC and was able to re-install ROS. I can now connect to the device to configure it. thanks again.