Question is like this, my company deployed a set of monitoring products, need to open Windows server 445, 135, 139, 3389 port and a remote login account, by the monitoring server from the impassability, before opening I took a test port access, telnet445, 135, 139, 3389 can be, but because of the new user didn't join the remote access policy, so can't log in the monitored server, spent two weeks later, when the service deployment found four machine 77.88.21.6-9 445 port, check out standing rules, what works, firewall is to restart the server, the strategy map is no problem, because can normal Telnet the 135, 139, and still have the same network segment 77.88.21.1-4 win server is can Telnet access, so Internet strategy should be no problem, on a remote server, found a Telnet (Telnet 77.88.21.6 445) in the form of a native port 445 also impassability, but 135, 139, and using Telnet 127.0.0.1 445 form, can be measured, now try a variety of methods can solve this problem, this a few left out to make a few, want to ask you a great god have what good method or advice
Server is deployed on a virtual machine, local netstat - an | findstr searches 445 listening is normal, can also be before via Telnet, the only during the period of operations is that they add the newly created users to have remote access permission of user groups, this should not affect local port strategy, induction didn't take long, I am also not learning network, baidu brother all sorts of methods are tried, individual needs great privileges, the somebody else vendors to open account privileges is not enough, also won't be able to operate, ps (I went to the manufacturer's office on the machine to see, what also didn't see it)
A great god, please grant instruction, make uncertain,

CodePudding user response:

Bring 2 points for reference
1. Turn off the firewall can not see
2. Make sure use netstat - an | findstr searches 445 to check the process is that the remote access server, which is the binding of IP network segment

CodePudding user response:

@ heronism firewall is already closed, netstat - an | findstr searches to see 445 as a result of the
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 77.88.21.6:56445, 4002:77.88.16.15 TIME_WAIT
TCP [: :] : 445 [: :] : 0 LISTENING
On this server is now on the remote 77.88.21.6 Telnet localhost 445 open a command window can Telnet 77.88.21.6 445 stuffed up