VMware Communities
gptbr
Contributor
Contributor
Jump to solution

VMware NAT service dying

I have VMware Workstation 12.1 Pro installed on a Windows 10 64-bit host.

I created a port forwarding rule for VMnet8 (NAT network). I can confirm through netstat that the ports in LISTEN state on the host. I can confirm the guest ports are also working.

As soon as I attempt to open a connection to the forwarded port from the host, the VMware NAT service dies.

If I restart the NAT service, the ports are open again and, again, it will die once I try to connect.

Here are the relevant messages from the event viewer:

Log Name:      Application

Source:        VMware NAT Service

Date:          1/29/2016 1:56:03 PM

Event ID:      1000

Task Category: None

Level:         Information

Keywords:      Classic

User:          N/A

Description:

Service started

Log Name:      Application

Source:        VMware NAT Service

Date:          1/29/2016 1:56:03 PM

Event ID:      1000

Task Category: None

Level:         Information

Keywords:      Classic

User:          N/A

Description:

Using configuration file: C:\ProgramData\VMware\vmnetnat.conf.

IP address: 192.168.169.2

Subnet: 255.255.255.0

External IP address: 0.0.0.0

Device: vmnet8.

MAC address: 00:50:56:EB:9A:84.

Ignoring host MAC address: 00:50:56:C0:00:08.

Log Name:      System

Source:        Service Control Manager

Date:          1/29/2016 1:56:19 PM

Event ID:      7034

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Description:

The VMware NAT Service service terminated unexpectedly.  It has done this 5 time(s).

Log Name:      Application

Source:        Application Error

Date:          1/29/2016 1:56:19 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Description:

Faulting application name: vmnat.exe, version: 12.1.0.2487, time stamp: 0x565668d4

Faulting module name: vmnat.exe, version: 12.1.0.2487, time stamp: 0x565668d4

Exception code: 0xc0000005

Fault offset: 0x0000befb

Faulting process id: 0x14e4

Faulting application start time: 0x01d15aad8e6ff1a9

Faulting application path: C:\Windows\SysWOW64\vmnat.exe

Faulting module path: C:\Windows\SysWOW64\vmnat.exe

Report Id: 6b76381c-38e4-4cb7-86ee-317f57b61095

Faulting package full name:

Faulting package-relative application ID:

Log Name:      Application

Source:        Windows Error Reporting

Date:          1/29/2016 1:56:19 PM

Event ID:      1001

Task Category: None

Level:         Information

Keywords:      Classic

User:          N/A

Computer:      GTIRLONI

Description:

Fault bucket , type 0

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: vmnat.exe

P2: 12.1.0.2487

P3: 565668d4

P4: vmnat.exe

P5: 12.1.0.2487

P6: 565668d4

P7: c0000005

P8: 0000befb

P9:

P10:

Attached files:

C:\Windows\Temp\WER1C4B.tmp.appcompat.txt

C:\Windows\Temp\WER1C5C.tmp.WERInternalMetadata.xml

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_vmnat.exe_20f42c45e9411a26b8a065f72a726fbaef111e76_f3265a09_cab_13cd1c6a\memory.hdmp

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_vmnat.exe_20f42c45e9411a26b8a065f72a726fbaef111e76_f3265a09_cab_13cd1c6a\triagedump.dmp

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_vmnat.exe_20f42c45e9411a26b8a065f72a726fbaef111e76_f3265a09_cab_13cd1c6a

Analysis symbol:

Rechecking for solution: 0

Report Id: 6b76381c-38e4-4cb7-86ee-317f57b61095

Report Status: 4

Hashed bucket:

Tags (2)
1 Solution

Accepted Solutions
gptbr
Contributor
Contributor
Jump to solution

Downgrading to version 12.0.1 "fixed" the issue.

View solution in original post

2 Replies
gptbr
Contributor
Contributor
Jump to solution

Downgrading to version 12.0.1 "fixed" the issue.

kbarandy
Contributor
Contributor
Jump to solution

Got the same issue, thanks for the info.

Update: Fixed my issue too

0 Kudos