Any DFS Guru's ??
-
I have a really annoying DFS issue, which Microsoft are aware of and say will be fixed in Windows .NET, and wondered if anyone else has had problems with DFS and got any resolutions. The problem, briefly... Our local DFS rooter is not selecting our local DFS share when it comes to accessing files etc through DFS. That is not so much a problem and is bareable, however when we run an access database with a client front-end and the backend database on a DFS share, the speed is completely unbareable. Every time a query runs it appears as though the DFS rooter is enumerating through the DFS shares and picking one. This happens everytime you try to do something in the access database. Microsoft were not keen to help and the only solution they have is to map a network drive to a certain level in the DFS structure and use the network drive to access the backend. This works to a degree but in my mind defeats the purpose of DFS. Has anyone else encountered this? Or a similar situation? Many Thanks for reading this, Rhys. Rhys Kirk
-
I have a really annoying DFS issue, which Microsoft are aware of and say will be fixed in Windows .NET, and wondered if anyone else has had problems with DFS and got any resolutions. The problem, briefly... Our local DFS rooter is not selecting our local DFS share when it comes to accessing files etc through DFS. That is not so much a problem and is bareable, however when we run an access database with a client front-end and the backend database on a DFS share, the speed is completely unbareable. Every time a query runs it appears as though the DFS rooter is enumerating through the DFS shares and picking one. This happens everytime you try to do something in the access database. Microsoft were not keen to help and the only solution they have is to map a network drive to a certain level in the DFS structure and use the network drive to access the backend. This works to a degree but in my mind defeats the purpose of DFS. Has anyone else encountered this? Or a similar situation? Many Thanks for reading this, Rhys. Rhys Kirk
RHYS wrote: Our local DFS rooter is not selecting our local DFS share when it comes to accessing files etc through DFS. That is not so much a problem and is bareable, however when we run an access database with a client front-end and the backend database on a DFS share, the speed is completely unbareable. Have you considered using a SQL Server? Depending on the size of the application it can be a daunting task, but most Access applications would upgrade easily with a simple DTS and some query rewriting. I see dumb people
-
I have a really annoying DFS issue, which Microsoft are aware of and say will be fixed in Windows .NET, and wondered if anyone else has had problems with DFS and got any resolutions. The problem, briefly... Our local DFS rooter is not selecting our local DFS share when it comes to accessing files etc through DFS. That is not so much a problem and is bareable, however when we run an access database with a client front-end and the backend database on a DFS share, the speed is completely unbareable. Every time a query runs it appears as though the DFS rooter is enumerating through the DFS shares and picking one. This happens everytime you try to do something in the access database. Microsoft were not keen to help and the only solution they have is to map a network drive to a certain level in the DFS structure and use the network drive to access the backend. This works to a degree but in my mind defeats the purpose of DFS. Has anyone else encountered this? Or a similar situation? Many Thanks for reading this, Rhys. Rhys Kirk
I'm not sure if I understand your problem completely, but if you have DFS shares in multiple sites, linked by slow connections, you do have to tell DFS to only use intra-site DFS shares, otherwise you might end up connecting through a slow link. AFAIK, DFS only goes through this selection procedure when connecting to the share, or if the share becomes unavailable. I have two DFS replicas running in the same site, and when I connect, DFS picks one, and stays there as long as possible. Speed is just as fast as over a regular share connection. Are you sure you're not reconnecting after each query or something? ps: you can always check what connections are attempted to which server by doing a 'netstat 1' just before effecting the query Lars