Help !!

Quickbooks needs to run from a computer on the local network that has a folder shared..and that has the Quickbooks Database Server manager installed to serve up the file.

Well..let me back up a bit....you can have your Quickbooks company data hosted in Intuits cloud...get to it via browser. And there are other more complicated answers like a terminal server.

The reason to have a server? There are many. I wouldn't want to remove this small business server, or recommend removing it, without seeing LOTS more of the existing network.
Other file shares
My Documents redirect
Company Web (you saw that...it's the intRA web site....Sharepoint)
Print sharing
Backup
 
Ok well I will be there by 1pm your time and send an update post. I won't change any settings but I will run setup wizard as instructed. If wizard is successful, will it require a reboot or probably not since this is a server...? Is the reboot idea a no-go or will the wizard suffice?

Thank you so much for your help.
 
Running the wizard doesn't usually require a reboot...it usually restarts the necessary services that may have been affected.

Since it's not working...not doing its job, not serving up quickbooks...there's no harm in rebooting it any time you want.

When it reboots, you should see the Quickbooks database manager icon somewhere..launch it..point it to the shared folder that houses the company files...have it scan and find the files, and minimize it.
 
Chances are that the Quickbooks server is just fine but can't connect because the network is hosed. Get the network working correctly on the server and I bet it starts working again.
 
Quickbooks needs to run from a computer on the local network that has a folder shared..and that has the Quickbooks Database Server manager installed to serve up the file.

Well..let me back up a bit....you can have your Quickbooks company data hosted in Intuits cloud...get to it via browser. And there are other more complicated answers like a terminal server.

The reason to have a server? There are many. I wouldn't want to remove this small business server, or recommend removing it, without seeing LOTS more of the existing network.
Other file shares
My Documents redirect
Company Web (you saw that...it's the intRA web site....Sharepoint)
Print sharing
Backup

Ditto that. This server may be doing more for the end users then even THEY realize. Just because they say it does nothing for them doesn't mean that is the truth. End users are clueless idiots.
 
Chances are that the Quickbooks server is just fine but can't connect because the network is hosed. Get the network working correctly on the server and I bet it starts working again.

All the computers show up as connected under the 'network' tab of SBS console? Does that even make sense? All network shares have been restored-- doesn't that mean that the internal network has been restored? The server just won't connect to the internet. All other computers connect to the internet.

So I have to manually start the Quickbooks server every time I reboot?-- (which hopefully I will never have to do again lol)
 
@YeOldStoneCat-- I am reading your article, as suggested. Does leaving the servers default gateway setting blank pose an issue? That is how the network was configured before I touched it, but setting it to the router's IP address seems to make more sense.

Okay-- Thanks again.
 
Progress!!

The wizard restored internet connectivity to the server.

Now the clients can't reach the shares. I am restarting them to see if that fixes the problem.

Just to clarify, Quickbooks should not be open on the server?

THANK YOU ALL FOR SAVING ME!!
 
If they did it correctly, doubtful, quickbooks shouldn't be install on the server. Only the QB database manager. That program has to be running. It isn't a full copy of quickbooks. It's just a tool to host the files and advertise them on the network.

As for the shares. You probably will have to remove the connections and recreate them. Goto each workstatation and delete Drive F(or whatever drive letters are being used) and reconnect them. Make sure you can see the server on the network first. You may have to shutdown and reboot EVERYTHING.(server, workstations, switches, hubs, modems, PRINTERS) All computers even the server. Boot modem, switches, first. Then Boot the server. Wait till it is up and then get to the workstations.
 
Not sure what you mean.

What I mean is at a workstation you can open the start menu and type

\\server

*replace "server" with whatever the netbios name is of the server.

and the shares for the server open up.

If you open network neighborhood/My Network you should see the server icon and be able to click on it.
 
Last edited:
OKAY-- so I can't see the server. Thanks man. I'm learning a lot from you. The clients can see each other but not server.

I can ping the server though.

Also, form the 'Network' tab in the SBS2011 Standard Console that appears by default at boot-- the clients are 'online'

Did the network reboot also.
 
Last edited:
Post an IPCONFIG /ALL from one of the workstations.
If the "router" is running DHCP, and not the server..the workstations are probably being handed the routers LAN IP, or the external DNS servers that the router gets from the ISP....thus the workstations cannot properly find the domain controller (which runs active directory...meaning DNS is underneath)....and they will fail to properly log into active directory.
 
Post an IPCONFIG /ALL from one of the workstations.
If the "router" is running DHCP, and not the server..the workstations are probably being handed the routers LAN IP, or the external DNS servers that the router gets from the ISP....thus the workstations cannot properly find the domain controller (which runs active directory...meaning DNS is underneath)....and they will fail to properly log into active directory.

Yep. I'd like to see one for the server too.
 
Yea I'm learning-- SERVER


Windows IP Configuration

Host Name . . . . . . . . . . . . : BAYPETRO-SERVER
Primary Dns Suffix . . . . . . . : baypetroleum.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : baypetroleum.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 54-04-A6-A6-94-2B
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a597:1b12:7078:563b%11(Preferred)
Link-local IPv6 Address . . . . . : fe80::abbf:8306:16fa:f1ae%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 190055590
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-A2-C5-AA-54-04-A6-A6-94-2B
DNS Servers . . . . . . . . . . . : fe80::abbf:8306:16fa:f1ae%11
192.168.0.5
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{E14E376B-9345-4908-AF08-C5D7E5D99E4C}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

CLIENT:


Windows IP Configuration

Host Name . . . . . . . . . . . . : KAKHI-PC
Primary Dns Suffix . . . . . . . : baypetroleum.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : baypetroleum.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
Physical Address. . . . . . . . . : D0-67-E5-0C-54-E6
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::30ee:16fc:4229:9489%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 248539109
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-61-06-5F-D0-67-E5-0C-54-E6
DNS Servers . . . . . . . . . . . : 192.168.0.5
192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{3120BFE2-9DE0-41BE-BC17-BFD2B0006309}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
 
Last edited:
Ahh Client workstations are setup manually...using the SBS IP first..and the routers IP second.

So that should work.
You could adjust the login script to net use * /del /y and have them reboot twice..and then edit out that line so the normal mapping occurs again.
 
Back
Top