Network problem

[JimmyW]

Well, I just unistalled VMware, and I can get out. You might have seen this in the files I attached with my last post, but, after the uninstall, this is the ipconfig frm the particular NIC:

Connection-specific DNS Suffix . : domain.actdsltmp

IP Address. . . . . . . . . . . . : 192.168.0.3

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IP Address. . . . . . . . . . . . : fe80::2e0:81ff:fe54:c788%4

Default Gateway . . . . . . . . . : 192.168.0.1

What's the second IP address that's two-byte hex strngs? It's not my or the gateway's IP. Thanks!

[Mr Snrub]

Thanks. I'm not sure what you mean by "multi-homed." I attached files with outputs from the commands. NETWORK 2 is the one with the issue, but the issue will exist with either NIC. Perhaps there's a conflict with VMware.

You don't know what multi-homed means, but you have installed VMWare on this machine and the host is trying to obtain DHCP settings from one of its guests?

Okay, uninstall IPv6 as you will not need it.

You can't route anywhere as you don't have a default gateway on the network adapter, and did you join the host to a domain running on a server in a guest OS or something? (DNS suffix is "domain.actdsltmp")

Ethernet adapter NETWORK 2:

Connection-specific DNS Suffix . : domain.actdsltmp

Description . . . . . . . . . . . : NVIDIA nForce Networking Controller #2

Physical Address. . . . . . . . . : 00-E0-81-54-C7-88

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.3

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IP Address. . . . . . . . . . . . : fe80::2e0:81ff:fe54:c788%6

Default Gateway . . . . . . . . . :

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

205.171.3.65

fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

Lease Obtained. . . . . . . . . . : Monday, February 13, 2006 9:49:04 AM

Lease Expires . . . . . . . . . . : Tuesday, February 14, 2006 9:49:04 AM

Your VMWare (possibly NAT?) adapter appears to have a conflicting subnet with your physical network.

192.168.0.1 must be your router, connected to the LAN that "NETWORK 2" is connect to, but when VMWare is installed it is screwing up the configuration by putting the IP of your router on the virtual interface.

Multi-homed means the machine has multiple network interfaces (physical or virtual).

Your machine is multi-homed with 2 physical network adapters (192.168.0.0/24 and 10.10.10.0/24) and with 2 virtual network adapters provided by VMWare (192.168.0.0/24 and 192.168.40.1).

The strange-looking IP addresses are IPv6 which you will not need.

A gateway is the device which network traffic is sent to when the destination is not on your local networks.

Having no default gateway means you can't route.

Having more than one gateway can cause routing problems or delays as the computer will just the use first it "sees" even if it isn't right (unless you set up static routes).

Leave VMWare out of the equation until you understand more about networks & IP routing, then reconfigure "VMware Virtual Ethernet Adapter for VMnet8" so it doesn't try to use the same subnet as your physical network adapter.

[JimmyW]

Thanks very much for your patience and help. "Multi-homed" is not a term that I've heard for multiple adapters, despite my advanced years and at least modest talent. Sorry. I will admit to being foolish in not observing that VMnet8 had already grabbed the default gateway as its IP address. I skipped right by that, as there were no VMs running, and I didn't stop to think that the virtual adapter would have grabbed the gateway's address as its IP. For one, it shouldn't have the same IP for the adapter and gateway. As I mentioned, this came about suddenly, after VMware has been in substantial use.

After reinstalling VMware, all is well, as its adapters assumed IPs elsewhere in the 192.168 range. Perhaps what happened is that, when I ran a VM with NAT or changed the IP within the VM to use DHCP, it assumed my gateway's IP as its own, and I neglected to reset the address. When I run a VM with networking, it's generally bridged to the host's physical adapter. As you observed, TCP/IP is not my strong point, but I do know enough to (usually) get by. For the times when I don't, I'm grateful to folks like you who can point out the obvious. Thanks again.