Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 627
  • Last Modified:

WinNT://localmachine/User script Hangs

We have a call to Getobject("winNT://localmachinename/username"). This is (unfortunately) run from some legacy code in VB6, as part of a login script on a Windows network, but with Novell eDirectory LDAP servers. The Login is being processed by the Novell Login GINA. The program, and call to "winNT" works perfectly across an installed user  base of several 1000 windows XP pc's, but on one site and on some PC's it hangs.

In addition it particularly hangs on cold boot but not warm boot of the PC's. In our script we are trying to retrieve the user's SID, once we have the object returned from the winNT call.

The network uses a mix of NETBIOS/WINS/TCPIP and DNS

Our current working theory is that the getobject call is timing out on a network name resolution, however surely the call to "winNT://localmachinename/user" would check the local pc name first prior to doing a network name resolution

If we wait "5" minutes then the script does complete, however typically it would complete in a number of seconds not minutes.

Any suggestions regards solving this?
How can we stop the hang
0
Vince Wingate
Asked:
Vince Wingate
  • 3
  • 3
1 Solution
 
sirbountyCommented:
How are you deriving the localmachine name?
0
 
Vince WingateAuthor Commented:
good question - we are reading the environment variable "USERDOMAIN" - which as its Novell eDirectory and not Windows DC/AD's is the local machine name
0
 
sirbountyCommented:
Does it work if you hard code the computername in there - as a test?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Vince WingateAuthor Commented:
we have debug statements all thru the code producing a log, and although the name is actually held in a string variable - we know that the string variable is set correctly - so in the actual (vb6) code we have

dim sComp as string
dim sUser as string
dim o as object

sComp = environ("USERDOMAIN")
sUser = environ ("USERNAME")

o = GetObject("WinNT://" & sComp & "/" & sUser")
0
 
sirbountyCommented:
Hmm - I would still advise, especially since you're reaching to the environment, to grab sComp = environ("Computername") instead....and/or trim the   string value as well...
0
 
Vince WingateAuthor Commented:
We have determined the cause of this issue to be a Novell application called iPrint which was causing the WinNT:// lookup to run very slowly. Thanks for your assistance
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

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