• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 381
  • Last Modified:

Slow guess access to Windows 2008 Server

I have a multi site network Novell Network and I have added a couple of Windows servers as needed.  I have the Primary Domain controller in the main office and another server at a separate site.

I have setup the external server as a Global Catalog and DHCP server.   I have shared some folders on this server and added a Net Map command to the Novell login to map them when users logon.

It is taking forever to connect to the server whether it is during the initial logon or a Net Map command issued later.  I am also getting several complaints about the server being extremely slow after a connection is made.    

The server is on the same subnet as all the local computers and I have created a subnet in AD and assigned it to the site.   I am using the Primary Domain controller in the main office as the DNS server.  The users who are trying to connect are not part of the domain and the Net Map command specifies the user as guest.

Any suggestions as to why it takes so long to connect and the access to files is slow afterwards?
0
qvfps
Asked:
qvfps
  • 2
  • 2
1 Solution
 
Cris HannaCommented:
The guest account should never be enabled in Windows.  every user should have an account with user name and password to match Novell.  And then not specify a user in the netmap
0
 
qvfpsAuthor Commented:
That is the end goal. This is a remote site so I was trying to avoid  changing all of the computers from a local account to a domain account and having to recreate their profiles until I had the time to be onsite and assist with it.

Does the guest account have drawbacks other than open access?
0
 
Cris HannaCommented:
The guest account is NOT a member of any security groups, so by default it has no access to anything.

The computers need to be fully functional in the domain before expecting reasonable results.
0
 
qvfpsAuthor Commented:
I think the issue is resolved.  The server has two network connections and one of them was flopping between 1gig and 10M.   After that was resolved the connection has been acceptable.  

Thanks for your input on the Guest account.  This is not intended as a permanent solution.  It is just a temporary situation to get everyone off a not Microsoft server which was failing and to get by until I could be onsite to correctly connect everyone.   I have no one onsite who has the time to do it and several users for who this would be a traumatic experience if I asked them to do it or even tried to do it remotely.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now