Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
General Discussions
Switcher Hangout (Windows to Mac)
VM Fusion 3
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Nethfel" data-source="post: 999164" data-attributes="member: 89124"><p>try this:</p><p></p><p>in Fusion at this point since you're using OSX obviously to post here to help keep you from rebooting every five seconds - just remember to check this on the bootcamp side)</p><p></p><p>If in Fusion, check whether you are using Bridged mode or NAT for the network adapter settings. If you can use multiple IP's for your computer, go ahead and set Bridge mode - and make sure it's bridged to the proper ethernet adapter you are using on your Mac (nat mode is great, but I want to try to get vmware to run the bootcamp partition so it appears as a separate computer on your network instead of on an isolated network that uses your Mac acting like a router/gateway).</p><p></p><p>Once you have windows running in fusion, open a command prompt, (start - run - type in: cmd <enter></p><p>type:</p><p>ipconfig -all</p><p></p><p>Look for the Ethernet Adapter Local Area Connection, and check:</p><p></p><p>DHCP enabled</p><p>IP Address</p><p>Subnet Mask</p><p>Default GW</p><p>DNS Servers</p><p></p><p>and see what they are filled in as. If the IP address reports something like:</p><p></p><p>169.254.x.x - you have an automagically assigned private IP address (an APIPA address) which is non-routeable and probably the source of your problem.</p><p></p><p>If your ip address is 192.168.x.x or 10.x.x.x or 172.16.x.x - 172.31.x.x - then you have an appropriate private IP address - whether it's correct for your network or not may be another issue - one way to check is to open a terminal on OSX and type ifconfig - look for the entry for en0 and compare its IP/mask to what you see in windows - they should be in the same range (but different) and have the same mask. If that's ok, check to make sure your DNS servers are correct (you can compare them to the DNS settings on your Mac in your System Preferences networking pane). If that's correct, it's time to start trying to ping.</p><p></p><p>First in the command prompt that you have open in windows in bootcamp, try to ping the gateway by typing:</p><p></p><p>ping <IPADDRESSOFGATEWAY></p><p></p><p>so if your Default GW IP is: 192.168.1.1 you'd type:</p><p></p><p>ping 192.168.1.1</p><p></p><p>just replace the numbers with the gateway you have reported and see what comes back.</p><p></p><p>If you get too desperate, before re-installing bootcamp, try uninstalling vmware tools and boot into bootcamp and see if anything starts to work again.</p></blockquote><p></p>
[QUOTE="Nethfel, post: 999164, member: 89124"] try this: in Fusion at this point since you're using OSX obviously to post here to help keep you from rebooting every five seconds - just remember to check this on the bootcamp side) If in Fusion, check whether you are using Bridged mode or NAT for the network adapter settings. If you can use multiple IP's for your computer, go ahead and set Bridge mode - and make sure it's bridged to the proper ethernet adapter you are using on your Mac (nat mode is great, but I want to try to get vmware to run the bootcamp partition so it appears as a separate computer on your network instead of on an isolated network that uses your Mac acting like a router/gateway). Once you have windows running in fusion, open a command prompt, (start - run - type in: cmd <enter> type: ipconfig -all Look for the Ethernet Adapter Local Area Connection, and check: DHCP enabled IP Address Subnet Mask Default GW DNS Servers and see what they are filled in as. If the IP address reports something like: 169.254.x.x - you have an automagically assigned private IP address (an APIPA address) which is non-routeable and probably the source of your problem. If your ip address is 192.168.x.x or 10.x.x.x or 172.16.x.x - 172.31.x.x - then you have an appropriate private IP address - whether it's correct for your network or not may be another issue - one way to check is to open a terminal on OSX and type ifconfig - look for the entry for en0 and compare its IP/mask to what you see in windows - they should be in the same range (but different) and have the same mask. If that's ok, check to make sure your DNS servers are correct (you can compare them to the DNS settings on your Mac in your System Preferences networking pane). If that's correct, it's time to start trying to ping. First in the command prompt that you have open in windows in bootcamp, try to ping the gateway by typing: ping <IPADDRESSOFGATEWAY> so if your Default GW IP is: 192.168.1.1 you'd type: ping 192.168.1.1 just replace the numbers with the gateway you have reported and see what comes back. If you get too desperate, before re-installing bootcamp, try uninstalling vmware tools and boot into bootcamp and see if anything starts to work again. [/QUOTE]
Verification
Post reply
Forums
General Discussions
Switcher Hangout (Windows to Mac)
VM Fusion 3
Top