Networking WindowsXP on Win2K Server

I have a network with 4 PCs plus 1 laptop (occasionally) connected to a server. The laptop and 3 of the PCs run Windows 2000 Pro. The server is running Windows 2000 Server Edition. (All PCs have all the Service Paks installed and are up to date.) All of these items work fine on the network, with each allowing me to share files in and amongst the different PCs and with a SHARED folder on the server. I have problems with one PC that is running Windows XP Pro. It logs in to the server just fine and accesses any resource on the network including the SHAREED folder on the server. But after some time elapses it will not access the SHARED folder on the server without logging off the network and back on.

Apparently Active Directory is installed.

I have tried several things to determine the reasoning behind this but nothing has worked. One last thing: I have logged onto the network and immediately accessed the SHARED folder on the network. I have left that folder open and can continue to access it at any given time though it takes a while (10-20 seconds) before the folder's contents are actually accessible.

Can anyone help? I can give more information if necessary.

 

I just created a similiar thread under the Networking section. I have found a lot of similiar situations but no real solution

 

Moving this thread from XP to the networking section. It will fit better there and bet better looks I think.

First, "Apparently Active Directory is installed" is a little confusing. You can certainly be using XP-pro and 2K on an Active Directory domain setup but not sure if that is what you mean. It would be odd for a small network unless you had just set it up that way for testing and learning. Need to know that before trying any ideas/fixes.

 

This network has 1 server, 4 workstations, and one laptop. I thought I had set up the server as a domain controller but have since found out that not to be the case so I have a workgroup.

The problem has existed all the time - the workstation running XP Pro has always been able to get to the SHARED folder on the server right after logging onto the network and then not been able to get to it later without logging off and back on.

I made a statement about Active Directory that might have caused a question or two. Let me say that when I purchased the server and software and installed it I wasn't sure of all the steps. Somewhere along the way I must have set it up to use Active Directory. And apparently I did the same thing with the XP Pro workstation. I thought it was an option that I would readily see but I guess I chose it without being aware of it. In any case I do have Active Directory installed.

Thanks for looking and giving some thought to this.

 

First with 4 computers you do not need the server to be a DOMAIN controller unless you have some very unique requirements. (These are mainly for networks of networks).

No harm but some processor cycles would have been used and 1 level of unnessesary complexity that would effect things system wide. So be glad it is not a DOMAIN controller.

You may have not needed the DFS but it is there.

I am not sure at this stage about the connection problem so begin by doing the following:

In device manager remove the NIC and shut down and let it redetect and reinstall NIC.

Retest for problem before continuing, go no further if fixed.
_________________________________________________
Visit the www site of your Network card Mfg an download and install the latest driver for this card.

Retest for problem before continuing, go no further if fixed.
_________________________________________________

Rt click My network Places then properties, rt click local area connection.

At top will be displayed the Network card choose configure then advanced

Make sure Flow control is enabled.

select Media Type and "if set to hardware default" then set to Auto Select. If set already Auto Select change to 100mb, full duplex.

Get back with results.

Mike

 

Thanks for the ideas. I have already tried removing the NIC from Device Manager and that didn't do it. Also, I have changed from Auto configure to Manual Full-Duplex 100 setting on the NIC and that didn't do anything. I also know that I have the latest drivers for the NIC as that was the first thing I checked before I put a post on the BBS.

Got any other ideas?

 

Scott

Still possible driver problem.

In absence of other suggestions then do this.

D/L the driver anyway and save to disk ready to install. Just in case something not appearent is wrong with.

Disconnect all mapped /captured resources.

Remove the NIC from control panel.

Shut down

Physicall remove the NIC.

Boot back up. Do a registry clean if you can.

Shut down

reinstall NIC, a different one even if same brand if possible.

Boot back

install new driver.

Let me know. Going out to eat will think on it.

Mike

 

I cannot physically remove the NIC as it is a part of the motherboard. This is a PCChips 810 LMR motherboard. I have two and the other one is on a Win2K PC working just fine.

I'm really stumped on this one myself because as long as I leave a window open to the server I can access the files. If a few hours pass in between accessing files on the server it takes about 15 seconds to actually access the files. But, once access starts, it's just like it should be. It almost seems like when the link is idle for a period of time that I get logged off though nothing is indicating that is what is happening. That is just what it seems to be doing.

 

scotth67 - if you are just looking for a "fix" then from the behavior you describe, you could make a persistent mapping from the XP machine to the share in question.

If you prefer to dig around for a more elegant solution then my suggestion for a first step is to run Dcpromo.exe on the server. If your server was configured as a domain controller, the app will allow you to "demote" it. Demoting the last or only DC will put you back to a workgroup environment which is more appropriate for a very small network anyway unless you just want to practice with domains. At any rate the app will tell you exactly how you are structured now and we can proceed from there.