Quantcast
Channel: VMware Communities : Discussion List - VMware Fusion® (for Mac)
Viewing all articles
Browse latest Browse all 12061

Fusion 2.0.2/Win XP guest keeps dropping network connection

$
0
0

Every time this happens it kills all my active network connections -- and it is very disruptive. The drop lasts for just a few seconds. The following appears in the MacOS X system log:

 

Mar 24 21:50:09 brian kernel[0]: vmnet: bridge-en0: interface en is going DOWN

Mar 24 22:05:37 brian kernel[0]: vmnet: bridge-en0: interface en is coming UP

Mar 24 22:05:37 brian kernel[0]: vmnet: VMNetDisconnect called for port 0x14d23e00

Mar 24 22:05:37 brian kernel[0]: vmnet: bridge-en0: filter detached

Mar 24 22:05:37 brian kernel[0]: vmnet: bridge-en0: down

Mar 24 22:05:37 brian kernel[0]: vmnet: bridge-en0: detached

Mar 24 22:05:37 brian kernel[0]: vmnet: Freeing hub at 0x1194a000.

Mar 24 22:05:37 brian kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0xe815000.

Mar 24 22:05:37 brian kernel[0]: vmnet: VMNetConnect: returning port 0xe815000

Mar 24 22:05:37 brian kernel[0]: vmnet: Hub 0 does not exist, allocating memory.

Mar 24 22:05:37 brian kernel[0]: vmnet: Allocated hub 0xe190800 for hubNum 0.

Mar 24 22:05:37 brian kernel[0]: vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:e3:5a:dc

Mar 24 22:05:37 brian kernel[0]: vmnet: Hub 0

Mar 24 22:05:37 brian kernel[0]: vmnet:     Port 0

Mar 24 22:05:37 brian kernel[0]: vmnet: bridge-en0: got dev 0xde5a404

Mar 24 22:05:37 brian kernel[0]: vmnet: bridge-en0: up

Mar 24 22:05:37 brian kernel[0]: vmnet: bridge-en0: attached

Mar 24 22:05:37 brian kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0xe815000.

 

 

 

 

 

 

Please fix this!!

 

Message was edited by: bld

 

And the following appears in the WinXP System Events:

 

Event Type:     Warning

Event Source:     Dhcp

Event Category:     None

Event ID:     1003

Date:          3/24/2009

Time:          10:11:51 PM

User:          N/A

Computer:     BRIAN-WINXP-VM

Description:

Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address XXXXXXXXXX.  The following error occurred:

The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.


Viewing all articles
Browse latest Browse all 12061

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>