VMware/Win10 bridged network

I have an openSuSE System with VMware installed and Windows 10 inside that. I “was” able to interface with my Linux system from the Windows 10 system back and forth UNTIL some of the latest Microsoft UpDates. I have a copy of my Virtual Machine “before” the UpDates and when I reload it the networking is fine. I tried to turn off the UpDates in Win 10 but I was ignored and they got put in again.

Have any of you experienced this -and- is there possibly a fix on our side that I haven’t found yet?? I run a LinWin system. Only because of a couple of programs, Homesite, Dream Weaver and TopStyle5. I’m old and can’t change my ways so I still use those to create and edit my Web Pages.

Thanks to all,
-Chuck

First,
I recommend you post in the Virtualization forum since this doesn’t likely appear to be a general networking problem
(Maybe this post should be moved).

When you troubleshoot any network connectivity issue whether virtualized or not,
You should run your typical commands like ip addr (on Linux) or ipconfig (on Windows), run Ping tests, and specifically for Virtualization verify your Guest Properties are set correctly.

Also,
Generally speaking,
Unless you have a need for other machines to connect to your Guest,
You should set up your Guest with NAT, not Bridging, then your Guest configured as a DHCP client will automatically work everywhere with least amount of manual configuration… especially configured to Bridging networking.
Common network troubleshooting includes things like testing using IP addressing, name resolution, verifying your assigned and configured network address is consistent with the network it’s connected to…

If you try the above and still have problems,
Post again but with some detail about your Guest network settings and your troubleshooting attempts.

Also,
Don’t know what you mean by “interface.” Do you mean viewing your Guest using a Guest graphic console? Connecting to your Guest using some app over a networking connection? Something else?

HTH,
TSU

Oh darn… it meant outside of the quotes.:shame:

From your Windows machine,
Post the results

ipconfig

From your openSUSE host
Post the following

ip addr

In your Guest directory,
The .vmx file

Also,
Although it’s not likely an issue you should also post the application you’re running (Player? Workstation? Something else?) and the version (current supported are 12 and 14).

TSU

Hi TSU2, Sorry I don’t know or remember your name, but here is the info you requested. AND I must say that it is NOT the copy that doesn’t work. I read your message AFTER I dumped the bumb one and replaced it with my UN-updated copy. I have since found some info that Microsoft themselves have produced a program that will let you be selective on UpDates:
http://www.thewindowsclub.com/block-unwanted-windows-updates-in-windows-10
and
Windows Update: FAQ - Microsoft Support

Thanks for your concern and help,
-Chuck

First,
In the Windows Update section, you can configure blocking specific updates. No script needed unless you prefer to use a script that issues the specific blocking command you want.

You might be interested that one of my Win10 machines (not virtualized) this month received a Patch Tuesday update this month(Apr 10 2018) that killed web browsers’ use of DNS. Everything else besides web browsers worked, including using IP addresses and using nslookup to query DNS servers, even populating the name cache. Even using an alternate web browser and cache (using the Tor Browser Bundle) worked. Only solution was to roll back the machine to prior to Apr 10, 2018 using VSS restore points, uninstalling the patch did not fix the problem.

Regarding this month’s MS Security patch (Patch Tuesday), there has been plenty of speculation and advice about removing or replacing the NIC drivers, but at least my personal investigation revealed the problem is a very specific part of the MS TCP/IP stack (Web browsers accessing the name cache) so would not be related to any NIC drivers. I can only speculate that maybe for some installing new NIC drivers might re-install the stack, but who knows for them… I only know what I saw on my machine.

If you suffered what I’m describing, no amount of troubleshooting would have helped.

TSU