Home Forums Discussions Problems Reconnecting to network

How come I have to re-map my network to the AC folder every time the computer re-boots? I don't remember doing this before upgrading to v4.

the easy solution is to create a batch file that maps the drive for you. here is a sample, which maps 2 drives:

the first line which contains "* /del /y" deletes all the mappings on the computer.

The next line maps the work folder on the server to your W drive, and sends the Username and password.

The 3rd line maps another drive. The Username/password are no longer needed because you have already passed them.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++

net use * /del /y
net use r: \\192.168.0.7\work /username:myUserName MyPassword
net use x: \\192.168.0.7\dictations

++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Enjoy

Which computer? The workstation reboots and then has to re-map? Or the computer that is acting as the server?

The short answer is you shouldn't have to. I would think there is something in your network settings that are making that happen.

I always bring this up on these types of questions, and I never hear back. And, given you have used the phrase "map" it may seem confusing.

But, have you tried mapping the shared folder on the server to each client and connecting to it?

I have one "server" (desktop) and one "client" (laptop). Re-mapping to the shared folder on the desktop is what I have to do everytime the laptop re-boots. I agree, I don't think I should have to and don't remember doig so previously.

Thanks.

I have a similar issue with my desktop and the Paperport received fax file. But it happened before I upgraded to V4. It began after the latest windows update which included a malicious software removal tool. It does not happen on any of the other stations.

Leslie

Bruce,

It is very important in this troubleshooting exercise, whether I can help or not, to know the following. When you say "re-map" are you referring to getting the window which asks you to browse to the desktop with the shared database or are you referring to mapping a network drive?

And, you laptop is using a wired connection?

Desktop, laptop, wireless network, nothing has changed. I click on the Windows "Start Button", "Network", "Desktop (that's the network name for my desktop, I'm not too creative), and then on the AC folder. Then everything is good until the next time I lose power and need to re-boot.

That is not what I was referring to when I said map the network drive.

But, why are you clicking on Start and then Network each time.

What happens when you reboot the laptop and simply click on the AC icon?

When I simply click the AC icon I can't connect. Browsing to the AC folder (Start/Network/username/password etc.) is the only way I can get AC to open on the laptop. Ever since the upgrade if I lose power to the laptop and need to re-boot I get an error window that says "SQL Server Connection Error" (that's why I'm convinced that it has something to do with the upgrade).

My bad. I was using the wrong term. I have gone back to the desktop ("server") and mapped the .xml file to Z: drive but still get the error message window.

This is probably because your drives where mapped using a batch file. If your computer was using a login.bat file. The MSRT probably thought it was a "malicious" file and deleted it.

I don't believe that I was using a login batch file

Map the entire folder. Not the .xml file.

I am still a bit confused. What happens EXACTLY when you click on the AC icon?

I share your confusion! Whenever I need to need to re-boot I get an error window that says "SQL Server Connection Error" with several suggested options from AC to correct the problem. None of them have worked. The final option is to contact tech support but when I did I was told that it sounded like a network problem and they didn't offer network support. It may have been that thye were overwhelmed with upgrade calls.

I believe this is the same problem I spoke of in another thread, Bert. When trying to connect, Bruce, is this the screen you get? [img]http://farm4.static.flickr.com/3651/3501793975_d0f845c324.jpg?v=0[/img]

Couldn't see the picture, Paul, until I copied and pasted it. Yes, I have seen that one before.

This is probably silly, but have you run all of the utilities including the Advanced options.

Bruce,

Should get down to basics here. What are you running for software? For instance do you have Vista Business on desktop and Vista Home Premium on laptop? Or something like that?

Seems the ubb code won't let you put an image in unless it ends in .jpg or another picture extension. Here is the picture...

I might be inclined to think it has something to do with the Network and Sharing Center's properties for the connection. I would check both machines and see what settings are there.

That snapshot is exactly what I get. I have re-worked both desktop and laptop. It only started happening AFTER upgrade to v4. I didn't change anything at that time, although I have tried A LOT of changes since.

I know this sounds trivial. Just wondering if you could let me/us know what you are running on each computer and what version of the software.

This is what I think:
1) I would rule out the OS version because at some point YOU ARE connecting.

2) You are either losing your credentials or your login information on reboot.

I'm not quite sure of the SQL Architecture of AC4, but if it uses ADO.Net, you should not be having these issues. ADO.Net does not, repeat DOES NOT, PERSIST the database connection. It connects, does its database "transaction" and disconnects.

Now it is entirely possible that the "files" you upload to AC require a PHYSICAL CONNECTION and that is what is being lost, HENCE the AC error.

But I think we need to eliminate the error as a db connection error and focus on the loss of the connection to the physical drive.

