Hardware ERROR ?!?!?

[Skybuck Flying]

C:\Documents and Settings\Administrator>ping 192.168.0.61

Pinging 192.168.0.61 with 32 bytes of data:

Hardware error.
Hardware error.
Hardware error.
Hardware error.

That's supposed to be the VMware connection 1.

Computers are assigned as follows:

Local Area Network connection: 192.168.0.1
VM network connection1: 192.168.0.61
VM network connection8: 192.168.0.68

Windows 7 Guest in VM: 192.168.0.67

Netmask all: 255.255.255.0

Why can't this work ?

Also why must the internet have stupid network masks ?!?

Isn't the ip just enough... ?!?

Anyway can this configuration work like this under normal circumstances/vm
ware usage ?

Maybe something got damaged...

I remove Microsoft Point to Point Adapter from Windows 7.

Not sure if it was there before...

Maybe I should add it back to see if it helps...

I will do so now..

Bye,
Skybuck.

 

[Skybuck Flying]

I am gonna do a full reboot to see if that helps... route table seemed to
contain lots of junk by now.

Bye,
Skybuck.

 

[David Schwartz]

Also why must the internet have stupid network masks ?!?

Isn't the ip just enough... ?!?

Without a network mask, how could you tell if two IP addresses were on
the same network or not? How would you know when to use an interface
route and when to use a default route?

DS

 

[Skybuck Flying]

This simple configuration might not work... I was my last attempt during the
screwed up situation.

Now that I look at VM network editor it says the following:

VMnet1 (host only) subnet: 192.168.122.0
VMnet8 (NAT) subnet: 192.168.88.0

So I think at least the computer inside vmware... in this case windows
7/guest must be 192.168.122.7 or so ?

Not sure what the vm connection in windows needs to be... maybe also
192.168.122.1

So gonna try that now...

Bye,
Skybuck.

 

[Skybuck Flying]

This simple configuration might not work... I was my last attempt during
the screwed up situation.

Now that I look at VM network editor it says the following:

VMnet1 (host only) subnet: 192.168.122.0
VMnet8 (NAT) subnet: 192.168.88.0

So I think at least the computer inside vmware... in this case windows
7/guest must be 192.168.122.7 or so ?

Not sure what the vm connection in windows needs to be... maybe also
192.168.122.1

So gonna try that now...

And subnet mask 255.255.0.0

Bye,
Skybuck.

 

[Skybuck Flying]

Hmm I noticed I made a type in windows it was 158 instead of 168 not sure if
that mattered maybe not...

I probably tried different things before that typo anyway

Bye,
Skybuck.

 

[Skybuck Flying]

And subnet mask 255.255.0.0

Hmm this configuration does not work...

Bye,
Skybuck.

 

[Skybuck Flying]

Now it's totally kaputt huh ?!?

Wacky.

Bye,
Skybuck.

 

[Skybuck Flying]

Ok made another stupid typo 192.169 instead of 192.168.

Now xp vm connection is 192.168.0.201
Now vm windows 7 connection is 192.168.0.202

xp cannot ping windows 7 ?

But vice versa it does work ?

Weird.

Bye,
Skybuck.

 

[Skybuck Flying]

Hmm it just occured to me....

Maybe windows 7 firewall is blocking ping packets/icmp ?!?

Bye,
Skybuck.

 

[Skybuck Flying]

Yup that was the problem... ****ing firewalls !?!

(Firewall for windows 7 turned off)

Bye,
Skybuck.

 

[Skybuck Flying]

There is still one little thing irritating me...

The VM tray icons have an exclamation mark... complaining about "unknown
network"

and network properties says: "no network access" ?

Also something asked me if I wanted to create some kind of network or
something...

I didn't have time to look into it at that moment and I simplied pissed it
off
but entering some stupid network name without reading wtf I was doing...

So I am not sure if that has anything to do with it...

If so... how to remove stupid network groups or whatever ???

^ Weird ^.

It's not a big deal.. it's just a bit weird.

Bye,
Skybuck.