Different IP address for each user?

[jerichardson]

In interest of trying to reduce open holes in the network we are trying to setup a single VNC server that each of us can remote to. However, in order to do that and make it so that each user could be potentially logged in at the same time we need to give each user on that machine a different IP address. I know that Server 2003 has the ability of housing up to 32 ip addresses. Is there any way to give each user a specific ip address?

 

[58sniper]

No. NTIAO, anyways.

IP addresses happen before the user is logged in. Not sure what you're trying to do, but I don't see how that's going to reduce "holes in the network". Imagine the DNS issues you'll have to deal with that more than one IP address going to the same box.

Pat Richard
Microsoft Exchange MVP
Contributing author The Complete Reference: Microsoft Exchange Server 2007

 

[jerichardson]

It would reduce holes in the network by having 1 port open for VNC instead of the 11 or so we have now. I'm not as concerned about the DNS problems. I just want to know if there's a way to make this work.

Is there a way to make UltraVNC listen on a specific IP?

 

[cajuntank]

If you are trying to mutisession VNC, I believe that only works under Linux. You need Terminal Server CALs to mutisession to the server, VNC on a Windows box will just be remote control of the console.

 

[TheLad]

VNC for your scenario would not work, as suggested above Terminal Services would work for what you are trying to achieve but you would have to buy TS CALS (licenses) for each of the users who would connect (via RDP which listens on port 3389)

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[jerichardson]

We are trying to make it so that there is a single box that runs all of the VNC sessions. We would have the techs remote into the single machine and then have the remote users use a single click VNC to access the VNC server.

What I need to find out is if there is a config file or something that can specify that, let's say John Doe, has his VNC on his profile listening on ip address 192.168.0.1 and then Jane Doe has her profile on the server listening for 192.168.0.1

 

[cajuntank]

Understand that the only thing VNC is going to do is control the 1 console session, again 1 console session only. Even if you did have multiple VNC users come in on that 1 session, they would all fight for control of the screen, mouse and keyboard, I don't think that's what you want.

I'm guessing you are wanting your users to be able point to one remote control server and come in and have access to there own session so that each of them has an individual "desktop" experience. This is what's called a multisession and VNC under Windows CANNOT do this. Windows itself can multisession in the form of Terminal Server and you must purchase TCALs for however many users you want to log in this way.

Hope that's clearer.

 

[jerichardson]

I think you've got this backwards. I want it to do this:

1. End user double clicks a Single Click VNC Icon
2. That brings them up with the selection of names
3. They double click on Jeremy
4. That initiates the allow/deny window on a single server for my user account
5. I log into that single server using RDC (I know you have to buy multiple licenses and that doesn't matter) into my user account and can then see the allow/deny window

Then I want User B to do the same thing, but be able to click on John Doe and then John Doe logs into that single VNC server under his profile and sees a separate allow/deny window from User B.

 

[cajuntank]

VNC will only access the console session, nothing else, I don't care how you cut it, license it, add IP addresses, or sing it a song. There is only 1 "Console" session capability on a Windows box and VNC can only access that 1 "Console" session.

If you RDP into a terminal server you are running a session outside of the console so by definition you won't be able to run VNC. You have to run mstsc.exe /console and only then will you be in the "Console" session and can run VNC, but anyone else RDP'ing in will be in a non-console session meaning they cannot run VNC.

Do a google search on "running vnc on a terminal server" and you will see about it running only on the "Console" session.

Hope I was clearer'er.

 

[jerichardson]

Thanks! Any other ideas how to do what we're trying to do? Our two objectives are to continue using VNC (we have about 2000 clients and we don't want to change them all) and we only want to have a single port open.

 

[jerichardson]

I found something that should work for this, Ultra VNC repeater. However, I'm having trouble using it. I have the repeater setup but I don't know how to access it. I'm setting up a Single Click III setup as shown here:

http://www.simply-postcode-lookup.com/SingleClickUltraVNC/SingleClickVNC.htm

However, I'm having trouble getting this to work even internally.

[HOST]
Simply Support Desk 1
-id 1 -sslproxy -connect 172.30.16.97:443 -noregistry
#172.30.8.38==repeater ip
#SSL -> :443 needed

That is the HOST section of my helpdesk file. However, I don't understand which IP does what. I'm assuming that the first IP is my machine's ip address and the second ip is for the repeater.

Also, when I try and launch the executable using the file that I just showed it will launch the exe, give the popup stating it will retry so many times, then just close.

Any ideas? I don't know much about this at all.

 

[etjohnson81]

with terminal server liscences to the server, you can connect out to the others. you would have to specify an IP for each person and have their VNC client listen on just that IP.

i think some of the others made this more complicated.

As they did state, you can only help one user at a time per terminal server session.

We do a similar thing where we rdp to a server, then connect to the end user at the off site location to help with issues.

Travis

http://www.bluelinenetworks.net

 

[jerichardson]

How do you get each user's vnc to listen on a specific ip?

 

[TNGPicard]

jerichardson,

> How do you get each user's vnc to listen on a specific ip?

etjohnson81 said they RDP to a server -- they RDP to ONE ip address on ONE port which can handle MULTIPLE connections with each user having their own desktop experience. THEN they use the VNC Client/Viewer to connect to a different VNC servers for different clients. Client A might be 15.1.2.3, Client B might be 16.17.18.19. VNC on the same box is not taking multiple inbound connections which is what it sounds like you're trying to do.

TNGPicard / Mark