The office I work in, uses Outlook Messenger for internal communication. And I want to use VirtualBox for some development purpose being in the office network.
But after installing VirtualBox the Outlook IP is somehow intercepted. I know, if I uninstall VBox, Outlook will function like before. But I don't want to uninstall VBox.
How can I resolve the conflict?
Is there a way I can temporarily shut off the VBox's IP configuration so the Outlook can work nice? In this way I can sacrifice Outlook for team communication for that niche bit of time while I would use VBox.
It's easy. Solution given by my colleage Mr. Afzal Hossain:
As of Windows 7:
Step 1: Open Network and Sharing Center:
Step 2: Change adapter settings:
Step 3: Disable the VirtualBox Host-Only Network:
And yala! Now get back to the Outlook Messenger and right click and Refresh the users, it'll work fine. :)
Bonus Tip
You can make it a Desktop Shortcut, so that you can easily Enable/Disable the connection anytime.
Props: Mr. Afzal Hossain Noman.
Related
I was following this new edx course on Big data on Apache spark. For setting up environment I was told to install virtual-box and vagrant. After installing box and vagrant I restarted my laptop. My modem was working fine, Windows was showing Ethernet connection active but when I try to open any browser and search it was reported that can't connect to internet. I tried uninstalling both box and vagrant but no use. I even restored my system to state when these both applications were not installed but still I can't access internet. What should I do? I'm using Windows 8.1
Just googled a bit and found this:
http://thomascgreen.com/tech/?p=26
Seems to be a working solution.
In any case this is how I got it working again. First go to:
Control Panel > Network and Sharing Center > Change Adapter Settings
Right click on the connection you are having a problem with. In my
case it was “Wireless Network Connection”. On this menu select
“Properties”.
Notice there is a line here that says “Virtual Box Bridged Networking
Driver”. This is Vagrant watching the connection, is my guess.
When I unchecked the box in front of “Virtual Box Bridged Networking
Driver” my internet connection started working again.
Now at this point I started using Google to find out what was going
on. I never found a solution or reason. After searching I rechecked
the box. And everything started working again.
I would also advice to disable/enable all network cards, from the "network connections" panel. (right click on the networks, open the "Network center" and then go to to "update parameters" (I don't have the exact english labels, my Windows isn't in English). It may fix the issue.
I have this code in my WinJS default.html:
<x-ms-webview src="http://localhost/"></x-ms-webview>
<x-ms-webview src="http://display/"></x-ms-webview>
<x-ms-webview src="http://192.168.1.2/"></x-ms-webview>
display is defined in the hosts file:
127.0.0.1 display
and 192.168.1.2 -- the one that is successful -- is another computer on the network.
This is in my appx.manifest:
display and localhost successfully load in IE on the desktop and metro.
My OS is Windows 8.1 Enterprise. I have also completely disabled the Windows Firewall and this has had no effect.
What else can I do?
Microsoft blocks connections to the local machine except while running from the Visual Studio debugger.[1]
There is, however, a workaround tool. Quoting from this post on an MSDN blog:
Immersive applications (and IE11 on the Desktop) run inside isolated processes known as “AppContainers.” By default, AppContainers are forbidden from sending network traffic to the local computer (loopback).
[...]
I have built a GUI tool that allows you to very easily reconfigure an AppContainer to enable loopback traffic. This tool requires Windows 8 and runs on the .NET Framework v4. When launched, the utility scans your computer’s AppContainers and displays them in a list view. Each entry has a checkbox to the left of it, indicating whether the AppContainer may send loopback traffic. You can toggle these checkboxes individually, or use the buttons at the top to set all of the checkboxes at once. Click Save Changes to commit the configuration changes you’ve made, or click Refresh to reload the current configuration settings.
The aforementioned standalone tool is available from here.
I am trying to install and run my Windows Store app on a real Surface RT device. I have installed the Remote Debugger for ARM and its running, with no authentication on 4018.
Visual Studio fails to see the device, fails to connect and deploy.
In Windows on the desktop, I cannot ping and my port-query tool says 4018 is down, the host is unreachable.
What can I do? Why didn't they just use USB like Windows Phone development?
Microsoft don't tell you this, but you need to configure some firewall rules for the device to become visible on the network. Of course, you won't find anything by searching for "firewall" from the Start screen, but it can be found as a Snap-in for MMC.
You could turn the firewall off for the Private Profile, i.e. your local, private home network, since your home router already has a firewall and the one in Windows is just there to annoy people; cause family members to call and interrupt your dinner while they struggle to get things working on their budget new Windows 8 laptops (with no touch screen), or you could set the right rules manually.
However there's an easier way, turn on the oh-so-discoverable - especially on a tablet that's not even supposed to even have a desktop - "Network discovery and file sharing" by opening Windows (file) Explorer and clicking on the Network node on the left. A bar will pop up to remind you that Windows is getting in the way and that you can click it to make stuff work again; this configures the firewall for you.
Note that turning on "Network discovery..." via the option under Control Panel > Network Sharing Blah > Instantly-forgettable Name doesn't work. No one knows why.
By now you should be able to ping you device and the port is open, just in time for your battery to have gone flat.
Important Edit
Today, its not working again and pop-up doesn't appear again so I cannot try the same trick. My port query tool says the port is not open (it was the other day).
So I tried this, but its not working for me.
# Elevated Command Prompt #
netsh advfirewall firewall add rule name="RemoteDebugger" dir=in action=allow protocol=TCP port=4018
That says 'Ok.' but the port isn't open.
So I went into MMC and added the Firewall snap-in and its enabled itself again for the Private profile.
Then I noticed that it doesn't turn off. If you flip it to Off and hit Apply, it does nothing!!
There are now two inbound rules for the Remote Debugger, the one I setup and another for the executable. Still, doesn't work.
This thread:
http://answers.microsoft.com/en-us/windows/forum/windows_rt-networking/possible-windows-firewall-bug-on-surface-rt-blocks/caa8b40c-dacc-4d19-a751-7a04f8ef00e4
There's an answer stating:
Open Control Panel -> Administrative Tools -> Windows Firewall with Advanced Security.
Click "Windows Firewall Properties" in the main frame
In each of the three tabs of Domain, Private and Public Profile:
1) Note that: If you change "Firewall state", or change "Inbound connections" to "Allow" (inbound connections that do not match a rule are allowed), it is not going to work. The change is immediately lost after you click "OK" or "Apply" to close the dialog box.
2) What you need to do is: click Protected network connections: "Customize", it will show another dialog box, in which you can deselect some network connections. In this case, you can uncheck "Wireless" and leave "Bluetooth" on.
Once you finish step 3, Action Center will pop up an alert, saying Windows Firewall is off or not using recommended settings. You can ignore this alert, or turn it off in "Change Action Center settings".
Though someone on that thread confirm it had worked, it hasn't for me.
Luke
OK, at first I thought it was a Norton 360 problem so I deleted Norton 360. The Windows firewall is no longer being controlled by it.
Windows firewall is turned off, it's a public location, printer and file sharing is turned on, discovery is on, I reloaded the default settings for the firewall, the owner is administrator which my login is set for. Didn't matter if the Windows firewall was turned on or off, I still got the error message above.
I used to have D shared but took it off. Now when I try to create the share I get the error message above.
I have another Win 7 Pro computer with the same settings as above and I can share everything just fine.
Any ideas on how I can fix this would be greatly appreciated.
I found something nice that fixed my problem...
See solution on: Firewall and sharing folders
I did what he recommend:
export firewall polices from a Windows 7 computer that does not have this problem. (Option on the right most panel of the 3 panel screen for Windows Firewall - advanced)
Copy the .wfw file you exported to your bad firewall computer.
Use the "import Policy" option in Windows Firewall to replace the firewall policy on the bad computer.
It fixed my issue. Firewall is working - so are home groups.
We just purchased new HP Z200 machines that came with Windows 7 Enterprise 64-bit on them and we have upgraded them to Service Pack 1.
When we go into Component Services and expand computers and right-click on My Computer and choose properties, the Options tab has a disabled "Enable partitions" option that we have not been able to figure out how to enable.
We do not have this issue on Windows 2008.
Any ideas?
According to: http://social.technet.microsoft.com/Forums/windows/en-US/a601d45a-10c0-4da9-a424-d35afef22161/how-to-enable-windows-7-windows-8-com-partitions-function
I'll quote in it's entirity:
According to the Product team on this behavior, starting from Windows
Vista, they have the “Enable Partitions” checkbox grayed out on client
desktops. This was an intentional change as they want the ability to
have COM+ partitions to be available only on servers and not client
desktops.
...which makes me wonder why the blazes the checkbox is there in the first place if there's never going to be a way to enabled it.