shared drive problem

We have two Windows SBS servers on the same segment of our LAN. They are
both DCs. The server A has all the user and computer accounts assigned to
it. The second server B, is just a SQL database server with no users
assigned to it. One of our Vista workstations has mapped drive1 on server B
as drive Z on their work station. After booting the Vista machine the user
can see all the folders on their drive Z and move files in and out of the
network drive on server B drive1. After about an hour or so clicking on the
user's Z drive yeilds a message telling that the drive is not accessable
anymore. Trying to access server B's drive1 via the network works fine after
inputting the proper credentials. Does anybody know what is going on here?

Thanks in Advance!!!

Hi, can you post the ipconfig /all of the 2 servers and the workstation?
Server A is your AD DNS Server?

--
Swartz

"Charles MacLean" <(E-Mail Removed)> ha scritto nel messaggio
news:B86BAC37-834F-42AE-B8BE-(E-Mail Removed)...
> We have two Windows SBS servers on the same segment of our LAN. They are
> both DCs. The server A has all the user and computer accounts assigned to
> it. The second server B, is just a SQL database server with no users
> assigned to it. One of our Vista workstations has mapped drive1 on server
> B as drive Z on their work station. After booting the Vista machine the
> user can see all the folders on their drive Z and move files in and out of
> the network drive on server B drive1. After about an hour or so clicking
> on the user's Z drive yeilds a message telling that the drive is not
> accessable anymore. Trying to access server B's drive1 via the network
> works fine after inputting the proper credentials. Does anybody know what
> is going on here?
>
> Thanks in Advance!!!

Hi,

The problem exists using UNC names also. The following works after a fresh
boot of my Vista workstation but fails after an hour of so. Corsair is our
DC that is the foreign domain.

Thanks

DirExist("\\CORSAIR\Drive1\$FusionImportAPD\voice\ ")

"Charles MacLean" <(E-Mail Removed)> wrote in message
news:B86BAC37-834F-42AE-B8BE-(E-Mail Removed)...
> We have two Windows SBS servers on the same segment of our LAN. They are
> both DCs. The server A has all the user and computer accounts assigned to
> it. The second server B, is just a SQL database server with no users
> assigned to it. One of our Vista workstations has mapped drive1 on server
> B as drive Z on their work station. After booting the Vista machine the
> user can see all the folders on their drive Z and move files in and out of
> the network drive on server B drive1. After about an hour or so clicking
> on the user's Z drive yeilds a message telling that the drive is not
> accessable anymore. Trying to access server B's drive1 via the network
> works fine after inputting the proper credentials. Does anybody know what
> is going on here?
>
> Thanks in Advance!!!

"Charles MacLean" <(E-Mail Removed)> wrote in message
news:B86BAC37-834F-42AE-B8BE-(E-Mail Removed)...
> We have two Windows SBS servers on the same segment of our LAN. They are
> both DCs. The server A has all the user and computer accounts assigned to
> it. The second server B, is just a SQL database server with no users
> assigned to it. One of our Vista workstations has mapped drive1 on server
> B as drive Z on their work station. After booting the Vista machine the
> user can see all the folders on their drive Z and move files in and out of
> the network drive on server B drive1. After about an hour or so clicking
> on the user's Z drive yeilds a message telling that the drive is not
> accessable anymore. Trying to access server B's drive1 via the network
> works fine after inputting the proper credentials. Does anybody know what
> is going on here?
>
> Thanks in Advance!!!



This sounds like it's either one of two things. First, possibly your DNS is
misconfiged. The ipconfig /all of the DC and a sample workstation, as
already asked for by another poster, will help us understand your
configuration. Two, which can be a combo of the above and this, is the TCP
Chimney RSS feature can be causing it.

Let's concentrate first on the ipconfigs before getting any further, because
the other issue requires registry changes.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(E-Mail Removed)

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right
things." - Peter F. Drucker
http://twitter.com/acefekay