Reinstalled S2K3 - now XP can't access it

Hi,

I had a home network that was set up by a friend of mine, consisting of
Server 2003 acting as a file server for the XP machines in the house
(just a simple workgroup). The S2K3 machine had a bad day and I had to
reinstall the OS. I got the server back up and running, but now my XP
machine can't access the server, and my friend has since moved. I
followed the following procedure I found online for setting up file
sharing:

1. Start > Run > secpol.msc

2. In secpol.msc (Local Security Policies) navigate to Security Settings
> Local Policies > User Rights Assignment

3. Make sure Access this computer from the network contains Everyone.

4. Make sure Deny access to this computer from the network does NOT
contain the Guest account.

5. In secpol.msc navigate to Security Settings > Local Policies >
Security Options.

6. Make sure Network access: Let Everyone permissions apply to Anonymous
users is Enabled.

7. In Network access: Shares that can be access anonymously add the name
of the share you wish to allow Guest to access (it has to be on it's own
line).

8. Set Network security: LAN Manager authentication level to Send LM &
NTLM reponse - use NTLMv2 session security if negotiated.

9. To make sure these settings are enforced run gpupdate /force /boot
from the command line. The /boot will force a reboot if any of the
settings require the machine to be restarted before taking effect.

10. Now make sure your Guest account is enabled because it's disabled by
default.

11. Now create your share and set the "Everyone" group with the level of
access you wish anonymous users to have (i.e. Full Control, Read, etc).
Of course, be sure to set this on both the Share and Security
permissions.


So, I set up all the shared folders on the server, but my XP machine
can't even access the server from the network in the first place... it
seems like something more fundamental is broken, but I don't know enough
about networking or S2K3 to know where to start. I also tried disabling
the requirement that only local accounts can use blank passwords, but it
still doesn't let me access the server.

In news:Xns98A599D69CCF9Default664@207.115.33.102,
Luddite <(E-Mail Removed)> stated, which I commented on below:
> Hi,
>
> I had a home network that was set up by a friend of mine, consisting
> of Server 2003 acting as a file server for the XP machines in the
> house (just a simple workgroup). The S2K3 machine had a bad day and
> I had to reinstall the OS. I got the server back up and running,
> but now my XP machine can't access the server, and my friend has
> since moved. I followed the following procedure I found online for
> setting up file sharing:
>
> 1. Start > Run > secpol.msc
>
> 2. In secpol.msc (Local Security Policies) navigate to Security
> Settings
>> Local Policies > User Rights Assignment
>
> 3. Make sure Access this computer from the network contains Everyone.
>
> 4. Make sure Deny access to this computer from the network does NOT
> contain the Guest account.
>
> 5. In secpol.msc navigate to Security Settings > Local Policies >
> Security Options.
>
> 6. Make sure Network access: Let Everyone permissions apply to
> Anonymous users is Enabled.
>
> 7. In Network access: Shares that can be access anonymously add the
> name of the share you wish to allow Guest to access (it has to be on
> it's own line).
>
> 8. Set Network security: LAN Manager authentication level to Send LM &
> NTLM reponse - use NTLMv2 session security if negotiated.
>
> 9. To make sure these settings are enforced run gpupdate /force /boot
> from the command line. The /boot will force a reboot if any of the
> settings require the machine to be restarted before taking effect.
>
> 10. Now make sure your Guest account is enabled because it's disabled
> by default.
>
> 11. Now create your share and set the "Everyone" group with the level
> of access you wish anonymous users to have (i.e. Full Control, Read,
> etc). Of course, be sure to set this on both the Share and Security
> permissions.
>
>
> So, I set up all the shared folders on the server, but my XP machine
> can't even access the server from the network in the first place... it
> seems like something more fundamental is broken, but I don't know
> enough about networking or S2K3 to know where to start. I also
> tried disabling the requirement that only local accounts can use
> blank passwords, but it still doesn't let me access the server.

Did you install 2003 as a domain controller?

When you say access, can you describe exactly how you are trying to connect?
Mapped drive? UNC? Please show examples and the exact error message you are
receiving. PLease also provide an ipconfig /all (unedited please) of the
server and one of the clients.

Thanks

--
Ace
Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...