I have done several research on the subject but I still remain unanswered.
I wonder if these possible to create an ActiveDirectory server and connected it from a computer that is not under the same local network.
If these possible would you have a URL to tell me the steps or possibilities.
No answer is currently found on StackOverFlow.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I'm wondering if its possible to host a Minecraft server on my PC and have my wife connect to that server without any internet connection. We are willing to get a router/modem or switch if need be. We just can't use internet and need instructions on what to get, how to set it up, and how to use it. My hope is that it is possible to have our computers in the same room, plug our PCs into a router that has no internet service via Ethernet cables, turn on the server on my PC, my wife can type in the IP and we can play together.
Yes you can. I am running a Minecraft server on a separate Linux machine, and me and my brother connect to the Minecraft server from separate computers, all of it from our own wireless LAN and without an Internet connection.
We are using a WiFi router that is not connected to the Internet, the computer running the server is an old laptop, and then we have two additional computers, each running an instance of Minecraft, and it all works fine.
I'm not sure about using only a network switch, because you need to be connected at the IP layer, since you need to specify the internal, private IP address of the computer running the Minecraft server from the Minecraft client in order to join.
So in a nutshell, you will need to download and install the Minecraft server, install the latest Java OpenJDK, run the Minecraft server, read the eula, and last in order for this to work completely offline (that is, we want this to work without an Internet connection), you will need to go into the Minecraft server configuration file, locate the property of online-mode=true and set it to online-mode=false.
This setting basically controls whether or not players authenticate to Mojang's servers before they connect to your server, and it prevents players with cracked clients from connecting to your server, but since you will be hosting and joining from within an internal, private network anyways it does not matter. No one will be connecting to your server from the outside world if there is not a connection to the Internet anyway.
For more details about how to install and run a Minecraft server, there are many guides out there. It's actually pretty simple, if you're comfortable using a console screen and know just a little bit about IP addresses and editing a configuration file with a text editor. For me, I run the Mi ecraft server and I was able to connect to it with my brother and start playing right away, without having to mess around with the server at all.
So there you have it, I hope this helps someone.
The very definition of a server is something that provides resources over the internet:
A server is a computer program or a device that provides functionality for other programs or devices, called "clients", over the Internet.
There is a way that would work the way you intend, but without Ethernet, it runs over WiFi. Go into a world, open the Pause menu, and click Open to LAN. Then you can go to a server menu on another computer and it will show up in the LAN Worlds section. However, this will only run vanilla gameplay.
Just FYI, this question would be considered off-topic here and should be asked in the Gaming or Networking communities.
EDIT: Opening to LAN would work over ethernet too.
Old linux user here; but only recently started using Google Cloud solutions to create a few VM instances running CentOS. Works great and have been using them for a few years successfully.
I am adding some new functions and I would like to be able to get emails that normally go to root to be sent to me.
In the past, I simply added a line in /etc/aliases at the end of
root: myemail#gsuitedomain.com
This worked well as most of the boxes that I managed were inside a network where I also controlled the local mail server and could just send through it.
It appears that I need to setup some sort of relay using G-Suite?
Is that the right path?
Also, I really don't want to relay the email. I just want to send it to one of the G-Suite accounts. So, no real relaying needed.
Can someone direct me in the right direction for the easiest path to accomplish this?
Thank you for your help,
Tamer
GCP by default blocks all outbound traffic on port 25 so you have to use different one. You can read about it in more detail in the GCE documentation.
In my opinion you will have to run sendmail, postfix or anything else to send emails out but you have to configure them to some other port than 25.
We decided to move dev machines (PC's) into the cloud in the form of Amazon Workspaces. In simple terms, a provisioned workspace is very similar to a PC accessed via RDP. However, the scaffolding for the service assigns a 'unqiue' computer name to each workspace. We wanted to set a specific computer name and therefore we connected to the workspace and used the standard Windows technique of going into Properties on "This PC". Windows prompted to restart, which we did. Thereafter the workspace was unreachable from the Windows WorkSpaces client stating the status was Unhealthy. The WorkSpaces Management status was initially REBOOTING then PENDING. Finally it showed UNHEALTHY.
It is not unusual to want to change the computer name, particularly if modelling a current physical config into the cloud. However it looks like this derails / confuses the workspaces scaffolding.
Question: How to make the workspace reachable again, especially if much time investment has been made configuring it?
I shall provide the answer that solved the issue for me, which I leave for others hitting this issue and in the hope that it helps.
I found the basis of this answer in the Amazon Workspaces forum from the same question asked by JoeA in 2016. It took me a while to find - see the original post here. which I shall paraphrase following in case this precious link breaks in the future.
Amazon's answer was:
Changing the computer name on your WorkSpace will cause the PCoIP application to fail, so you won't be able to connect to it using the Amazon client.
To connect to the workspace, you can edit the security group associated with the workspace's ENI and allow TCP traffic on port 3389 so you can RDP into it.
Once you are connected to the WorkSpace, rename it back to the original name and reboot it and you should be able to connect again.
JoeA responded:
Thank you very much for your reply, there is hope! I'm a newbie with AWS and Workspaces. Can you provide more details, or point me to a document, on how to access the Workspace using RDP? I searched the forum, but no luck.
Specifically, I don't know how to "edit the security group associated with the workspace's ENI and allow TCP traffic on port 3389 so you can RDP into it" as you state. I did find under the "Directories" setting that my "Security Group" is set to "None selected". (FYI, I have only this one Workspace.) "Access to Internet" is set to "Enable", if that is a factor. Thanks.
JoeA then followed up with the solution which was, in his words:
The changes to open the port are under the EC2 console, not the Workspaces console where I was originally looking. I found the Security Group for Workspaces, and changed Inbound traffic to allow RDP (port 3389). Then also on the EC2 console, I found Network Interfaces that shows the public IP. (I first tried to RDP using the IP shown in Workspaces console properties ("WorkSpace IP"), but that must be a local IP inside that network.) RDP'ing to the public IP, I connected and put back the original machine name, restarted, and now I can connect again using the Workspaces client again.
Thanks JoeA for that good work.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
In my company's physical office, there is no domain controller setup, just a bunch of computers ranging from Windows XP to Windows 10 that are all part of the same workgroup in the same LAN. These computers can access shared folders on other computers in the network by logging with user accounts that exist on those computers. With me so far?
Problem: I've set up a VPN through the router (netgear router with openvpn client), and I can see the shared folders on "Most" computers. I'm using Windows XP Professional, and inside the VPN I can access computers that are Windows XP or newer. I'm getting a local IP address from the router's DHCP and all that seems perfect. But I'm having I'm having problems accessing Windows 2000 computers. I try to log in and receive the error "STATUS_LOGON_FAILURE". I'm typing the correct username and password, and just can't figure out why it's not working.
I'm using Wireshark to analyze the packets and can't really see anything in there that is that much different in the SMB communication between these machines, and I'm not really sure where to start. Since XP machines in the same office behind the same router can access Windows 2000 machines, but I can't through the VPN, it seems the problem might have something to do with that. Any tips on how to trouble-shoot this?
Thanks!
I found the solution. It had to do with this registry setting:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\lmcompatibilitylevel
On all machines in the office, this value was set to 0. If I set mine to 0, I can login fine. Of course, the REAL problem is that 0 seems pretty out-dated and insecure, so now I'll need to review whether all the old machines in the office can support a NTLMv2 so I can update that, but that's a different issue. So this is SOLVED.
i have a problem with local network connection. i'm writing an iphone application and i need to read/write files to a computer. Both devices connected on the same network.
if it's possible, i want to get connected computers ip list, select one of them and read/write files like pdf, doc, txt etc.. if it's not possible to do, i will write the computer ip which i want to connect. There is no problem, both of solution is OK.
But i dont know what do i do after get the computer's ip ?
i found this chat client/server on local, but i got it very complicated.
Anyone have any idea about this ?
You'll need to have a server running on the computer, which can show files and allow for files to be read and created.
Easiest is to run a webdav service on the computer, Apache provides the mod_dav module for this purpose.
The iPhone app then becomes the client. I'd suggest using neon for this purpose. It's a C library that provides listing, reading and writing files on a remote webdav server.
That's how I would do it.
1) Find the network address of the computer you want to connect to. For this you can make use of Bonjour. It's very easy to setup because Bonjour handles the resolving of address for you.
You just have to publish a service (e.g. _myprotocol._tcp) via the ´NSNetService` class which is available on iOS and OS X (Windows too)- in your case you would publish the service on your computer.
Then you search for the service with the NSNetServiceBrowser class.
When you found a service you can then resolve it. This actually gives you the network name of the other device.
2) Connect to the other device via a tcp socket. The CocoaAsyncSocket library is very good at this. This project also includes some examples. One example already provides a bonjour server and client implementation.
i found exactly what i want. The solution is here