Re: FSO to non domain server UNC?

From: Leythos (void@nowhere.com)
Date: 01/15/03 

From: Leythos <void@nowhere.com>
Date: Wed, 15 Jan 2003 12:40:42 GMT

In article <eMYMqiDvCHA.440@TK2MSFTNGP12>, levinson_k@excite.com says...
> This should work fine. Have you tried enabling auditing on both machines to
> see what account is being denied access to where?

Yep, the NAS does not record any attempt to access it by the FSO. There
is no log in anything that indicates the FSO even tried to get to the
NAS. I've enabled all security auditing features - it appears as though
the FSO uses some computer account, and since the computer/NAS are not
part of the same network there is no auth. for it to access the NAS.

Most articles cover same domain.

> You didn't specify that you had already tried the items below, so I'm going
> to be cautious and assume maybe you haven't.
>
> You do need to have an identical IWAM or IUSR account set up on the remote
> machine, and it needs to have the exact same password as well. This means
> you need to change the IIS MMC so that it does not manage the IUSR password,
> and you can change or find out what the IUSR and IWAM passwords are set to
> in the metabase using the ADSUTIL.VBS command. This command is documented
> at www.microsoft.com/support, search for ADSUTIL. The password for that
> account must be set to the same thing within Windows on both machines and
> also in the IIS Metabase.

Been here, done this 8 ways to Sunday - in fact two other admins have
tried this before me.

Since they two devices are not in the same AD/Domain, and the FSO can
not be specified as using a user account, it's not possible from what I
can see.

 
> "Leythos" <void@nowhere.com> wrote in message
> news:MPG.188e729acfccf00f989943@news-server.columbus.rr.com...
> > I have two servers, one is a NAS device NAS1 running W2K, the other is a
> > standard Windows 2000 Server WEB1. WEB1 is setup as a workgroup server,
> > no Active Directory - NAS1 is also not AD and is in it's own workgroup.
> >
> > I have a website running on WEB1 that used a FSO connection to the NAS1
> > device "\\192.168.0.X\sharedfolder", but it never connects. I've read
> > all the articles about passwords and ensuring the IWAM and the Anonymous
> > user accounts have the same user/pwd on the NAS as they do on the WEB,
> > but it just won't connect.
> >
> > I can map a drive to NAS1 using net use O: \\192.168.0.X\sharedfolder
> > somepassword /USER:IWAM_WEB1USER.
> >
> > I can get the WEB1 FSO to connect to another domain servers shares, just
> > not the Iomega NAS device.
> >
> > All this is using IIS/ASP (not .Net).....
> >
> > I've tried all the MS KB article fixes....
> >
> > Any help would be appreciated.
> >
> >
> >
> > --
> > --
> > Leythos999@columbus.rr.com
> > (Remove 999 to reply to me)
>
>
> 

-- 
--
Leythos999@columbus.rr.com
(Remove 999 to reply to me)

Relevant Pages

  • Re: SMS 2003 + NAS
    ... Let's approach this outside of the NAS issue entirely for the moment. ... site system connection account. ... Of course the site server's machine account must have rights on the DP. ... will probably want to clear the site server machine ...
    (microsoft.public.sms.setup)
  • Re: SMS 2003 + NAS
    ... Let's approach this outside of the NAS issue entirely for the moment. ... site system connection account. ... Of course the site server's machine account must have rights on the DP. ... will probably want to clear the site server machine ...
    (microsoft.public.sms.admin)
  • Re: Indexing a NAS share
    ... If you are indexing a virtual directory that is pointing to the NAS share ... If you added the share manually to your catalog then Index Server uses ... Otherwise we use the SYSTEM account. ...
    (microsoft.public.inetserver.indexserver)
  • Re: ASP.NET application cannot access network drive
    ... I finally figured out a way to disable all "guest" access to the NAS ... was to create a new "ASPNET" user account on the NAS drive WITHOUT ... Windows' aspnet_wp.exe worker process uses. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Unable to Share Folder
    ... It may look daunting, but if you follow the steps at the links and suggestions below systematically and calmly, you will have no difficulty in setting up your sharing. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ... You do not need to be logged into the same account on all machines and the passwords assigned to each user account can be different; the accounts/passwords just need to exist and match on all machines. ...
    (microsoft.public.windowsxp.general)