Jump to content

Recommended Posts

Posted

Hi.

Im trying to get LanView3 working, as it'll save me a fair few grand over getting another 150 licences of NSS.

 

Anyway.

Ive installed the server software on my workstation.

Ive installed the client software on a test machine.

Ive installed UltraVNC on the test machine.

 

I can send some commands to the test machine already, for example, gpupdate.

But i cant view it.

 

The errors ive seen thus far, are cannot connect. So i installed a VNC app (tight vnc). Then it asks for a password, so i put the VNC password in, incorrect password.

Then i install ultravnc, and now i get socket errors! :(.

 

 

Can someone help me get all this working:

- LanView Server working on my workstation.

- All the nessessary apps in MSI format for GP deployment, along with config files that'll hide all of it from the users, so no user prompts come up.

- Remote viewing working.

 

 

Thanks in advance all. :).

Posted
I'm pretty sure there is a vnc package that you download from the same site with a password in it of... Nah I'll pm that to you if you need it
Posted
I'm pretty sure there is a vnc package that you download from the same site with a password in it of... Nah I'll pm that to you if you need it

 

Any chance you can PM me it too :D

 

We've been using a fresh install of tightVNC and setting our own password, but a pre-packaged msi with its own password in there is a lot easier for roll out :)

Posted
I'm pretty sure there is a vnc package that you download from the same site with a password in it of... Nah I'll pm that to you if you need it

 

Whats the package called? As i couldnt find one thats suitable for vanilla networks.

Posted
vnc is hidden when running the students cant tell when we watch them, the set password in the msi isnt great but it will do, plus the kids cant run any vnc software. or install on the pc's.
Guest theeldergeek
Posted
You need to turn off the windows firewall. We use TightVNC 1.2.9 and it works a treat!

 

You don't need to turn off the Windows firewall... the latest MSI's for LANview add exceptions in.

Posted (edited)
Tight VNC MSI

 

To download the lanview package you have to register.

Is the password/setting for it IN the MSI itself?

As the download has MSI files, reg files, nai files, ini files, ect;

 

I install the client +the tight VNC msi on a VM, and it still doesnt work. LV3 can see the station, but again, cant connect to it?

 

+ How do i set a network password in LanView3? Im getting access denyed for everything.

Edited by boomam
Posted
The password is stored in HEX in the reg key supplied and can be changed before you send the MSI out, assuming you get the hex right ;)
Posted
The password is stored in HEX in the reg key supplied and can be changed before you send the MSI out, assuming you get the hex right ;)

The password for VNC?

So will the MSI automatically apply the reg file? Or will i have to deploy that myself?

Posted
The password for VNC?

So will the MSI automatically apply the reg file? Or will i have to deploy that myself?

 

Yeh, the password for VNC. Just edit the reg file in the MSI and it will deploy it for you.

Posted
Yeh, the password for VNC. Just edit the reg file in the MSI and it will deploy it for you.

How do i edit in the MSI then?

Orca?

I can see some password enteries under 'registary' but dont know the hex keys to change?

 

Have you put the password in Lanview? File>Options>Security and Custom messages.

 

I havnt no, as i dont know what it is. :p

 

Can someone PM or email it to me please?

 

Thanks. :).

Posted
How do i edit in the MSI then?

Orca?

I can see some password enteries under 'registary' but dont know the hex keys to change?

 

 

MST Software

 

That will explain it better than I can ;)

Posted

Something odd going on here.

 

I edited the MSI with a new hex code for the registry entry. Installed on a test workstation, double checked the hex code in the registry to what it should be.

Put the right password in LanView3....still doesnt work. :(.

 

Ideas?

Posted

Right.

The only way that ive managed to get this done anyway is to have the MSI go out@ default, then a script run at startup to change the registry enteries.

 

Not ideal, but better than a kick in the teath. :p.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...