Re: access problem using UNC on foreign DC

The ticket timeout is set to 24 hours on the "B" server (Corsair) which is the DC for the MTSVOICE.local domain. All workstations are member of MTS.LOCAL domain which has Mustang as its DC. Is there something about Vista and accessing foreign DC that could be causing this issue?

Thanks

"Charles MacLean" <CharlesM@xxxxxxxxx> wrote in message news:86A8C5E3-22D0-4EC7-AF89-8085A209EB74@xxxxxxxxxxxxxxxx
We used the administrator's ID/password for the initial connection to Drive1-ServerB and then asked Windows to remember it. We are not prompted for ID/password after a fresh boot of the Vista WS but after a while if we try to click on the Server B -Drive1 we are once again prompted for the ID/password. When this happens the correct ID/password does not grant us access to the drive. We are experiencing a similar problem with an XP Pro WS but it is much less frequent.

Any ideas?

Thanks,
Charles MacLean
MTS, Inc.


"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message news:ff16fb66271458cbb76769fdd1ab@xxxxxxxxxxxxxxxxxxxxxxx
Hello Charles,

How are the permissions configured for drive1 on domainB? If the user account and computer are member from domainA, there must be an user account/password be used to access the SQL machine on domainB. I assume the connection is lost because the security ticket is timed out.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

We have two Windows SBS 2003 RS 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.
The statements returns TRUE after a fresh boot of my VISTA workstation
and fails (retuens FALSE) a few hours later. If I reboot my my VISTA
workstation it will immediatly return TRUE. Corsair is the DC that
has no workstations accounts that we are trying to copy files to.

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

Does anybody know what is going on here?

Thanks in Advance!!!





.

Relevant Pages

  • Re: SBS 2003 Misconfigured?
    ... up one of the workstations via remote web connection, ... but why are you looking at the server rather than the workstation? ... (this will show you the DHCP lease info). ... The Netgear, or whatever you use as your gateway to get out to the Internet. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... When I remote back into the server and look at DHCP, ... I assume DHCP assigned it, but how can I verify that. ... the workstations, I was having connection problems with the workstations. ... The netgear has a setting for the Internet IP which is set to the ...
    (microsoft.public.windows.server.sbs)
  • Re: status of mas90 client
    ... Gregg Hill wrote: ... The Dell PE 2800 server ... The workstations are slow to open applications, slow to save files to the ... SBS BPA gives a clean report. ...
    (microsoft.public.windows.server.sbs)
  • Re: status of mas90 client
    ... Gregg Hill wrote: ... The Dell PE 2800 server ... The workstations are slow to open applications, slow to save files to the ... SBS BPA gives a clean report. ...
    (microsoft.public.windows.server.sbs)
  • Re: access problem using UNC on foreign DC
    ... We are not prompted for ID/password after a fresh boot of the Vista WS but after a while if we try to click on the Server B -Drive1 we are once again prompted for the ID/password. ... How are the permissions configured for drive1 on domainB? ...
    (microsoft.public.windows.server.security)
Loading