Re: Userenv error EventID: 1000
From: Roland Hall (nobody_at_nowhere)
Date: 10/04/04
- Next message: Seto: "Re: Fails to load Taskbar. Cannot access desktop"
- Previous message: E Humphries: "Start menu programs don't appear"
- In reply to: Kevin D. Goodknecht Sr. [MVP]: "Re: Userenv error EventID: 1000"
- Next in thread: Ace Fekay [MVP]: "Re: Userenv error EventID: 1000"
- Reply: Ace Fekay [MVP]: "Re: Userenv error EventID: 1000"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 4 Oct 2004 02:23:01 -0500
"Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message
news:uxgu%23R8pEHA.1952@TK2MSFTNGP12.phx.gbl...
: In news:uhc8a$7pEHA.3896@TK2MSFTNGP15.phx.gbl,
: Mike Morgan <mmorgan@ci.gulfport.ms.us> commented
: Then Kevin replied below:
: > Yeah, I just did it both ways, too. Either way
: > (\\netbiosname\sysvol or \\fqdn\sysvol) works fine. On
: > the upside, the error only occured once last night and I
: > can't find a single problem with either the domain or the
: > server. It passes every test so far. I guess I'm going to
: > proceed until I run into a problem.
:
: Just to verify, these are the names of the domain and not the machine's
: name.
:
: I have also seen this error if the DC is multihomed and the NIC with file
: sharing is not the default connection. (Top of the binding order)
: TO check the binding order, right click on Network Places and choose
: properties from the pop up menu. Then in the Network properties window
: select the Advanced menu, then Advanced settings. In the connections pane
: (top) the internal NIC should be at the top of the list and File sharing
and
: client for MS Networks selected in the Bindings pane.
I helped someone setup an FTP server yesterday who was having issues with
Event ID: 1000 Source: Userenv
The FTP server was a DNS server with 2 NICs. Public address on one NIC,
private IP on the other.
The resolution had four parts:
1. User was a domain user and needed to be added to group policy for local
logon.
2. Primary DNS on public NIC needed to point to itself (public address -
also running DNS). Primary DNS on private NIC needed to point to DC DNS.
3. Primary DNS on DC needed to point to itself. (Primary was public address
of other server and secondary it pointed to itself)
4. The private NIC needed to be first in the binding order and file and
printer sharing needed to be removed from the public NIC.
I believe the Primary DNS pointing to the public address of the multihomed
FTP server was the main issue.
The FTP/WWW configuration also had to be modified to allow for a single IP
address hosting multiple FTP sites but it's not relevant here.
The original problem was the FTP user could not authenticate but web and
FPSE authticated fine. Hopefully this info can be of some benefit to the
discussion.
-- Roland Hall /* This information is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. */ Online Support for IT Professionals - http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech How-to: Windows 2000 DNS: http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201 FAQ W2K/2K3 DNS: http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382
- Next message: Seto: "Re: Fails to load Taskbar. Cannot access desktop"
- Previous message: E Humphries: "Start menu programs don't appear"
- In reply to: Kevin D. Goodknecht Sr. [MVP]: "Re: Userenv error EventID: 1000"
- Next in thread: Ace Fekay [MVP]: "Re: Userenv error EventID: 1000"
- Reply: Ace Fekay [MVP]: "Re: Userenv error EventID: 1000"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
