AREV 3.12,NLM 1.12, NT Workstation and Station Id (Networking Products)
At 24 MAR 1998 02:33:29AM Greg Nuttall wrote:
Currently an AREV problem.
Could someone please enlighten me as to how to get an NT Workstation to return a UNIQUE station id that does not include the Network session number. I.E. My @Station is something like 1234*0003FE4500.
Under DOS and Windows 95 the string after the '*' is unique but under NT (Server and Workstation), this number is not unique. Our whole application is base in this uniqueness.
Please can someone tell me how to fix this problem. I need this number to be unique as it is a fundemental assumption with the programming of the database. The problem happens at our office and at the clients site so i believe it is complete reproducable.
Is it possible that the NLM 1.5 addresses this problem?
Greg.
At 24 MAR 1998 03:21AM Greg Nuttall wrote:
Note that the problem still occurs if i do not use the NLM!!!!
At 24 MAR 1998 04:48AM Steve Smith wrote:
Greg,
Have you considered using a DOS environment variable set uniquely on each workstation?
Steve
At 24 MAR 1998 12:57PM Aaron Kaplan wrote:
Unbfortunatly, the code for give me the network card ID returns back the machine name in NT. There are a few set station programs floating around, you can find them on CompuServe (GO REVELATI).
Other than that, machine names should be unique on a network anyway.
apk@sprezzatura.com
At 25 MAR 1998 06:18PM Greg Nuttall wrote:
The setname utility does not modify the Station Id if the network type is IPX/Advanced Netware…
Any Ideas RTI (or anyone)?
Greg
At 25 MAR 1998 06:23PM Greg Nuttall wrote:
I have but this should not be necessary. I will do this as my absolute LAST option as the amount of work to go through my application and modify this would be VERY time consuming.
Thanks for you suggestion
Greg.
At 30 JUN 1998 08:55AM Lee Dobson wrote:
What network client are you using? We had a similar problem using both Novell's IntraNetware Client 4.0 and the rubbish thing which comes with NT. When we upgraded to version 4.11 of the client, this problem went away. (NB. current version of Novells client is 4.3, we are currently on 4.11a and having no problems)