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 8 years ago.
Improve this question
I think this is more a Mac networking configuration issue than anything else, but am not sure.
I have Subversion set up on my Windows Home Server machine (similar to this: http://www.hanselman.com/blog/RunningASubversionServerOffYourWindowsHomeServer.aspx). This setup has been working for me for months, using Windows clients.
Now I'm trying to add a Mac client, and it can't resolve the network name of my WHS server. If I open a terminal window on the mac, and attempt to ping or use nslookup, I get an error that it can't find the server. On the PC side, I can ping, but nslookup doesn't resolve the name, so I'm assuming that PC's ping is resolving the name as a NetBios name.
I've found a number of articles online that explain how to set up default suffixes based on Windows domains, but the Windows Home Server doesn't establish a domain by default. (It's in workgroup mode.)
Anyone have any suggestions or pointers?
The quick and easy way to get this working would be to add an entry to your host file on the MAC. You can find the file in /etc/hosts
Edit the file and add an entry at the end as follows:
<ip address> <hostname>
example:
69.59.196.211 www.stackoverflow.com
That is the way that I would go, and they mention using the host file in the article you posted. More info on editing the hostfile of different machines can be found here:
http://practice.chatserve.com/hosts.html
Related
Closed. This question is not about programming or software development. 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 8 days ago.
Improve this question
Im using windows 10.
When I connect wifi it connect and show no internet even not show the wifi icon only shows glob icon.
But I can browse internet in browser.
Im not able to use internet in many windows application like in update , my phone application ect.
I tried all method that I know like changing dns to manual or auto.
Flush dns , running trouble shooter, ipconfig /renew ect
Please help me to sort out this problem.
I guese this problem come with windows update.
I tried all method that I know like changing dns to manual or auto.
Flush dns , running trouble shooter, ipconfig /renew ect
but these all step didn't solve my problem
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 4 years ago.
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.
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.
Improve this question
I have been using OvertheWire terminal coding wargame and i have accedentally
ssh'ed the server and it said in the describtion that i there is no ssh.
this message appeared
Permanently added 'natas0.natas.labs.overthewire.org' (ECDSA) to the list of known hosts.
what should i do so im not a host and what does it mean that im a host?
A "host" in this context means server, and it's talking about the server you were connecting to, not your machine.
On your machine, there is a file called known_hosts. This contains the ssh "fingerprints" of every server that you have connected to.
The first time you connect to a new server, ssh records the fingerprint. This is important, because it means ssh can detect someone spoofing the server in the future (by warning you that you are connecting to a different server from last time). Typically, users see this warning when the server is upgraded or moved to a new datacentre, rather than when something untoward is happening.
Your message is just saying that your ssh client has recorded the server fingerprint to allow you to check that you're connecting to the same server the next time you ssh to it. My guess is the server that you connected to accepted your ssh connection, but used it to print a message saying that ssh was not available.
If you want to remove the fingerprint from your system, you can can open that file and remove the line that describes the wargame server. However, I doubt there is any risk from keeping the fingerprint.
If you want to do this this:
On a mac or a unix/linux system, the file will be in ~/.ssh/known_hosts. Open it up, remove the line that describes the wargame server, and then save the file.
On a windows machine using putty, you will need to edit the registry to remove the hosts:
Open up ‘regedit.exe’ by doing a search.
Navigate to HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys
Delete the host key for the wargame server.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 6 years ago.
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.
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.
Improve this question
I am wondering what is wrong with my windows server 2012 r2 standard, use this server to serve as file server only to replace my current windows server 2003 standard edition.
During installation, setup with ip address 192.168.103.200 and everything ok, after some adjustment and configuration, we decide to take the server to production and change the ip address to the old ip address and power off the old server, which the ip address is 192.168.2.2, but after change the ip address, the server is not able to connect to other computers and vice versa. Try to change the ip address to 192.168.2.3 and everything is working.
Anyone know what could the cause for this issue?
I think the source this problem there is network level. Try to ping itself. Make on server ping to 192.168.2.2. If no then this is problem with driver's NIC. But if yes... Then check your network switch or router. There are maybe any settings for MAC address and this IP address(any filter rules your firewall). I'm almost sure this problem is in port access settings in your network equipment.
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 8 years ago.
Improve this question
I just setup remote desktop to my Windows server 2012 R2. Thi works great from LAN. How can I setup remote desktop from outside of the LAN. I have tried NAT like this:
192.168.1.200 = windows server's IP
192.168.1.200:80 -->> my_public_IP:10200
when I want connect to it like this, it doesn't work. Maybe other local port..?
Windows vista onwards provides secure RDP connectivity over IPv6 without port forwarding configuration on NAT. This feature is called WICN & it gives a unique name to your computer using which you can directly RDP to the machine. Please check the below link to enable & use it:
http://technet.microsoft.com/en-us/library/bb727045.aspx
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
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.
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.
Improve this question
I am running a trial of Windows Azure and setup a simple Windows Virtual Machine. However, I do not seem to be able to use the Windows Remote Desktop connection to remote into the machine. What am I doing wrong? At first sight it does not seem to like my userID and password. But then I also cannot ping the VM address. I do not want to go through VS or any other tool, I like to do a simple remote desktop connection through the Windows RMD tool.
Can you check that port 3389 is open in your VM? This port is normally used by remote desktop? You can check this from Virtual machine->Endpoint section within new azure preview portal. if there is no port defined, you will have to create new one.
It could be that the port is blocked, Azure VMs default to port 52137, in your endpoint settings alter this to the regular port 3389 - this worked for me.
Freddy, would u please confirm first if your Windows Azure Virtual Machine is running or not and this you can confirm by looking at Preview Portal. I have seen some cases when the VM does not start first time and you would need to restart it first time.
So if VM is not running then please start it from the portal directly or even if it shows "Running" start please restart it again.
There are a few troubleshooting steps described below so please follow them:
http://social.msdn.microsoft.com/Forums/en-US/WAVirtualMachinesforWindows/thread/9c88a364-c3eb-41aa-a6b0-3ceae00491c2
If none of the above steps resolve your problem go ahead and report this problem to same forum and you will have direct assistance from Windows Azure Virtual Machine team.
RDP to a new VM with the RDP "endpoint" setup does not work by default for security reasons.
You need to get the RDP certificate or the .RDP file from azure.
click on a running VM and click "Connect" in the control panel at the bottom, this will download the .RDP file that contains the certificate, enter user name and password and away you go.