WinXP client on a Win2k Domain

[Steve Parks]

We have a small domain with a Win2k domain server and
several Win2k client machines. I just bought a top of
the line Dell with WinXP Pro and Office 2003 Pro.

My machine runs great if everything I do is local, but as
soon as I try to do something on a mapped network drive
there is about a 50% chance that some random error
occurs. For instance, in Explorer, sometimes connecting
to the drive just to look at files takes up to a minute
to connect and sometimes (rarely) it doesn't connect at
all.

A more common problem (70% of the time) while in Adobe
Photoshop 7, I try to save a file to the networked drive
and it comes back and says File System Error and writes a
0KB file or it says the file is in use by someone else,
which it clearly isn't, because the file didn't exist
until I just tried to save it.

Is there anything I can do to improve the networking
status or did I just waste my money on a useless
operating system. This computer was going to help
improve productivity but it's made it twice as bad.

Thanks,
-Steve

 

[BryanW]

Steve;
This isn't much consolation; however, I have run into the
exact same issue! One of our departments just purchased
20 new PC's all running WinXP Pro to replace Win98
systems. All these systems simply crawl when
authenticating to a Win2K domain controller, when I remove
them from the domain they function 85% better, but I still
run into odd issues such as you described with file locks
or file in use messages and overall system slow down
issues.
I am really hearing it from my users as they were to
believe these new systems running this newer OS would
improve their efficiencies over their old P2 systems
running Win98 and what do I tell them? I've tried just
about everything and I have posted to numerous groups here
for assistance but the only reply I've received in these
newsgroups is to check DNS, which I've done and DNS is
fine as is WINS (worked great with Win98 machines).
I will format their new hard disks and reload Win98 before
I pay MS their standard $200 fee to remedy this issue!
ANY HELP WILL BE GREATLY APPRECIATED!

 

[Guest]

Have had same problem. I have worked out a little of the slowness. I'll tell you what I have done, it may help

I am running xp clients, 2000 server(seperate box), linux mail server(seperate box), and smoothwall for firewall solution(seperate box). Left linux/apache webserver outside firewall

I create an internal ip 192.168.0.0 under the firewall. I made the 2000 server(fileserver) primary dns. The firewall secondary dns. Then created my domain xxxx.org inside the firewall. I created each user and added each computer in active directory user and computer directory and set the permissions. I did not use wins, domain/trust directory, etc. Every time I try to start setting rules and permissions, they seem to bog down the auth process

Then I mapped the public area for users on the server, and mapped a personal folder for each user on the server.

It is the simplest config, but when I try using bells and whistles, logging on to the network becomes painfully slow, or returns weird errors.

Don't know if it will help you, but after way too many late nights trying to figure out why xp doesn't like to authenticate to a 2000 box, ;(

----- BryanW wrote: ----

Steve
This isn't much consolation; however, I have run into the
exact same issue! One of our departments just purchased
20 new PC's all running WinXP Pro to replace Win98
systems. All these systems simply crawl when
authenticating to a Win2K domain controller, when I remove
them from the domain they function 85% better, but I still
run into odd issues such as you described with file locks
or file in use messages and overall system slow down
issues.
I am really hearing it from my users as they were to
believe these new systems running this newer OS would
improve their efficiencies over their old P2 systems
running Win98 and what do I tell them? I've tried just
about everything and I have posted to numerous groups here
for assistance but the only reply I've received in these
newsgroups is to check DNS, which I've done and DNS is
fine as is WINS (worked great with Win98 machines)
I will format their new hard disks and reload Win98 before
I pay MS their standard $200 fee to remedy this issue
ANY HELP WILL BE GREATLY APPRECIATED

 

[Guest]

I really don't encounter very much slowness. When I
login to the domain (vs to the machine) it takes about
twice as long, but it's still less than a minute. I
don't notice any problems with speed while on the
network, but occaisionally I experience problems saving
files with Photoshop and then deleting the 0KB files it
creates.

I'm running NAV2004; does anyone know if it scans files
when you save them to a mapped network drive? Maybe the
Antivirus is somehow locking the file and that's why
Photoshop can't finish writing it.

-Steve

-----Original Message-----
Have had same problem. I have worked out a little of

the slowness. I'll tell you what I have done, it may
help.

I am running xp clients, 2000 server(seperate box),

linux mail server(seperate box), and smoothwall for
firewall solution(seperate box). Left linux/apache
webserver outside firewall.

I create an internal ip 192.168.0.0 under the firewall.

I made the 2000 server(fileserver) primary dns. The
firewall secondary dns. Then created my domain
xxxx.org inside the firewall. I created each user and
added each computer in active directory user and computer
directory and set the permissions. I did not use wins,
domain/trust directory, etc. Every time I try to start
setting rules and permissions, they seem to bog down the
auth process.

Then I mapped the public area for users on the server,

and mapped a personal folder for each user on the server.

It is the simplest config, but when I try using bells

and whistles, logging on to the network becomes painfully
slow, or returns weird errors.

Don't know if it will help you, but after way too many

late nights trying to figure out why xp doesn't like to
authenticate to a 2000 box, ;(.