Unable to access shared folder in Win 7 homegroup via IP address

[user0x12]

I have 3 Win-7 64 bit machines in a homegroup. MAC addressing enabled on the router. Machine A, B and C.

All are in a homegroup. I want to share a folder on machine B to the rest of the group so I share with homegroup (read/write allowed). I jump on machine A and C to test, and am able to click network and open machine B and access and modify the shared folder via explorer. I try the same via windows key run explorer, by typing in \machineb\share and I am able to access and modify the folder. However, when I type the IP address (192.168.0.13) it will no resolve and I get a "Windows cannot access \path\share."

-I run it in safe mode with no results. Here are my troubleshooting efforts:

-removed all machines from homegroup and and created a new one for all to join -tested this process on machine C. Machine A and B are able to access the share on C via hostname and IP address. -ran ipconfig /flush dns on all machines. Then ran net stop "dns client" and net start "dns client" -restarted router -ran problematic machine (B) in safe mode (no anti-virus). -ran the other machines in safe mode. -on machine A, ran net use to map P: as the machine B share (machineb\share) by mapping to its host name. Successful drive mapping and ability to access. When I try the same to the IP address it's fails again. -disabled firewall on both ends

Why can't I access this folder via IP address? I'm pretty sure I'm putting in the right address as shown by ipconfig.

Any ideas? Would MAC address filtering have anything to do with it? I may try to remove/add the problematic machine at router level. Thanks.

**Basically, I can access file shares in homegroup via host name but NOT IP address. Why is this?**

 

[user0x12]

111 views and not one bit of help. Any ideas at least?

 

[Tookeri]

You didn't give any example on how you tried the IP address, so sorry if you already tried this:
\\192.168.0.13\sharename

Usually the problem is the other way around, that people can access through IP but not by name, so I think this is very unusual.

If MAC Address filtering was the problem than it would result in the machine not being able to connect to the router at all.

 

[user0x12]

You didn't give any example on how you tried the IP address, so sorry if you already tried this:
\\192.168.0.13\sharename

Usually the problem is the other way around, that people can access through IP but not by name, so I think this is very unusual.

If MAC Address filtering was the problem than it would result in the machine not being able to connect to the router at all.

Thanks for the response, Tookeri.

I tried what you suggested to no effect. It looks like I can't connect to any share via IP on either machine (A->B->A) but I can through hostname just fine. I wonder if it's a homegroup failing or if something in between is corrupted, like a HOSTS file or something of that nature.

Perhaps I have to reconcile NetBIOS hostname to IP manually via HOSTS config file?

This is not really hampering my work or anything it's just a puzzle that has intrigued me. Any ideas?

*note When I ping other machines in the homegroup LAN by machine name it does not display IP address after machine name in PING output, as it would in say, a google.com PING. It just displays MAC address.

 

[Tookeri]

Same result from machine C?

Could you paste the ping output?

Also try a ping and the parameter -4. Example: ping machineB -4
This will force using IPv4, to see if perhaps the problem is related to the use of IPv6 adresses.

 

[user0x12]

Same result from machine C?

Could you paste the ping output?

Also try a ping and the parameter -4. Example: ping machineB -4
This will force using IPv4, to see if perhaps the problem is related to the use of IPv6 adresses.

Yes, same result with computer C.

Okay, I'm able to display IP addresses from ping only by using -4.

I'm guessing this is some DNS issue but I don't know at which level. File and sharing settings in all Windows firewalls are enabled. Antivirus is disabled for my tests.

 

[HammerHead]

Possibility

I have a setup similar to what you describe. I have a file sync program to sync my shares. I ran into a problem with one particular folder. I found the problem by focusing on the folder and right clicking. Select properties and then Security. There was some off the wall entries in "Group or User Names". I deleted those entries and then made sure I had admistrators, my account, system, and I added "Everyone" all with full control. Also while you are at this point I would click on the sharing tab and check out the entries there. Click advanced and check the box on that window.

This may not help but it is worth checking.

I didn't enter the accts that I deleted they showed up on their own.

 

[Tookeri]

I'm able to display IP addresses from ping only by using -4

Ok, that explains it as it seems the IPv6 addresses are used by default. I'm no expert in IPv6 so I think you should leave things as they are until someone else maybe can give you some better advice.

You could try using the IPv6 address instead of the IPv4 address to access a network share, maybe that works. With ipconfig you should be able to see both the IPv4 and the IPv6 address.

 

[user0x12]

Hammerhead, I checked the securities tab and went to advanced and cleared out some erroneous user entries to no effect. All file users (admin, everyone) are set to share all.

Tookeri, I found the ipv6 address but failed to connect via \\ in start because of an incorrect address. The address is too long and tedious, is it worth exploring the ipv6 notion?

 

[jbert1949]

Guys, I have been working on my network 3 days with this problem. No one mentioned having to sign in with user name and password. I am trying to connect to an old PC as a backup for our other 2. Will repost if I find anything out. I did reboot router at one point but many of the same errors, then Irebooted my switch and it cleared up some things. I have tried homegroups up and running and then homegroups off. Funny thing is, I tried Acronice 2014 and when I tried to specify the destination and clicked all paths in the directory trees, it still asked for credentials. I think it should though as passwords is ticked in advanced sharing.

Would not mind a small 2Terabyte cloud, and I think that might take care of all the paths, but credentials. Plan on call Western digital today for confirmation.

 

[Tookeri]

Tookeri, I found the ipv6 address but failed to connect via \\ in start because of an incorrect address. The address is too long and tedious, is it worth exploring the ipv6 notion?

I don't know enough about IPv6 so I'm not sure if that's supposed to work or not.

By default, Windows prefers IPv6 over IPv4. It's possible to change that but I can't recommend it: http://support.microsoft.com/kb/2533454

As I said before: "I'm no expert in IPv6 so I think you should leave things as they are until someone else maybe can give you some better advice."
As long as it works with computer names instead of IP, you're fine.