Terminal Server relies on the underlying Windows operating system to establish the transport for the client pool, and Windows will only issue one TCP/IP connection to the remote server – in this case Samba. This results in all virtual client sessions and share mounts being multiplexed over a single TCP/IP transport pipe to the Samba server
On a Windows Server 2008 R2 RDS Server I'm trying to maintain a separate TCP virtual circuit per each user - this for allow separate connections to a remote Samba shares per each user.
On old Windows server, you can allow each terminal server client to maintain a separate virtual circuit using regedt32, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters and adding a value named MultipleUsersOnConnection as a type REG_DWORD entry and setting the data value to 0.
I can't find the same registry setting for Windows Server 2008 R2 with RDS rolde installed.
How I can maintain a separate TCP virtual circuit per each user ?
Probably you shoud state a little bit more clearly what problem you are trying to solve, it seems to me that your users connected to RDS having an issue with connecting to Samba shares from RDS session. If this is the case look at (probably) relevant question here.
Related
Now this is the issue that I have. I need to join my Windows 7 user to Windows Server 2019 Active Directory Domain in VM. But then I'm not sure whether this could work if the Windows Server 2019 is powered off and the server is still working. If yes, I can't ping the Windows Server's ip address from my Windows 7 user cause I can't run 2 different Windows in VM. I tried to use "Save the machine state" in order to keep the server running. So I don't know if "Save the Machine state" is actually like "Sleep". And if the server domain name could be joined when the server is powered off, I can't ping the domain name from the server.
I'm not sure what you're trying to achieve here but if you want to join the Window 7 WM to the Domain of the Server you need both of them to be running and then log on to the Domain with a privileged domain user.
Anyways savin the state is not the same as power off.
I am using an android app that streams real-time accelerometer data to the specified ip address of a server. I have written a "server" in C running on Linux which is running in VMware.
I am connected to the hotspot created by the Windows7(Host machine) running the VMware Workstation.
So my question is how do I connect the virtual-machine to same network as the hotspot so that I can get the phone and the "server" program on the same network and stream data to the server program?
I use VirtualBox, but I'm guessing the settings are very similar in VMWare Workstation.
You probably need to do one or both of these things:
1) Port Forwarding. If your app is hitting port 80 (or whatever port), you'll need to tell VMWare that any hits coming in to the host machine on that port get forwarded to the VM. Of course, your VM will have to be listening on that port. I'd suggest using a high port number (over 1024) to minimize conflicts, and avoid annoying root/admin issues using a low port number.
2) Hopefully that gets you there. If not, you may need to change the virtual adapter settings on the VM. NAT mode is a good first try. If not, there are other modes (bridged, internal, host-only) you can tinker with. (Not sure if VMWare uses different names)
That's probably all you need for the topology you describe -- Android device connected directly to the same subnet as the host machine. If not, perhaps your hotspot routes all client traffic to the gateway (i.e. out to the Internet), without allowing direct access to localhost. If so, maybe there are settings for that. If not, ngrok is your new best friend.
It is SUPER easy and allows you to tunnel traffic from anywhere on the Internet to a specific service running on your machine. This would sidestep some of the issues above.
If you want to take your Android device to another network (e.g. cell network), then ngrok is absolutely the way to go, particularly for development and prototyping. This lets you avoid issues with DNS, routing, firewalls, etc.
I have the next scenario: a physical server with X cores (CentOS). In it, I am running 3 virtual machines using virtualBox (vm1, vm2 and vm3, each one with CentOS too).
Now in the physical machine, I have an internet socket binded in an specific port (says 1111). Is it possible for each vm to have access to that socket and read data from it? Maybe using a kind of port forwarding or changing the network configuration?
The idea is that each vm could access to the socket created for the physical machine for a kind of load distribution.
Is it possible?
Thanks!
I was setting up a Perforce server and only noticed options for localhosts and such. What I'm trying to do is setup up the server on a desktop machine at one household, and then be able to connect to it using the P4V Client to access the files over the internet form a another household. I no that I'll have to forward some ports and stuff but what set up files do I need to do this? I can only find info for servers that are all being run on the same network like at a business or something nothing that is over the internet. I've set up a team speak server like this where you go to connect and type in the ip address and port and then connect to the server but this dosn't have options like that, that I've seen anyway. This will be done all on Windows 7 64 bit machines. Server on desktop and clients will be on desktops and laptops. All help is appreciated and I'll be posting back with updates on what i'm doing so others can follow this as well if needed.
The server accepts TCP/IP connections, which can be from any client machine which has TCP/IP connectivity. The Perforce server configuration for telling it which IP address and port number to listen at is the P4PORT setting: http://www.perforce.com/perforce/r12.2/manuals/cmdref/env.P4PORT.html
Since you're on a Windows machine, your server will probably be run as a Windows Service, and hence its P4PORT setting will be held in the registry section for that service. You can edit the service's configuration using a registry editor such as RegEdit, or more simply you can use 'p4 set -S Perforce P4PORT=my-host-name:my-port-number' to specify the desired IP address and port.
Then restart your Perforce service from the Services Control Panel and you're good to go!
So I have a mac host and some virtual machines. I want to use ossec to monitor my virtual machines and my host, mac OS X lion. (I've already fixed the compliation issue with lion, it compiled). See this
I'm having trouble understanding what all the server and agent's roles are. If you only want ossec to run locally, you set up under local. But I have VMs to monitor, so I must select sever. But does server do what agent does on the host, as in, is there some kind of agent functionality to ensure that the same monitoring and checking is also occurring on the server just as it is on the VMs with agent?
If not, then how do I make sure that the host is also being monitored with ossec? What I had thought was that ossec would have to be set up on the host as both a server and client, but if you go to run the installer twice, it will want to delete the server's installation and remake it as an agent only.
The server does all the things an agent does, and on top of that it centralizes log collection and processing. You don't need to install OSSEC as server and agent on your server, just as server.