Topic: Some service starts slow

[sbryan]

This will be my final question today - I promise!

We use an admin system called MAZE it is a front end for  an MS SQL database. If a user logs into our e-smith /SME server then they can't login to the admin system for about 15 minutes - they just get accessed denied type errors, if they wait about 15 minutes they can ogin normally with no further issues. A user that logs in locally to their machine does not experience this problem.

Seems that something is taking a long time to start up. Any ideas on what it could be?

[jackl]

sbryan,

Is this the same server as in your other posts?
We had similar problems after replacing an NT server, the workstations had various customized dns, wins settings and each had a static address. Try changing ip settings to dhcp on the workstation, release+renew ipaddress or reboot and see if that improves things. If not check using ipconfig that the dns and wins server and gateway are set to the SME box. If they are not check the advanced section of IP properties, you may find there are some entries there that are causing problems. In other words workstations are still looking for old NT4 box for dns requests etc.
This could account for a lot of the delays you are experiencing.


Regards
Jack

[sbryan]

Yes it is the same server - will be replaced on TUesday this week.
All workstations are on DHCP and the SME box is the DHCP server. I don't think it is a DNS problem as a user that logs into their local machine can access the SQL system immediately - same system logging into the SME server, wait 10 minutes or more. Yet it would get the same properties from the DHCP server every time.

[sbryan]

We have replaced the server, in fact simply moved the HDD to another machine which is a P4 and 1GB RAM. Problem persists, in fact it is even affecting Equation Editor in WOrd as well. The only explanation I have been able to get from our supplier is below, does this ring any bells with anyone:

"Yes, the problem is that the domain user which has been added a local administrator rights, however, doesn't have sufficient permission on the local resources. In order to overcome this problem, we could create a local user account and run the application using the local user account.
 
We need user to log-in as the domain user because the user will then have permission on resources on the network and we could implement group policy to the user. Therefore, the application should not be run with the domain user but local user. To do it, we can just right click the shortcut and instruct the application to run under different credential.
 
We have to wait for 30 minutes becausethe application will then give up about the system error and run the rest of the code."