No one has replied
It seemed like someone on the VMware forums had a similar issue, yet it wasn't resolved. https://communities.vmware.com/thread/574921 I can just suggest the most common solution of "reconfigure it and see if that helps".
Thanks for sharing. I hope it saves others from making a similar mistake. I know I probably would have done just what you did.