Forum Discussion
Cannot access using \\IP but works via \\localhost
Hello,
Can anybody help me with this problem - Cannot access using \\IP but works via \\localhost.
When I try with PortQry.exe use as Destination IP or FQDN server IP or name, I receive back this result :
==
Starting portqry.exe -n ac-cloud3 -e 445 -p TCP ...
Querying target system called:
ac-cloud3
Attempting to resolve name to IP address...
Name resolved to 89.221.223.251
querying...
TCP port 445 (microsoft-ds service): FILTERED
portqry.exe -n ac-cloud3 -e 445 -p TCP exits with return code 0x00000002.
==
But when I use as Destination IP or FQDN localhost - result is OK :
==
Starting portqry.exe -n localhost -e 445 -p TCP ...
Querying target system called:
localhost
Attempting to resolve name to IP address...
Name resolved to 127.0.0.1
querying...
TCP port 445 (microsoft-ds service): LISTENING
portqry.exe -n localhost -e 445 -p TCP exits with return code 0x00000000.
==
Regards
Jaroslav Jasek
- HidMovSteel Contributor
89.221.223.251 is a public IP address; I suspect that a firewall may be blocking port 445 traffic from coming outside in to the device. When you test with localhost, it is just testing the NIC on the device itself so won't be going through any external firewalls (only the Windows Firewall if it is enabled).
Is there an internal IP you can test?
- Jaroslav_JasekCopper Contributor
- HidMovSteel Contributor
- AvirupDasCopper ContributorI am here stuck on the same issue. Any idea?
- AmolShelarCopper ContributorAvirupDas,
To troubleshoot your SMB share access, I'll need the following details:
Source IP: The IP address of the system you are using to access the SMB share.
Destination IP: The IP address of the system hosting the SMB share.
Network Firewall Configuration: Information on any network firewalls configured between the source and destination systems.
Windows Firewall Status: The status of the Windows Firewall on the local system from which you're attempting to access the share (enabled/disabled).