Wrong metric automatically assigned

  • Thread starter Thread starter David Balazic
  • Start date Start date
D

David Balazic

Hi!

I am having an issue on win2003server/enterprise, but I see no w2k3
group. If this is not the proper place to post, say so and sorry for
spamming.

I have a 100megabit ethernet LAN card connected to a switch. Another
PC (windows XP pro) and an ADSL modem are also connected to the
switch. I have set up a TCP/IP netowk on the LAN between the two PCs
and also have a PPPoE connection over the ADSL from the from the
win2003 PC.

The problem is that windows 2003 assigns the metric of 1 to the ADSL
connection and 20 to the local connection (LAN). The docs (
http://support.microsoft.com/default.aspx?scid=kb;en-us;299540 ) says
that the metric is auto-assigned according to the interface speed,
which is 100mbps for LAN and 1mbps, so even if Windows can not detect
the speed of the ADSL connection, it should not give it lower metric
than to the LAN, right ?

I have set "Local Are Connection" with static (manually set) IP
address and automatic metric. The ADSL PPPoE connection is set to
"Obtain an IP address automatically" and has no "Automatic metric"
setting in the dialogs.

ROUTE PRINT :


IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1c0003 ...00 20 ed 6c 61 f6 ...... Realtek RTL8139 Family PCI Fast
Ethernet NIC
0x290004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 213.250.59.9 213.250.59.9
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.120.0 255.255.255.0 192.168.120.1 192.168.120.1
20
192.168.120.1 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.120.255 255.255.255.255 192.168.120.1 192.168.120.1
20
213.250.19.90 255.255.255.255 213.250.59.9 213.250.59.9
1
213.250.59.9 255.255.255.255 127.0.0.1 127.0.0.1
50
213.250.59.255 255.255.255.255 213.250.59.9 213.250.59.9
50
224.0.0.0 240.0.0.0 192.168.120.1 192.168.120.1
20
224.0.0.0 240.0.0.0 213.250.59.9 213.250.59.9
1
255.255.255.255 255.255.255.255 192.168.120.1 192.168.120.1
1
Default Gateway: 213.250.59.9
===========================================================================
Persistent Routes:
None

ipconfig/all :


Windows IP Configuration

Host Name . . . . . . . . . . . . : slave8
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : steinovia.test

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet
NIC
Physical Address. . . . . . . . . : 00-20-ED-6C-61-F6
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.120.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.120.1

PPP adapter SiOL:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 213.250.59.9
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 213.250.59.9
DNS Servers . . . . . . . . . . . : 193.189.160.11
193.189.160.12
NetBIOS over Tcpip. . . . . . . . : Disabled

The real problem this causes is, that there are two routes for
224.0.0.0 when I connect to ADSL and the ADSL one gets priority. So if
I am not connected to ADSL and start a multicast transmission ( by
running "rat-3.0.35 230.1.2.3/7890" ), the other PC can receive it,
but when I connect to ADSL, the transmission breaks up, it seems the
packets are sent to the ADSL interface and not to the local LAN. I can
fix this by deleting the extra 224.0.0.0 route ( ROUTE DELETE
224.0.0.0 ).

Is this a bug, misconfiguration or what ?
How to permanently fix it ?

Regards,
David Balazic
 
David Balazic said:
Hi!

I am having an issue on win2003server/enterprise, but I see no w2k3
group. If this is not the proper place to post, say so and sorry for
spamming.

I have a 100megabit ethernet LAN card connected to a switch. Another
PC (windows XP pro) and an ADSL modem are also connected to the
switch. I have set up a TCP/IP netowk on the LAN between the two PCs
and also have a PPPoE connection over the ADSL from the from the
win2003 PC.

The problem is that windows 2003 assigns the metric of 1 to the ADSL
connection and 20 to the local connection (LAN). The docs (
http://support.microsoft.com/default.aspx?scid=kb;en-us;299540 ) says
that the metric is auto-assigned according to the interface speed,
which is 100mbps for LAN and 1mbps, so even if Windows can not detect
the speed of the ADSL connection, it should not give it lower metric
than to the LAN, right ?

I have set "Local Are Connection" with static (manually set) IP
address and automatic metric. The ADSL PPPoE connection is set to
"Obtain an IP address automatically" and has no "Automatic metric"
setting in the dialogs.
Click to expand...

SNIPPED for brevity
The real problem this causes is, that there are two routes for
224.0.0.0 when I connect to ADSL and the ADSL one gets priority. So if
I am not connected to ADSL and start a multicast transmission ( by
running "rat-3.0.35 230.1.2.3/7890" ), the other PC can receive it,
but when I connect to ADSL, the transmission breaks up, it seems the
packets are sent to the ADSL interface and not to the local LAN. I can
fix this by deleting the extra 224.0.0.0 route ( ROUTE DELETE
224.0.0.0 ).

Is this a bug, misconfiguration or what ?
How to permanently fix it ?

Regards,
David Balazic
Click to expand...

David,

If I am not mistaken, Windows is correctly routing the broadcast. In the
above, you are specifying a session with 230.1.2.3 on port 7890, since your
routing table when NOT connected will attempt the default gateway which
would probably be 192.168.120.1 since you have none specified in your static
IP address.

When you connect through ADSL, your new default gateway is 213.250.59.9,
Windows will forward any *non local* (meaning 192.168.120.*) requests to the
default gateway 213.250.59.9.

It would be helpful to know a little more about the program you are using
and what you are attempting to accomplish, without much more information I'm
afraid I can only offer insight into what is wrong and not how to solve the
problem.

,
 
[ snip ]
David,

If I am not mistaken, Windows is correctly routing the broadcast. In the
Click to expand...

It is not a broadcast.
It is not correctly routed ( correct would be , if it reached it
destination )
above, you are specifying a session with 230.1.2.3 on port 7890, since your
routing table when NOT connected will attempt the default gateway which
would probably be 192.168.120.1 since you have none specified in your static
IP address.
Click to expand...

No, for network 224.0.0.0, it would try the specified route ( that goes
to the LAN )
When you connect through ADSL, your new default gateway is 213.250.59.9,
Windows will forward any *non local* (meaning 192.168.120.*) requests to the
default gateway 213.250.59.9.

It would be helpful to know a little more about the program you are using
and what you are attempting to accomplish, without much more information I'm
afraid I can only offer insight into what is wrong and not how to solve the
problem.
Click to expand...

The application join the specified multicast group and transmits
packets, nothing else ( of importance to this discussion), then a copy
of the same app, receives the packets on the another PC.
It is an audi conferencing tool, called RAT. See
http://www-mice.cs.ucl.ac.uk/multimedia/software/rat/

Maybe I use a bad multicast address. Going to read some multicast FAQs...

Regards,
David Balaic ( posting from another place )
 
Back
Top