SOLVED: Trying to map a drive to a QBW file on home network

[ell]

That error is a fairly common Win 10 problem/bug. I've had it happen twice now in various Win 10 builds. First was when accessing my NAS. I fixed that one with omiklik's answer from December 12, 2015 here http://answers.microsoft.com/en-us/...d00-6897-4596-9f85-e9f50fec46bf?page=2&auth=1 . Now I'm getting the error when trying to access my Win 7 machine. No luck fixing it yet. As a workaround. create a desktop shortcut to the machine using the IP address. I then pinned the shortcuts to Quick Access to make them easily found in Explorer.

I'm not done looking for a solution... just no more today. ;-)

Somehow I missed this post. Sounds like my issue. Kinda glad I'm not just losing it. I'm going to try the fix tomorrow thanks.

 

[ell]

Somehow I missed this post. Sounds like my issue. Kinda glad I'm not just losing it. I'm going to try the fix tomorrow thanks.

YES! that hack you posted worked:
One workaround is to create a desktop shortcut and insert the NAS IP address, e.g. \\192.168.1.XXX
I hope MSFT fixes this bug soon. Also I shared a single file from the desktop, no other items on the desktop were accessible from the workstation so sharing from there does not share everything on the desktop. Also it works without enabling sharing on the workstation


clicking on this opens the NAS in explorer

 

[Daifne]

YES! that hack you posted worked:
One workaround is to create a desktop shortcut and insert the NAS IP address, e.g. \\192.168.1.XXX
I hope MSFT fixes this bug soon. Also I shared a single file from the desktop, no other items on the desktop were accessible from the workstation so sharing from there does not share everything on the desktop. Also it works without enabling sharing on the workstation

clicking on this opens the NAS in explorer

Great. It's not the best work around, but it's the only one I've found that works consistently. I really wish MS would deal with the rather important bugs like this rather than giving us all these "wonderful" new features that nobody wants.

 

[ell]

Great. It's not the best work around, but it's the only one I've found that works consistently. I really wish MS would deal with the rather important bugs like this rather than giving us all these "wonderful" new features that nobody wants.

One important thing I just found out though, QB requires the shared QBW to be a mapped drive. I put in the IPV4 ip address of the server \\192.169.1.XXX and got the same networking error, put in the exact path \\192.169.1.XXX\users\user\shared file still failed, but it worked when I put the file into its own folder, \\192.169.1.XXX\users\user\shared folder

 

[Markverhyden]

Yes, you do not share the file itself. It's the folder that contains the file.

 

[Cody Ross]

Having installed QB's in many of my different clients networked environments I would like to add a few things from my own experience to assist with this forum members problem and perhaps help anyone else who runs into the same or similar issue with QB.

It is not correct that QB requires you to MAP the drive. Actually, mapping the drive for some reason actually can cause conflicts with in the QB database manager, especially if you have multiple machines in the environment (more than two that are using the qbw file). This is because often people will create a map using drive:x on machine 1, and a mapped drive:Y on machine 2, and so on.

The trick to an almost flawless installation and networking of QB's is to download the QB File Doctor from Intuit and 1st run it on the machine hosting the file, then run the same program on each machine in the network which is attempting to access the file across the network. This program from Intuit, will open all the necessary ports in your firewall to allow the proper sharing of the qbw file and will also typically create the necessary shares on your hard drive. I now make this my normal routine on every network installation and I've had zero issues since incorporating it into my installations.

One other caveat I would like to share: AVG antivirus (and possibly a few others) need to have exceptions added to their programs. (unless this has been corrected since my last installation about six months ago.

Hope this helps someone.

 

[ell]

Having installed QB's in many of my different clients networked environments I would like to add a few things from my own experience to assist with this forum members problem and perhaps help anyone else who runs into the same or similar issue with QB.

It is not correct that QB requires you to MAP the drive. Actually, mapping the drive for some reason actually can cause conflicts with in the QB database manager, especially if you have multiple machines in the environment (more than two that are using the qbw file). This is because often people will create a map using drive:x on machine 1, and a mapped drive:Y on machine 2, and so on.

The trick to an almost flawless installation and networking of QB's is to download the QB File Doctor from Intuit and 1st run it on the machine hosting the file, then run the same program on each machine in the network which is attempting to access the file across the network. This program from Intuit, will open all the necessary ports in your firewall to allow the proper sharing of the qbw file and will also typically create the necessary shares on your hard drive. I now make this my normal routine on every network installation and I've had zero issues since incorporating it into my installations.

One other caveat I would like to share: AVG antivirus (and possibly a few others) need to have exceptions added to their programs. (unless this has been corrected since my last installation about six months ago.

Hope this helps someone.

Hi, I almost ran that but not having any experience with it and the description says it "repairs" the data file and not any mention of networking so I was leary of it, good to know it does work, but have you tried it on Windows 10? I've never had issues with any other operating system.

 

[Cody Ross]

I haven't had need to use it on WIn 10 yet, but all the problems listed I've experienced on XP and up, including WIN7 & Win8. The description for Qb FD says, "If you're reading this article, it's probably because you're having trouble with QuickBooks data file integrity or QuickBooks networking setup." Every setup I've done has had some sort of issue with the networking with QB so, as I mentioned earlier, I've made it as part of my preemptive setup. They keep the program fairly well up to date as well. So if you're having issues with integrity, it can work with that as well... if it's networking, it'll help with that. It's a wizard interface. Use it without fear. Just ALWAYS be smart and backup the file FIRST!!!

 

[Diggs]

I apologize if I'm late to the discussion but thought I would add for future readers.
Win10 peer file sharing I've found is best done through C:\users\public set to share with everyone and no passwords. Shows up all over the network, can be mapped from any other machine like always (as was mentioned above, no Homegroups) and requires no passwords.

 

[ell]

Rats, they called and the mapped share dropped. I logged into machine trying to access it and can't even ping the server, it still has sharing enabled, ideas?

 

[Diggs]

A long shot: Is there a screen saver or monitor sleep involved? If the server is set to require a password when waking it's monitor, I've also seen it not respond to sharing requests at the same time. A bit weird...... Try no sleep on the monitor or check the box for no password required to wake even if the server itself has no password. Like I said, a long shot but I've seen it a few times now.

 

[ell]

A long shot: Is there a screen saver or monitor sleep involved? If the server is set to require a password when waking it's monitor, I've also seen it not respond to sharing requests at the same time. A bit weird...... Try no sleep on the monitor or check the box for no password required to wake even if the server itself has no password. Like I said, a long shot but I've seen it a few times now.

I'll try it, but I logged into both and rebooted, disconnected the share, tried to reconnect it, but the pc is visible on the workstation in network sharing but cannot open it on the lan at all, but i have no trouble remoting in and checking it. Driving me nuts, I duplicated the same steps on my my two win 10 machines no problem, only difference is on theirs one uses a pin to log in and the server uses a local account.

1. on server pc all sharing settings are enabled, no password required (using wifi on both)
2. for the shared folder the security is set to "everyone" its a local account not a msft one.
3. on the workstation she has a pin login, all sharing enabled.
4. server is visible in networking on workstation, but cannot open or ping it from servers ivp4 ip address.
5. Workstation is accessible from server.

I'm stumped.

 

[ell]

OMG!!! I can't believe I missed this!!! She had a guest wifi checked to automatically reconnect along with her main wifi both had the same name so she was toggling between both networks!! Got back on main wifi and got the old ip address back, mapped the drives and reshared everything, but now the QB file wouldn't open on workstation . Ran the QB File Doctor as Cody recommended on the server (just the networking part) and it fixed it!