Hi everybody!

I have a problem. When I'm trying to access the shared folders on my Win 2003 Server from my Win XP, it takes 20 seconds before it shows the content of the folder. After that it takes no time accessing the folder.
It's like there's some kind of timeout that has to timeout before a new "session" is started.
When accessing the Win XP folders from the server there's no timeout.

I have seached over and over again on the Net without finding any solution to my problem.

Maybe, one of you guys know how to fix it?

Any help is appreciated.

Thanks
Frederick

In Ref: to your problem with slow access time to your server. I just recently had a similar problem when trying to add a third party application on a 2003 server which required me to access a folder from XP clients that was stored on the server(2003).
I found that that it was mainly because the clocks of all the systems and the server were not synchronized. Part of the authentication process with Kerobos encryption relies on the sychronization of the Server and Domain controller. The clocks of your clients may be the reason for your delay. It was for me.
It would not hurt to also look at your event log that is under administravtive tools. This is what tipped me off to the fact that sychronization of clocks was part of my problem.
Good Luck.

Well, I only have one (Win XP) computer connected to my 2003 Server. I checked the Event View on the server and it seems that Win XP makes a couple of anonymous login attempts before it logins on. All of them are successful according to the log.
So instead of browsing the files via the Microsoft Network folder I mapped a couple of network drives and wrote the login and password. But it still makes a couple of anonymous logins when browsing the network files. That's all that the Event Viewer tells me.
I at least found the session timeout setting and changed it from 15 minutes to no timeout. But the slow login still apply.

Where did you change the clock syncronisation setting?

I'll try anything (but sex). ;)

Cheers
Frederick

Fredrick,
Make sure that your clock on your workstation is the same as on your Server. I need to know more about what you have set up. Is dns running, is dhcp running, have you already installed active directory? Have you set the server up as a stand alone server in a workgroup setting or a domain controller in a domain?

Have you joined the workstation to the domain, if in fact you are set up as a domain.
Check under Start/control panel/system/computer name tab/ click the change button. What do you have there.
Tell me what your ip configuration is:
you should be using static assigned IP addresses. Try setting the Server Ip address to 192.168.1.150 and the workstation to 192.168.1.151. Use the modem address as the default gateway.
Keep me posted.

Well,
it's a stand alone server and the Win XP computer is on the same workgroup. The XP puter has it's IP assigned with DHCP. And I use Internet Connection Sharing to be able to surf on it.

Can I set a static (local) IP for the XP puter when using DHCP? Now it's dynamicly assigned.

I've set the dns and gateway in XP to my server's IP.

Should I use Active Directory and if so, where do I enable it?

Both clocks are syncronized to a internet time server.

Thanks for taking the time to answer my questions!

Cheers
Frederick

Hi Fredrick,
For now shut off the dhcp service.
I believe it is under adminitrative tools/services/dhcp server. I don't have it right here in front of me so don't quote me. The reason for this is that it is one less thing we need worry about while fixing this. Secondly DHCP was designed to make it easier to administer a large network so that you didn't have to sit at each computer to set the ip address. Considering that you only have one client, we can eliminate it for now.
Are you using XP pro or Xp home. Please say XP professional!
The anwser to your next question is yes. You can statically assign the ip while running DHCP, but just stop DHCP for now.
I am not completly sure but I believe that Active Directory must be running before DNS will work correctly. The easiest way to do this would probably be to uninstall DNS and then install active directory. What should happen is, after or during the installation of active directory you will be propted to set up DNS at the same time. This is all done through a set up wizard. Just anwser the questions and you should be all set. Once you complete this step your network will become a domain. If you have XP pro you will need to change the client to be on the domain that you created when setting up active directory.
Now statically assign the server ip to 192.168.1.150 and the workstation to 192.168.1.151. The default gateway of the serve should be 192.168.1.1 and your client should be 192.168.1.150. Both server and client should have preferred DNS address set to 192.168.1.150.

Summary.
1) Stop DHCP service
2) Uninstall DNS
3) Install Active directory
4) Install DNS
5) set ip addresses
6) join client onto domain
7) create user account in active directory(let me know if you need help)

**there are two ways to set up active directory. 1)Start/run then type dcpromo.
2) Start/manage your server/add service.

I know it is a lot but I think your problem is DNS related. I think active directory could solve it.
good luck.