I agree, George. For me this only happens on the computers that are not joined to the domain (Workgroup computers). When the issue occurs for us I usually do a repair (right click the network connection and select repair, or in Vista "Diagnose and Repair") on the connection and delete the Network Place associated with the AC share and then remake the share giving credentials when asked. The problem seems to be with credential loss, not just to the SQL server but to the share. I can still seemingly access the share when the problem happens but I believe what I see is some sort of "cached" folder contents. When I browse to the AC database through the share I get the error again. This problem started happening either at the end of last year or the beginning of this year for us, but we were on V4 during beta since last Fall.

OK Paul, does the AC server store a path to the share? Is the share on the same box as the AC database?

Is EVERYONE using the share "mapped" to it as the SAME DRIVE LOCATION? for example as the Q drive. What may be going on is that every instance of ac that connects has to pass to the server the mapped credentials. But if everyone has it mapped differently then the drive gets reset on the last user and when you try to log back on, the Q drive is not mapped.

So eventhough the DB is generating the error, it does not seem like an DB error.

I would agree. I would say with 98% certainty that this is not a database issue or an AC issue. This is purely and simple a networking issue.

While you can connect at times, ruling out OS issues, I would make sure just for fun that File sharing is on and Password protected is off in the Network and Sharing Center. (I am assuming it is Vista since you talk about Start and Network which is not on XP -- you have never told us -- I would find it helpful).

On customize network settings, make sure it is private network and both are named the same.

Now, on a domain, when you reboot, you MUST log in with a user name and password which authenticates you to the server and allows you access to everything on the server which your admin has allowed and it sets up your network connections and reconnects your mapped drives. While mapped drives, e.g. W drive can be useful, they certainly aren't necessary.

The problem as I see it is that every time you reboot your laptop, you are losing your connection to the desktop. Does it ask for a username and password when you log back in? If it does, it is probably only asking a username and password for the local computer (laptop). So, now you are trying to connect to another computer on your WORKGROUP and trying to access a folder that is either password protected (see above) or you do not have credentials for, because you have not logged into it.

At some point you have always mentioned going to Start and Network. When you do this does it ask you for credentials (username and password) to get to the desktop, thereby circumventing the issue? If so, and you do, then that would solve the problem each time.

As George has stated and I have echoed, you may need log on and log off scripts which cancel all mapped drives and re-establish mapped drives or at least re-establish the connection to the database.

I do not think the error message you are getting -- the great big scary box that was shown earlier has anything to do with SQL. I think it is your AC's way of saying your laptop has not shaken hands with your desktop and has no idea where the path is.

I could be way off here, but when it is working, it is working because your laptop is "seeing" the desktop and vice versa. When it is not, it is because your laptop is not "seeing" the desktop. You will probably physically need to log in to the desktop from the laptop. The best way would be to use scripts.

This is done all the time. There are hundreds of thousands of support techs who have to connect to databases where they may work at five sites. They have five batch files, one for each, so they can log in quickly.

I am a bit confused on one thing. How often do you reboot your laptop? It would seem like only once per day. What is wrong with your current situation and workaround?

But, again, just for fun, make sure your network is set to private, the workgroup name is the same and you have file sharing turned on. Then for fun, map the AC folder to the laptop and THEN you should be able to enter the username and password of the desktop and click the button which says Reconnect at log in. I may be all over the place, but you can try.

By the way, are you using Vista or Windows 98?

To add to what Bert has said, I NEVER, repeat NEVER trust the "reconnect at logon" checkbox. That is why I use the login scripts.

The script I posted earlier, should work everytime, just:
1) paste the text between the stars to notepad
2) change the drive(s) to match what you want mapped
3) put in the username & password
4) save it as a batch file...you can call it hookmeup.bat
5) copy it to your startup folder and you're off.

If it resolves the problem then go with it. But I would not spend a whole lot of time trying to solve a problem when I have a work-around on hand.

Very well put guys. I think the reason that I had trouble was that the "Reconnect at logon" feature is not very good at doing what it should be. I am going to map the drive with a batch file as you suggested and see if that makes life easier.

LOL. And, I think the Reconnect at Logon is not doing what it should be doing, because you aren't really loggin on -- to the desktop computer that is.

Well, when a drive is mapped there is an option to use different credentials, to save those credentials, and to reconnect at every logon. I figured it would work as stated, but I think the joke was on me :P

Aha, it thought may have been the case. Those credentials!?!?!? Not saved. But here is the thinking: You set up "reconnect at logon," this means everytime you start up the machine the computer should connect to the drive. Unless you are 100% sure you are going to be on the same network every time, then do not reconnect at logon, because at sometimes it will find the drive and sometimes it wont.

I have a my batch file on my desktop. When I am ON THE NETWORK, I run it and I'm good!