Re: Which Server 03 best suits my needs?

From: Miha Pihler (mihap-news_at_atlantis.si)
Date: 10/12/04 

Date: Tue, 12 Oct 2004 20:48:53 +0200

Hi,

If I am not mistaken, your FTP server is also domain controller. If this is
so, do steps 2 and 3 in Default Domain controller policy (not local policy).

Open Active Directory Users and Computers and right click on Domain
Controller Organization Unit. Click on properties -> Group Policy tab and
select Default Domain Controller Group Policy. Click on Edit button... Then
follow instructions from the article...

Mike

"pro36" <pro36@discussions.microsoft.com> wrote in message
news:8A2E9DAA-89ED-4DA7-A081-3EFCEAD04617@microsoft.com...
> Miha,
>
> Can you help? Below is my most recent contact w/IIS General.
>
> Bernard,
> Thanx for your input. I tried all options listed in the link you provided
> and still no luck. All "logon anonymously" check boxes were cleared per
> option 1. Option 2 references IIS on a windows 2000 domain controller but
I
> tried it anway although some of the categories differed. No luck. Option
3
> talks about network permission. Mine is a stand alone 2003 server. Option
4
> provided no help. I have attached a copy of log in attempt to ftp
localhost.
> Maybe the answer lies therein:
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\Administrator>netstat -a
>
> Active Connections
>
> Proto Local Address Foreign Address State
> TCP aspeedyresponse:ftp aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:smtp aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:http aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:pop3 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:nntp aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:epmap aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:microsoft-ds aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:563 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:1025 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:1026 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:1801 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:2103 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:2105 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:2107 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:3083 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:3110 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:3152 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:3153 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:3154 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:4187 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:8098 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:8099 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:42510 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:3001 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:3002 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:3003 aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:netbios-ssn aspeedyresponse:0 LISTENING
> TCP aspeedyresponse:microsoft-ds 4.26.27.163:4137 ESTABLISHED
> TCP aspeedyresponse:microsoft-ds
> wbar20.lax1-4.26.116.55.lax1.dsl-verizon.
> net:3421 ESTABLISHED
> TCP aspeedyresponse:microsoft-ds
> wbar22.tmp1-4.26.206.167.tmp1.dsl-verizon
> .net:4302 ESTABLISHED
> TCP aspeedyresponse:microsoft-ds
> wbar22.lax1-4.26.248.246.lax1.dsl-verizon
> .net:4733 ESTABLISHED
> TCP aspeedyresponse:microsoft-ds
> wbar22.lax1-4.26.251.134.lax1.dsl-verizon
> .net:1203 ESTABLISHED
> TCP aspeedyresponse:microsoft-ds
> wbar22.lax1-4.26.253.163.lax1.dsl-verizon
> .net:2408 ESTABLISHED
> TCP aspeedyresponse:microsoft-ds
> wbar3.chi1-4-41-097-158.chi1.dsl-verizon.
> net:2061 ESTABLISHED
> TCP aspeedyresponse:microsoft-ds
> slip-32-102-142-231.md.us.prserv.net:2407
> ESTABLISHED
> TCP aspeedyresponse:microsoft-ds
> user-2ivfnh1.dialup.mindspring.com:3585
> LAST_ACK
> TCP aspeedyresponse:microsoft-ds
218-160-81-156.dynamic.hinet.net:3682
> ES
> TABLISHED
> UDP aspeedyresponse:epmap *:*
> UDP aspeedyresponse:microsoft-ds *:*
> UDP aspeedyresponse:isakmp *:*
> UDP aspeedyresponse:1027 *:*
> UDP aspeedyresponse:3014 *:*
> UDP aspeedyresponse:3109 *:*
> UDP aspeedyresponse:3155 *:*
> UDP aspeedyresponse:3168 *:*
> UDP aspeedyresponse:3456 *:*
> UDP aspeedyresponse:3527 *:*
> UDP aspeedyresponse:4500 *:*
> UDP aspeedyresponse:ntp *:*
> UDP aspeedyresponse:3456 *:*
> UDP aspeedyresponse:ntp *:*
> UDP aspeedyresponse:netbios-ns *:*
> UDP aspeedyresponse:netbios-dgm *:*
> UDP aspeedyresponse:42508 *:*
>
> C:\Documents and Settings\Administrator>ftp localhost
> Connected to aspeedyresponse.
> 220 Microsoft FTP Service
> User (aspeedyresponse:(none)): anonymous
> 331 Password required for anonymous.
> Password:
> 530 User anonymous cannot log in.
> Login failed.
> ftp>
>
> thanx,
> pro
>
> "Bernard" wrote:
>
> > Double check with this kb again.
> > Err Msg: 530 User <Username> Cannot Log In. Login Failed.
> > http://support.microsoft.com/?id=200475
> >
> > --
> > Regards,
> > Bernard Cheah
> > http://www.tryiis.com/
> > http://support.microsoft.com/
> > http://www.msmvps.com/bernard/
>
>
> "Miha Pihler" wrote:
>
> > Hi,
> >
> > For what you are describing, Standard Edition should be enough, but you
can
> > configure it using Enterprise Edition.
> >
> > Once you have it working on LAN, then go and try to access your services
> > from the internet. On your NAT device (netgear router) make sure you
have
> > proper services open from the internet to your servers and that you have
> > port forwarding configured from your NAT device again to your server.
> >
> > FTP uses TCP port 21
> > POP3 uses TCP port 110
> > SMTP uses TCP port 25
> > HTTP uses TCP port 80.
> >
> > Check your Netgear router documentation how to open these services and
how
> > to configure port forwarding.
> >
> > Note, some ISPs block certain services on their end. Make sure that
yours
> > allows you to run your own server with mentioned services.
> >
> > Mike
> >
> > "pro36" <pro36@discussions.microsoft.com> wrote in message
> > news:A693013D-7777-4C87-B135-D0A9CB852490@microsoft.com...
> > > Note: Workstation experienced but Server newbie-
> > >
> > > I want to build a stand-alone (non-networked) pop mail server which is
> > > accessible via the Internet. I also need FTp & web server provided.
My
> > dsl
> > > ISP modem secures thru netgear router. I want users to access email
using
> > > Outlook from their local machine and FTp & web services normally. I've
> > tried
> > > configuring 2003 Enterprise but could'nt get ftp to login in over
Internet
> > > (although cmd window shows FTP is running). Consequently, I didn't try
web
> > or
> > > mail set up. I also own other flavors of 2003 server.
> > >
> > > Please advise or redirect to appropriate help.
> > >
> > > Thanx,
> > > pro36
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >