Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Serious Networking Problems

3 views
Skip to first unread message

Henrik Schmiediche

unread,
Feb 27, 2001, 3:46:11 PM2/27/01
to

Hello,
I have set up vmware on my system using bridged networking and it works
without any problems. I am now trying to install it on another machine (A
Dell OptiPlex GX110 with integrated 3COM 3c905C network controller). I
installed vmware with bridge networking and the installation seemed to go
fine but I cannot get the networking to work. When I "ping" and outside IP
address I get a "request timmed out" reply 90%+ of the time. Occasionally I
will get a reply. Any ideas what might be causing this?

Here is my setup:

****************************************************************************
*****************

Linux Host (Mandrake 7.2):
-----------------------------

ifconfig eth0

eth0 Link encap:Ethernet HWaddr 00:B0:D0:B4:E0:74
inet addr:165.91.112.81 Bcast:165.91.119.255 Mask:255.255.248.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:259071 errors:619500 dropped:0 overruns:0 frame:619500
TX packets:140654 errors:0 dropped:0 overruns:0 carrier:26
collisions:1791 txqueuelen:100
Interrupt:5 Base address:0xec00


netstat -r

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
165.91.112.0 * 255.255.248.0 U 0 0 0
eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default bloc-osr-1.net. 0.0.0.0 UG 0 0 0
eth0


****************************************************************************
******************

On the vmware Win2k client:
------------------------------

C:\>ipconfig

Windows 2000 IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 165.91.116.165
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . : 165.91.112.1

C:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 56 b7 70 51 ...... AMD PCNET Family Ethernet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 165.91.112.1 165.91.116.165 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
165.91.112.0 255.255.248.0 165.91.116.165 165.91.116.165 1
165.91.116.165 255.255.255.255 127.0.0.1 127.0.0.1 1
165.91.255.255 255.255.255.255 165.91.116.165 165.91.116.165 1
224.0.0.0 224.0.0.0 165.91.116.165 165.91.116.165 1
255.255.255.255 255.255.255.255 165.91.116.165 165.91.116.165 1
Default Gateway: 165.91.112.1
===========================================================================
Persistent Routes:
None


Bob G

unread,
Feb 27, 2001, 5:49:54 PM2/27/01
to

"Henrik Schmiediche" <hen...@stat.tamu.edu> wrote in message
news:97h8tp$he7$1...@london.vmware.com...

>
> Linux Host (Mandrake 7.2):
> -----------------------------
>
> ifconfig eth0
>
> eth0 Link encap:Ethernet HWaddr 00:B0:D0:B4:E0:74
> inet addr:165.91.112.81 Bcast:165.91.119.255
Mask:255.255.248.0
[...]

> Windows 2000 IP Configuration
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> IP Address. . . . . . . . . . . . : 165.91.116.165
> Subnet Mask . . . . . . . . . . . : 255.255.248.0
> Default Gateway . . . . . . . . . : 165.91.112.1

Your guest IP is on a different subnet than the host _AND_ the default
gateway. Where did those addresses come from?

Those jump out at me at a quick glance.

- Bob

Henrik Schmiediche

unread,
Feb 28, 2001, 11:46:18 AM2/28/01
to

Hello,
those numbers are correct. The IP range:

165.91.112-119.x are all one subnet and the subnet mask
255.255.248.0 is correct for that 2000+ IP subnet.

I am pretty sure these are correct since we have a lot of system (100's)
that are configured this way.

Sincerely,

- Henrik


"Bob G" <vmwa...@bobspc.dhs.org> wrote in message
news:97hg5n$l7q$1...@london.vmware.com...

Chuck Gladu

unread,
Feb 28, 2001, 12:27:34 PM2/28/01
to
I think he misread the mask as 255.255.255.248 rather than
255.255.248.0

I know I did.

Petr Vandrovec

unread,
Feb 28, 2001, 2:09:16 PM2/28/01
to
Henrik Schmiediche wrote:
> fine but I cannot get the networking to work. When I "ping" and outside IP
> address I get a "request timmed out" reply 90%+ of the time. Occasionally I
> will get a reply. Any ideas what might be causing this?
>
> Here is my setup:
> ifconfig eth0
>
> eth0 Link encap:Ethernet HWaddr 00:B0:D0:B4:E0:74
> inet addr:165.91.112.81 Bcast:165.91.119.255 Mask:255.255.248.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:259071 errors:619500 dropped:0 overruns:0 frame:619500
^^^^^^ ^^^^^^

Maybe problem is here. Are you sure that your workstation and switch agree
on fullduplex setting?

Also, can you ping guest from host and vice versa? And is your guest's address
really unused?
Petr

Bob G

unread,
Feb 28, 2001, 2:11:03 PM2/28/01
to

"Chuck Gladu" <wen...@eskimo.com> wrote in message
news:37dq9t4o4r99lq0le...@4ax.com...

> I think he misread the mask as 255.255.255.248 rather than
> 255.255.248.0
>
> I know I did.

And that after reading it 3 or 4 times to make sure I hadn't. I spaced it
anyhow! My brain is fried from staring at Cisco books all day.

But back to the question of where the addresses came from: Are those in fact
the same addresses that had worked earlier? You mentioned high loss when
pinging outside. How about locally? Is all well then? Might there be an
outside factor (router config) that is affecting these addresses but perhaps
not your previous set (heh - RIP or VLSM issues on the router)? Do
traceroutes to those same outside addresses yield anything? Is there loss
going to the default gateway address?

THAT's what I really meant. :)

- Bob


Henrik Schmiediche

unread,
Mar 1, 2001, 11:23:21 AM3/1/01
to

Hello,
thanks to all who responded.

To answer the questions:

Bob wrote:
------------

"But back to the question of where the addresses came from: Are those in
fact the same addresses that had worked earlier? You mentioned high loss
when pinging outside. How about locally? Is all well then? Might there be an
outside factor (router config) that is affecting these addresses but perhaps
not your previous set (heh - RIP or VLSM issues on the router)? Do
traceroutes to those same outside addresses yield anything? Is there loss
going to the default gateway address?"

Pitr Wrote:
-----------

Maybe problem is here. Are you sure that your workstation and switch agree

onfullduplex setting? lso, can you ping guest from host and vice versa? And


is your guest's address really unused?

Answers:

These are not the same addresses that work earlier - that was on another
system. I guess I could try changing the IP to earlier address to see if
that matters (I have not done this), but I have changed the client IP once
to see if that would make a difference - it did not, so I have little hope
that changing the IP again will help. By the way, I am sure the IP address
is unused in the sense that there is no reply from the client IP when it is
not running.

As for the ping loss. When I ping the client from the host and vice versa I
have no loss of packets. I only have a loss of packets when I ping from the
client to any system outside the host (server). It matters not if the system
I ping is on the same subnet or outside the subnet. There is loss to the
default gateway and all systems on the subnet. Is it possible that router
problems are a cause? Well since I have high loss regardless if I ping
inside or outside the network I do not believe this is the case. I do not
actually controll the routers, but none of my other systems has any
problems.

As for the workstation and switch agree on fullduplex setting... that I do
not know. How would I check this? This question does bring up the one major
different between the system that worked and the system that doesn't. The
system that works was on a 100mbps line while the system that does not is on
a 10mbps ethernet line. So --- maybe --- the duplex setting or ethernet
switch or hub do have something to do with this. Unfortunaetly I cannot
(trivially) move the non-working system to a 100mbps line to test this
theory, but I will if no one else has any ideas.

Thank you very much for all you responses.

- Henrik


Ralph D. Ungermann

unread,
Mar 2, 2001, 7:49:52 AM3/2/01
to
Henrik Schmiediche wrote:
>
> Hello,
> I have set up vmware on my system using bridged networking and it works
> without any problems. I am now trying to install it on another machine (A
> Dell OptiPlex GX110 with integrated 3COM 3c905C network controller). I
> installed vmware with bridge networking and the installation seemed to go
> fine but I cannot get the networking to work. When I "ping" and outside IP
> address I get a "request timmed out" reply 90%+ of the time. Occasionally I
> will get a reply. Any ideas what might be causing this?


Hi Henrik,

did you try to disable the 3Com card and install another ordinary
network adapter?

Just my 2c (after replacing my own unreliable 3Com 3c905C)

Ralph

0 new messages