Home Forums Discussions Problems Wireless Problem

I hope somebody can help me.

Because of logistics, my Desktops require a wireless adapter to connect to my AC database.(Trust me I'd rather hardwire everything but in this case I can't)
The computer and server both run on Windows 7 Ultimate. Everyday, however, the wireless computer needs to search for the Database on the server.
(My Windows XP wireless dekstop however never has this problem!)
How can I fix this?

Thanks

I am using the same windows you are. is the server a true server or a regular computer that you are using as a server?

If it is a true server, are you not running a windows swerver program on there?

If it is just a terminal desktop that you are using as the server (i did this up till two months ago), i had windows ultimate on it, and it is a lot slower to search. I would have a lot of issues of loading the AC when it is starting and then while i am doing thigns it took longer.

Be happy to help some more depedning on which set up you have.

Thanks for the response.

I should have clarified, it is simply a terminal desktop with Windows Ultimate that stores the AC database, not a true server.

Three thoughts I have:
1. Could the computer with the AC database (AC calls it the "main computer", whether it is a server or not) be going to sleep or "hibernating"? This would interrupt the wireless connection of the main computer, forcing the client computer to look for a database every time it logs onto the wireless network.
What to try: Use the Control Panel>Hardware & Sound>Power Options settings to set up the main computer to never sleep. If that doesn't work, set up both computers not to sleep.
2. Do you have your wireless network set up to "connect automatically when in range"? This setting is in the Network & Internet control panel (choose Network & Sharing Center, and then (in the left margin) "Manage wireless networks". Double click on the network's icon, and the connection window opens.
3. Do you have your main & client computers set up to "Turn on network discovery"? This setting is in the Network & Internet control panel (choose Network & Sharing Center, and then (in the left margin) "Change advanced sharing settings".

Post back if this works or still having problems.

niko:

i used to have the same set up that you have now. i suggest highly to convert to a server (bert arn't you proud of me now?).

The issue is that the terminal desktop that you use as your server is still doing other things as well. It is going to respond slowly. So I was having ping times between the laptop and the "main computer" of up to 30 seconds at times. It just depends on waht is being done on the other computer.

I initally thought something was wrong with my wireless and played with different routers. THe minute i switched over to the server, i instantly had a huge difference.

I would ask other docs in the area of people they used to set up the server. I did mine for very cheaP! it was very easy. the guy spent about 6 hours at my pplace from 4pm till about 10 pm and we set it up and it works great.

the other thing you can god is take that main computer and don't let anyone use it at all. but these computers arn't made to have a bunch of terminals using it at once.

later

Thank you for your recommendations!

I guess what frusturates me is that my Windows XP computer that sleeps and wakes up every morning still has no problem connecting to the database even after the "server" goes to sleep at night. For now I will stop the "server" from sleeping and let you know.

Ideally I would like a server too, as I dont like using the AC database computer as a terminal too.

Can I dedicate ANY comptuer as a stand alone server, or do I need to purchase a server specific computer?

Also what is your server set up. I'd like it very cheap too!

I found when upgrading from XP to Vista or Win 7 that the settings for networking or sharing were much more complex than in XP. I guess to provide more security, but seems mostly to cause frustration IMHO.

Ideally, choose a faster, more modern computer for your main (AC database) computer, since it will have to manage several clients accessing the database at the same time. Faster refers not only to CPU, but also adequate memory (4 GB RAM), fast hard drive access (7200 rpm or faster will have less latency), and a 10/100/1000 wired network adapter. If you continue to connect with wireless network adapters, that will be a significant lag on database access.

Also be aware that the OS can limit the number of users that can access the AC database at the same time. A database computer running Windows XP Home is limited to 5 concurrent users; XP Pro to 10 users, and all versions of Window 7 to 20 users. A Windows Server OS has essentially no limit of concurrent users.

Dr. Niko,
Check the network adapter cards on the Windows Ultimate machines. Make sure under the network adapter properties>power management tab is UNCHECKED (allow the computer to turn off this device to save power), so the network adapter is always on. I also agree that your "main computer/server" should NOT be allowed to go into hibernation mode.

On buying a server, buy one. It will do your network a ton of good. I have two Dell PowerEdge 2900, one I got new from Dell (approx $3,000) and one I got on Ebay that is a refurbished model (apporx $1,200). The Small Business Server 2010 operating system will cost you about $800. Hire someone to help implement the software and connect your computers to the server.

I have a feeling you will never have these connectivity issues if you have a real "server," not a "main computer" on the current peer-to-peer network. I am speaking as someone who at one time used Microsoft XP HOME edition for my office computers and Bert famously pointed out to me over and over: What is it about HOME that you don't understand?

As someone who myself struggled with the challenges of using a peer to peer network and converted to a client-server network, let me share that the client-server network is very robust and does not have these issues. It is well worth $2,000-5,000 to implement (or more depending on the hardware and I.T. support you require).

Great discussion!

My question is do I need a server system with server software or a stand alone dedicated Window 7 computer?
It seems like I can get more for my money (more HD, RAM, etc.) if I get a high end Desktop vs a server.

Thanks for the advice

Adam,
"Check the network adapter cards on the Windows Ultimate machines. Make sure under the network adapter properties>power management tab is UNCHECKED (allow the computer to turn off this device to save power), so the network adapter is always on."

I have two Dell PowerEdge 2900, one I got new from Dell (approx $3,000) and one I got on Ebay that is a refurbished model (apporx $1,200)."

Where is the Power management tab?

Also why did you need 2 servers?[i][/i]

John,
I tried all of this and still no luck!

If you log out of AC on a client computer, and then try to log on right away, do you still get the window that makes you search for the database?

John,

No, when I log out and re-login it has no problem. It always seems to search for the database after it is shutdown for the night. It however, never has a problem re-connecting to Internet when it restarts or wake up.

I suggest checking if the main computer appears in the "Network" pane of Windows Explorer on the client laptop when you first start up in the morning, before trying to log onto AC. This may isolate it as a wireless network issue (can't see the main computer) or an Amazing Charts issue (can access the main computer over the network, but AC can't find the database). From what you have tried, I suspect the latter. I think it would be worth trying a "Live Chat" with an AC tech person to try to reproduce the problem.

Dr. Niko,
I know I am swimming against the tide when I say this, but I have been very happy with a network running AC without a true server or server OS. I have not had any significant connection issues. It sounds like your problem is more likely related to your requirement for a wireless network; you might have the same issue even with a true server.

John is doing a great job of helping you to trouble-shoot, and I don't want to get in the way. You did say "It always seems to search for the database after it is shutdown for the night." If you restart the client computer does it reproduce the problem? If so, then don't shut down at all; why is it necessary to shut down at all at night?

Jon,

You make a valid point. I am afraid that even with a dedicated server, I may still have this problem as, I will still be running wireless.

To clarify, the client computer usually goes into sleep mode at night, and it appears that after a lengthy "sleep" period (ie until the next morning or after the weekend) it loses the AC database connection. However, if I put the computer to sleep and quickly wake it up, it somehow retains the connection.

Also could you tell me more about your network set-up?

Thanks

This must have something to do with the "hibernate" setting that is on by default in many laptops with Windows 7, but was not as common in Windows XP. It might be possible to prevent the laptop from hibernating in the Power options Control panel. Or as Jon said, don't shut down, just close the laptop to turn off the display.

Niko

I agree with Jon. Don't shut down at night. Don't hibernate. Don't do system standby. Don't shut down your hard drives. Don't turn off your monitors (OK, you may disagree here)

IF YOU HIBERNATE, you will lose connection to the database almost every time. You don't need to. Pick up a cheap voltage/amperage/wattage meter from Home Depot. Test with all modes. You will gain very little by shutting down at night. And, that will be more than made up for by a good night's sleep.

The jury is out on whether computers last longer staying on or off. I am a big believer of their staying on. When do you run antivirus scans? During the day? Most would run them at night. Backups? Usually at night. I have computers four to seven years old who need a Video card or PSU every once in awhile, but they are still going strong.

I would just have your screensaver set to automatically to lock the computer and have your staff log off. Shutting down the PC or logging off the PC or locking it will not affect your connectivity.

Also, just to be sure check your NIC cards and anything to do with being lazy turn it off. Like allow the computer to turn off power when not in use. You don't need that.

I can guarantee you that if you just log off the computers (not lock them -- which would still work), you will not have this issue.

Niko:

I can put you in touch with my IT guy. He set it up. But it was cheap. And all the other wireless in the office work much faster now too!

You can use any computer as a standalone but with servers, you get mirror drives to back everything up.

If you are going to leave it this way, do not let the server computer sleep for now. If you are not using it at home, you can do that at night, but i use mine from home so i keep everything awake all the time.

Just a couple thoughts!

OK so I kept "server" desktop on all day. On the client, I found the network adapter power settings and UNCHECKED it from turning off. However, after client fell to sleep (ie it did not shutdown), it still was looking for AC database file!?

Don't let that client sleep!!!

Dr. Niko,

Jon put it succinctly, but I will be more specific. (Actually, read my post above).

There are two places on WIN7 to make changes to power. One is on your NIC card. These generally have little effect on your networking. The other is under Power Options in Control Panel. As usual, Microsoft makes it more complicated than it needs to be with all these power plans, etc. as if you are going to change them constantly. But, you can change your settings in a number of ways. The simplest way is to go to the left side and change the settings of "Choose when to turn off the display," and "Change when the computer sleeps." Personally, I recommend changing both of these to never.

There is absolutely no reason to have your computer sleep. It is not going to save you much energy, and it is going to cause you these problems. If you only had one computer like you probably do at home, then sure, go ahead and sleep away. But, in a production environment where you are trying to network and use databases, the computers need to be on, awake and functional.

As far as the monitor, I would imagine I will get more of an argument. Again, personally, I hate having to move the mouse back and forth to get the monitor to come to life. I like to be able to walk around the office and see the screensaver and know everything is working. If you see a monitor that is not showing a screensaver, it may alert you that something is an issue.

One of the nice things of having a server and a domain is Group Policy. I can use group policy to insure that every computer on the domain cannot be changed to hibernate, sleep or have the monitor turned off.

Try this:

Set every computer to stay on all the time. They can log off or lock, but do not sleep, hibernate or even shut down (which wouldn't affect database connection but still).

After this, come in a few mornings, and if you have any issues with not being able to connect, let us know. It is always best to log off, but if the computer is only locked, then you know you will have a connection, because nothing is changing as far as that goes. The only downside to not logging off and just locking is, ironically, that very thing. That computer is possibly connected to the database, which can affect things like backups, but not always.

Dr. Niko,
So are you still having this problem, or did the suggestions above help you to resolve it?

Also, you asked above about my computer set-up. I posted it here.

Jon,

If I leave the wireless computer still logged on to AC, the computer retains the connection, but if I ever decide to restart the computer, it still needs to look for the AC database.