Cannot access using \\IP but works via \\localhost

[Jaroslav_Jasek]

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

[#2]

Hi @Jaroslav_Jasek 

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?

[#3]

Hi @HidMov 

This IP is also internal adderess 

Regards

[#4]

Thanks for confirming @Jaroslav_Jasek 

Can you show the result of a tracert using the IP or domain?

[#5]

@HidMov 

c:\PortQryUI>tracert AC-CLOUD3

Tracing route to AC-CLOUD3 [89.221.223.251]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms AC-CLOUD3 [89.221.223.251]

Trace complete.

==

c:\PortQryUI>tracert 89.221.223.251

Tracing route to AC-CLOUD3 [89.221.223.251]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms AC-CLOUD3 [89.221.223.251]

Trace complete.

[#6]

@HidMov 
any info more - this server is not in Domain, only WorkGroup

[#7]

Thanks @Jaroslav_Jasek 

Can see that there isn't any funky routing going on - bit of a loss to explain why it is behaving in the way it is behaving. Just to check - what does this box do? Are the ports open on Windows Firewall?

Sorry I can't be more help, 

Mark

[#8]

@HidMov 

Any update or result on this issue as I'm hitting the same issue with \\<IP>\share does not work

but \\<server>\share works fine ...

[#9]

I am here stuck on the same issue. Any idea?

[#10]

@AvirupDas,

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).