I have used PuTTy.exe for an SSH client. But putty.exe is not working for a 64 bit Windows OS. It works perfectly 32 bit Win OS.
Questions:
Am I making some mistakes. If so please can you help?
Is there any app which works on both 32 and 64 machine for win os?
Is there any cmd commands to connect ssh?
Info:
Putty.exe ver 0.63.10125.0.
Run as administrator used no use.
firewall disabled no use.
putty.exe runs on a separate drive no use.
Error:
Network error: Permission denied
Oh I found the solution for this problem.
Its due to anti virus (ex: norton).
Anti virus blocks all the network permissions.
So I have disabled all smart firewall and browser protection from anti virus.
it worked fine.
Please disable all third party firewalls too then it will work. It is not 32 and 64 bit issue I think so.
It's usually a firewall problem, especially with third party firewalls, in my case TinyWall for Windows. Simply allow the program access.
I have McAfee Endpoint Security and I had the same problem. Whenever I try to connect with putty I get "permission denied". In this case, I opened McAfee Endpoint Security, went to "Firewall". In "Firewall" I went to "RULES" and pressed "Add Rule", wrote the rule name and went to the bottom to "Executables". In "Executables" I pressed "Add", then "Browse", and added PUTTY executable. That solved this problem for me.
Just in case someone comes across the same problem:
At some point I started to receive the following errors when trying to run port forwarding
Event Log: Local port 2001 SOCKS dynamic forwarding failed: Network error: Permission denied
After struggling with that for a while, installed Bitwise SSH where the error would appear as:
Failed to enable SOCKS/HTTP proxy forwarding on 127.0.0.1:2001: Address is already in use; bind() in ListeningSocket::StartListening() failed: Windows error 10013: An attempt was made to access a socket in a way forbidden by its access permissions.
So it was clear that the port is in use - although that didn't show up in CurrPorts. So I resolved that by changing the port number
Related
Got this legacy Avocent DSR2035 KVM over IP. Works! Anyone knows how I edit the TCPIP setting on this machine? I have access to the console, it works, but there is no IP settings in any of the menu!
It took some time to figure this out. I had to upgrade firmware first and that was done through the setup port in the back and using a special cable that I built. After the fw update, there were network settings in the standard interface.
I have installed odoo 9 on a windows 7 machine..
All working well when i try to access like localhost:8069 or 192.168.1.11:8069
But the same dosnt work when i try to access from locally connected computers.. I am trying to access odoo from computers connected through lan..
trying to access 192.168.1.11:8069
However If I try to access Xampp Server using the ip it works well..
when I ping 192.168.1.11:8069 from any network computers it shows 'unknown host'
I am relatively new to this kind of network config thing.. Hope if anyone had similar issue and have sorted it out??
PS. Same thing happens when I install odoo on an Ubuntu 14.04 based computer..
Looking Forward to a solution.
Thanks in Advance.
VJ
There is a number of reasons that can cause this. What you are describing is a network issue and not a odoo issue. You cannot ping xxx.xxx.xxx.xxx:port number. I would start with some of the obvious tests:
Disable the firewall and anti-virus
If it is the firewall, set it up to open port 8069 and make sure that the firewall allows connections from other computers.
I have installed windows phone 8 SDK and tried running a simple app which embeds a WebBrowser on a page. When I try to run the app in emulator the emulator does not get internet connection. It displays an error message saying "You don't have permission to modify internal Hyper-V network adapter settings required to run the emulator". Im sure my login has admin permissions. My machine is 64bit, hyper v is enabled and Hyper v manager is running, hardware virtualization is enabled in the BIOS settings, DHCP is enabled and its connected to a wired network. I have checked all the system requirements. What ever I do it keeps on giving the same error message. I setup everything in a different machine and tried running the app in that machine. The same error message is displayed in the that machine also. Can anyone tell me how to get it working.
DHCP is enabled and its connected to a wired network
Can you run ipconfig /all on your host machine and post it here please?
seems you have problem with your DHCP or maybe multiple DHCP and conflict.
You need to add your user account as a member of the "Hyper-V Administrators" group on the machine.
Detailed steps:
Hit Windows key + Q and search for "local users and groups". Change the search scope to "Settings". Click "Edit local users and groups".
Expand the "Groups" section. Right-click on "Hyper-V Administrators" and select "Add to group".
Add your user account.
Some connection tools on the host can have negative effects when used with the emulator; I found having cisco VPN client installed on the host prevented the emulator from finding the internet. Other VPN clients may have similar side-effects. I simply uninstalled cisco (the inbuilt windows VPN is fine for what I need) and it worked perfectly.
I've also seen problems where it won't find the internet after the host has been suspended / resumed. In that scenario, it turned out to be bad network drivers. I installed a dedicated Intel NIC (rather than the on-board NIC on the motherboard) - problem solved.
Basically, Hyper-V is a bit fussy.
try refreshing the hyper-v by unchecking and then checking it again,this worked for me.
Steps:
1.control panel>>programs>>Programs and features>>turn windows features on and off>>hyper-v
2.uncheck it and restart the pc.
3.again go to control panel an check hyper-v and restart the pc again.
the try to run the emulator,should work..
another possible reason is that you did not start vs2013 as admin
I have written an application using ALSA (snd_pcm_open, snd_pcm_readi, etc). The application works perfect locally on my machine. However, when I SSH to another machine and run it through the SSH connection, all calls to snd_pcm_open fails with a message "Device does not exist" or similar. The remote machine has a soundcard just as my local machine has.
What could be the problem here?
Thanks!
EDIT: If I run the application using the console on the remote computer (walk to the computer, login, run the application), the application runs fine.
The problem might be with /dev/snd/* access rights.
Be sure the user is in the audio group.
In my case, I had to do adduser $USER audio, disconnect and then reconnect.
Just to check for the obvious: Are the drivers for the sound card on the remote machine loaded and working correctly? Check /proc/asound/cards and see so that the card is listed.
Just to confirm...you have the application installed on the remote machine and the remote machine has otherwise working aplay etc? The remote machine must be set up so that if you were to login from the console and run the application, it would work
If this is the case then check your environment variables as sometimes they can be subtly different.
Found the reason. Turns out /dev/audio and the devices below /dev/snd/ where all owned by the user logged in on the remote computer, and readable/writable by no one else. For testing I applied chmod 777 /dev/audio /dev/snd/* and it started working.
Anyone know how I can apply a bit more generous permissions to the audio devices for the remote computer (which will last after a reboot)?
I don't know why? Whenever I install AOL desktop (9.5, 9.6, 10.0) on my computer and I'm connected to the internet using cable, every thing is ok. I can browse websites and sign in to AOL.
But whenever I connect to the internet using my wireless network at home, I can not sign in to AOL, but I can still browse the web.
My wireless network uses WPA2-Personal with AES encryption type.
I always get the AC-3000 error message whenever I want to sign into AOL. None of AOL solutions could be useful to solve this.
What do I have to do ?
You didn't mention what version of windows you are using but my suspicion would be that if you are on Windows Vista/7 then the cable connection is identified as "home" or private and that the wireless connection is identified as public and the AOL connection (which used to be on port 5190 IIRC) is getting blocked as a result.
If I am right, to change what apps have access on which network types, you can follow the instructions here:
http://www.addictivetips.com/windows-tips/how-to-stop-a-program-from-gaining-unsolicited-internet-access-in-windows-7/
Although it is about how to stop a program from accessing the internet, it works just as well the other way around ;)
You could use netstat to determine what the successful connection to AOL is on the cable set up in terms of destination and IP and then attempt a simple telnet connection to the same address/port on the wireless set up to verify if this is blocked at the network/port level or if it is blocking the application (usually referred to as ACS). If the telnet connection succeeds and does not timeout, then it is an application level restriction which you will need to fix .