Server Fault Asked by cryogenics on February 2, 2021
I have run into a weird issue that i just cant seem to figure out. One of our servers is a file server and is accessible by servername or by X.X.X.X from every remote location aside from the one in question. I am able to ping the file server, and confirmed port 139 is open by telnet X.X.X.X 139 as well as RDP on port 3389 but receive the below error message when I try to use port 445.
The error message i am receiving : Could not open connection to the host, on port 445: connect failed.
Netstat shows that the server is listening on port 445 for all other subnets. I have also created an inbound windows firewall rule to allow all connections over port 445. I was unable to find any ACLs that may be blocking on the edge as well. Interestingly enough, something has to be blocking this as if the user connects to a client vpn, they are able to connect to the share. Does anyone have any suggestions to further isolate where the issue is?
I would start by disabling the Windows firewall (temporarily) altogether. Also, you can do a packet capture on the server to verify that the attempts to tcp/445 are getting there at all... something like windump -ni1 port 445 and host 192.168.1.10 assuming that 192.168.1.10 is the client machine and interface 1 is the server NIC in question (run windump -D to get a list of NICs on the server). You can get WinPcap and WinDump from Riverbed.
Answered by theglossy1 on February 2, 2021
Get help from others!
Recent Questions
Recent Answers
© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP