Windows 7 file sharing problems

[tek9]

I'm having some trouble with a client's file sharing setup.
3 PCs, 2 of them new Dell Optiplex running Win7 Pro, one older HP all in one running win7 Home Prem.
They have an Access database shared from the Main PC which is one of the Dell systems. For some reason the Access database programmer set it up in such a way that the only way for it to work is if they shared the entire Users subfolder to the other machines.
The Dell systems came with Mcafee preinstalled for a year, so I left it on there (Otherwise, would have installed Kaspersky or ESET), while the HP has MSSE.
Every few days they would call me with issues accessing the network share where the Access database resides.
All usernames and passwords for the 3 machines are identical so I shouldn't have any issues with asking for a username and password when trying to access the share. I set the Network to a Work Network and allowed file sharing etc, checked permissions and everything is set correctly.
It worked for a while, then after a few days when they try to access the shared folder it asks for the username and password. Verified they're using the same username as on the Main PC.
I disabled the mcafee firewall and that helped for a few days. Now the same problem occurs. Firewall still off.
I turned off password protected sharing in the Advanced Sharing Settings, rebooted, no change. Changed 128 bit file sharing to the lower setting, no change. Gave Everyone full control in the advanced permissions area, no change.
I uninstalled Mcafee from both machines (installed MSSE temporarily) and now the second Dell system can access the share, but the old HP AIO still asks for a username and password.
The only difference between the machines is that the HP is running Win7 Home Premium while the others have Professional, but this should not really make a difference.
The only thing I can still think to try is to change the Network to Home and set up a Homegroup, but I feel this is a cop-out.
Before I go over there tomorrow to sort this out, can anybody throw out some ideas to try to get this to work correctly?
Thanks in advance.

 

[CLC]

Just wondering can you change the location of the database files, or is this impossible? If Not, maybe you can creat a symbolic link and mount it as a network drive, just pulling at strings here.

 

[tek9]

Can't change the database location. There are many different databases being referenced in the front end and you need the programmer's password to make those changes. He won't give them to me.
I didn't try the symbolic link thing. Maybe tomorrow, but I doubt that'll do any good. I just don't understand why it'll work one day and not the next, and what's the issue to begin with. I've done this many times and never had a problem.

 

[YeOldeStonecat]

The only difference between the machines is that the HP is running Win7 Home Premium while the others have Professional, but this should not really make a difference..

Experience has shown me (even back in the XP days)...mixing Windows Homeless editions with Pro versions will give you weird random quirks like this. You can wrestle with it for hours and hours and get it working...and then some time down the road it will flip out...and you'll come back and spend hours and hours wrestling with it.

Or upgrade the Homeless edition to Pro for 99 bucks (roughly the same cost as an hour of your time?) ......and then set it up and be done knowing it will all work. End result is the network is all the same version of Windows (as it should be)...it works, and ultimately a lower cost to your client (unless you're volunteering all of this troubleshooting time).

Should also neutralize that Access data folder by pulling it out of the users profile and putting it in a shared data folder off the C drive (Like C:\Data\AccessShare or C:\AccessData). Inside the user account profile you have that whole separate security thing to deal with.

 

[tek9]

I've already told them about the Access/Sharing Users folder issue but there's nothing to do now unless the programmer agrees and changes his setup.
Now, regarding the main issue, I went over there yesterday, and after rebooting the machine it connected right away. They tell me that usually after waiting about an hour or so and rebooting it connects fine.
Now they called me that the second Dell system is not connecting to the share, but the old HP is. It seems they take turns who connects. When I check the Network in Computer>Network on the second Dell system, it shows all three computers, but when I click on the Main system to show its shares, it shows the shared folders from the HP machine and not the Main Dell machine?!
The same thing happens in reverse when the HP doesn't connect. The Network shares in the Network window show the wrong shares. It'll show the shares of the second Dell system when I click on the Main Dell system.
I can ping all system by IP address no problem.
When I checked the Network and Sharing Center, and clicked to bring up the full map, it shows the second Dell and HP connecting to a switch which goes to a router and then the Internet, which is how it should be. But the Main Dell PC can't be placed on the map. They should all be connected to the Cablevision router. Why isn't it showing?
(I'm a bit wary of telling them to upgrade the HP to Pro because I just finished convincing them to buy the 2 new Dell Pro computers. If there's any way this would work as is, I'd rather do that.)

 

[YeOldeStonecat]

When you have "peer to peer" networks (workgroups)...a lot of varying success.
First...there is no "master browser"...like there is when you have a proper server doing active directory..thus it's the DNS for the network...and it's the master browser.

There's a ton I can write about "master browser" when it comes to workgroups..but basically just know it's the source of "sometimes it works...sometimes it won't".

The next monkey wrench to throw in the system is the router. Some routers run a local DNS service thus have a local host name table built.others just do DNS forwarding and can't help much. Others just pass on external DNS servers and make it really difficult.

But here's a couple of things you can do to help make a local workgroup a little more reliable.
*Any workstation that will be used as a quasi server...put it on a static IP address.
*Go into TCP properties...Advanced...WINS tab...and "enable netbios over IP".
*sometimes you can turn to the "poor mans WINS" approach of using the lmhosts file.

 

[tek9]

Thanks, stonecat.
I set all the computers to static ips and enabled netbios over tcp/ip. They're working for now. Let's see how long it lasts.

 

[JustInspired]

I've had a similar issue where changing the router fixed the problem. In case what you've done doesn't work...