odoo 9 installed on windows 7, not accessible through intranet network using ip:8069 works fine on installed system - odoo

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.

Related

Why can't my friends access my website built with Apache2?

So, I have been building this website with HTML and I decided to host it with on Apache2. It runs on an Ubuntu and me already changed the VM assigned Ip, which is 10.2.0.15, into another one. I can access it on the Mac where the VM is, but I asked my friend if he can open it, and he said it was a 404 Server not found error.
Please help!
You probably need to enable port forwarding:
https://www.howtogeek.com/122641/how-to-forward-ports-to-a-virtual-machine-and-use-it-as-a-server/
You haven't indicated what VM software you are using, but the above is for VirtualBox. VMware is a bit different. Also make sure your router is not blocking any packets or any firewall.

Cannot remote into raspberry pi via hostname

Let me start by saying that I have no experience with Linux and this is my first attempt at getting into the IoT with a raspberry pi3. My question is why can I connect via ssh to my pi when I use the ip address but not the hostname?
After getting everything set up at home, I tried to remote in via PuTTY from my laptop. (The laptop is less than 6 months old and if I need to provide the specs on it, I can. It is running windows 10 if that matters). It worked when I entered the ip address of the pi, but when I tried again with the host name (which is clearly defined in the raspberry pi configuration) it said host does not exist. I used hostname.local and still failed.
Today, I brought the whole setup to work to try a few more scenarios. From my work desktop, which is running windows 7 and not wireless, I could remote in via hostname.local. I then tried again on a different laptop running windows 7 and it worked too. Next attempt was on another new (less than 3 months old) laptop running windows 10 and it failed to remote in via the hostname.
This would tell me that there is nothing wrong with my home network or the network at work, and it also makes me think that this has nothing to do with the pi, since other computers can resolve the hostname to the ip address and successfully login. What the hell am I doing wrong or missing?
I spent 2 nights googling and browsing forums trying to find an answer for this but cant, so instead of bashing this post, please poke me for more information you think might be helpful for a solution.
EDIT I gave my computer and PI to my cousin to fix. He installed Samba, though I don't know what it does differently. After doing more research, it sounds like the problem I was having was a DNS issue. I don't know how it was resolved by downloading samba on the pi, but I can now connect via the hostname.
So if I understand correctly it would appear that there is some particular settings on that laptop preventing you from using SSH if that is the only thing you are changing? I think this is likely to be something to do with the security settings on the laptop but Windows isn't my thing sorry.

Can't access to wamp/xampp apache localhost:80 WINDOWS 10

I recently upgrade my Windows 7 to Windows 10 (9). I need to use Apache server for web development. But for some reason I can't access it via web browser.
First I tried to look in the firewall and antivirus settings. It looks fine. I've tried reinstall xampp then I tried Wamp. Nothing working. I'tried 3 web browsers Edge, Opera, Chrome. Then I tried to find if some application is blocking port 80. So I disabled Skype, IIS. Then I tried different ports 8080,9080,123. Still can't access it via browser, but ping works.
Then I disable preference of Ipv6 and I prefer IPV4 now. I've changed HOSTS file so only 127.0.0.1 localhost is uncommented.
Only problem occurs when I try run wamp my internet access became unavailible and a have to restart computer to access internet again.
Has anyone here have same problem, because according to everything I ve done it seems apache server and network settings is correct.
Maybe problem is somewhere else?
Thank you for your help.
Solved with clean Windows 10 installation.

How to configure VMware workstation for VHD

I am able to hook SharePoint 2010 VHD with vmware. The central admin comes up but port 80 dont even come up. I ran into this http://blogs.msdn.com/b/steve_fox/archive/2010/06/15/rtm-demo-vm-for-sharepoint-amp-office-2010.aspx article but I dont know to perform this in VMWare Station 8. Please suggest.
Ping localhost host gives 127.0.0.1. But I get 404 both on localhost and 127.0.01
Ping to intranet.contoso.com takes a long time and i get request could not find host ....
Binding looks good too.
I am not seeing anything in IIS log . I mean nothing specific to intranet.contoso.com.
Looks like a DNS Issue to me. Try to add intranet.contoso.com to the hosts file as:
intranet.contoso.com 127.0.0.1
If this works then it is definitely a DNS issue, check if the service is running.
Also check if you actually assigned a virtual network card to the box in VMWare.
Update: To add NIC to VM Ware you edit machine settings and add hardware, add a network card as bridged. You can then manage the network card normally inside Windows.

no internet on windows phone 8 emulator

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