Networking Forums

Networking Forums > Computer Networking > Windows Networking > Private network range routing

Reply
Thread Tools Display Modes

Private network range routing

 
 
Dalibor Krleza
Guest
Posts: n/a

 
      09-17-2004, 01:50 PM
Hi!

My PC box with WinXP-SP1 on LAN has IP 193.0.0.11.
There is a router to 10.0.0.0 network and his IP is 193.0.0.1
On my PC exists route to 10.0.0.0 over 193.0.0.1

Ping,telnet,anything to 10.0.0.100 does not work. Why?

When I change private network 10.0.0.0 to 11.0.0.0
everything works fine.

Please HELP.




 
Reply With Quote
 
 
 
 
Miha Pihler
Guest
Posts: n/a

 
      09-17-2004, 02:00 PM
Hi Dalibor,

The only private address in your post is 10.0.0.0. 193.0.0.0 and 11.0.0.0
are not in private IP range.

In RFC 1918 these IPs are defined as private:

10.0.0.0/8
172.16.0.0/12
192.168.0.0/16

Can you explain a bit more what you have and what you need to do.

Mike

"Dalibor Krleza" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> Hi!
>
> My PC box with WinXP-SP1 on LAN has IP 193.0.0.11.
> There is a router to 10.0.0.0 network and his IP is 193.0.0.1
> On my PC exists route to 10.0.0.0 over 193.0.0.1
>
> Ping,telnet,anything to 10.0.0.100 does not work. Why?
>
> When I change private network 10.0.0.0 to 11.0.0.0
> everything works fine.
>
> Please HELP.
>
>
>
>



 
Reply With Quote
 
Dalibor Krleza
Guest
Posts: n/a

 
      09-17-2004, 03:08 PM
I thought this is the problem, but I wasn't sure.

I don't see any reason why Windows OS shoudn't contact
default gateway stated in routing table. All other operating
systems does.

I'll define NAT on my router.

Bye and thanks!

 
Reply With Quote
 
Phillip Windell
Guest
Posts: n/a

 
      09-17-2004, 04:50 PM
"Dalibor Krleza" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> I don't see any reason why Windows OS shoudn't contact
> default gateway stated in routing table. All other operating
> systems does.


Windows does use the Default Gateway the same way every other OS does. That
isn't your problem.


> I'll define NAT on my router.


Just because they are not all RFC Private addresses does not mean you need
NAT. If these turely are LAN adresses then you could route between them all
you wanted if your oen router was configured properly. However you should
never run Non-RFC Private addresses on a LAN to begin with, then you would
never run into this.

But I am just "shooting blind" here, because you really haven't given enough
information about the system to make any difinitive statements.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Dalibor Krleza" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> I thought this is the problem, but I wasn't sure.
>
> I don't see any reason why Windows OS shoudn't contact
> default gateway stated in routing table. All other operating
> systems does.
>
> I'll define NAT on my router.
>
> Bye and thanks!
>



 
Reply With Quote
 
=?iso-8859-2?q?Dalibor_Krle=BEa?=
Guest
Posts: n/a

 
      09-17-2004, 07:17 PM
> Windows does use the Default Gateway the same way every other OS does.
> That isn't your problem.


Nop, this works on Unix/Linux. From all other machines I can
access customer's private network, just from WinXP this is not
possible.

> Just because they are not all RFC Private addresses does not mean you
> need NAT. If these turely are LAN adresses then you could route between
> them all you wanted if your oen router was configured properly. However
> you should never run Non-RFC Private addresses on a LAN to begin with,
> then you would never run into this.
>
> But I am just "shooting blind" here, because you really haven't given
> enough information about the system to make any difinitive statements.


I can't tell customer which IP range they should use. We have
link to our customer and router on our side which has IP address I
mentioned before. I use this router as gateway to customer's
private network. No Network Address Translation. Now, let's say
I have server on the other side which has IP address 10.0.0.50!

I'm setting in routing table of my WinXP machine default gateway
as 193.0.0.1 (local IP address of my router)! Now I'm trying to
ping other's side server with 10.0.0.50 (I was using sniffer on
my router to see incoming TCP/IP packets). Router doesn't
receive a single packet from WinXP machine. This looks like
WinXP machine doesn't send TCP/IP packets to router at all.

On the other hand, when trying to ping something like 11.0.0.50,
router normally receives packets from WinXP machine.

I was trying to accomplish same thing with Unix/Linux machines.
Everything works great.
 
Reply With Quote
 
Phillip Windell
Guest
Posts: n/a

 
      09-17-2004, 08:09 PM
"Dalibor Krleza" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> I'm setting in routing table of my WinXP machine default gateway
> as 193.0.0.1 (local IP address of my router)! Now I'm trying to
> ping other's side server with 10.0.0.50 (I was using sniffer on
> my router to see incoming TCP/IP packets). Router doesn't
> receive a single packet from WinXP machine. This looks like
> WinXP machine doesn't send TCP/IP packets to router at all.


What is the IP# of the XP machine?

> I was trying to accomplish same thing with Unix/Linux machines.
> Everything works great.


There is more to this than what you are telling me.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


 
Reply With Quote
 
=?iso-8859-2?q?Dalibor_Krle=BEa?=
Guest
Posts: n/a

 
      09-17-2004, 11:43 PM
>> I'm setting in routing table of my WinXP machine default gateway
>> as 193.0.0.1 (local IP address of my router)! Now I'm trying to
>> ping other's side server with 10.0.0.50 (I was using sniffer on
>> my router to see incoming TCP/IP packets). Router doesn't
>> receive a single packet from WinXP machine. This looks like
>> WinXP machine doesn't send TCP/IP packets to router at all.

>
> What is the IP# of the XP machine?


193.0.0.11

>> I was trying to accomplish same thing with Unix/Linux machines.
>> Everything works great.

>
> There is more to this than what you are telling me.


I swear there is nothing more than this!!!
We all were quite surprised. I have spent 2 whole days to figure
this out (within other work I have to do). Nothing works!

Router: RH9 machine with ISDN link to 10.0.0.* subnet.
Sniffer: snort
Clients: RH9, AIX, Digital Unix, WinXP ... everything works
except WinXP!

Hear this: After I succeded to connect 10.0.0.50 (telnet) from
RedHat Linux 9.0, I tried to use WinXP within VMware Workstation
4.5.2 on RH9. Bridged network adapter. This combination worked
flawless. Totally strange!!!

Why same thing won't work with WinXP machine???
 
Reply With Quote
 
Miha Pihler
Guest
Posts: n/a

 
      09-18-2004, 08:11 AM
> I can't tell customer which IP range they should use.

I guess you can't but you should advise them on correct network setup.

> I'm setting in routing table of my WinXP machine default gateway
> as 193.0.0.1 (local IP address of my router)!


You mentioned that your Windows XP have IP 193.0.0.11.

After you ping the gateway from your Windows XP run this on Windows XP.

ARP -a

Do you get the ARP table that includes ARP for 193.0.0.1.

Does Windows XP have same subnet mask configured as the router?

Mike


 
Reply With Quote
 
Jeff Cochran
Guest
Posts: n/a

 
      09-19-2004, 04:31 AM
On Sat, 18 Sep 2004 01:43:43 +0200, Dalibor Krle¾a <(E-Mail Removed)>
wrote:

>>> I'm setting in routing table of my WinXP machine default gateway
>>> as 193.0.0.1 (local IP address of my router)! Now I'm trying to
>>> ping other's side server with 10.0.0.50 (I was using sniffer on
>>> my router to see incoming TCP/IP packets). Router doesn't
>>> receive a single packet from WinXP machine. This looks like
>>> WinXP machine doesn't send TCP/IP packets to router at all.

>>
>> What is the IP# of the XP machine?

>
>193.0.0.11
>
>>> I was trying to accomplish same thing with Unix/Linux machines.
>>> Everything works great.

>>
>> There is more to this than what you are telling me.

>
>I swear there is nothing more than this!!!
>We all were quite surprised. I have spent 2 whole days to figure
>this out (within other work I have to do). Nothing works!
>
>Router: RH9 machine with ISDN link to 10.0.0.* subnet.
>Sniffer: snort
>Clients: RH9, AIX, Digital Unix, WinXP ... everything works
>except WinXP!
>
>Hear this: After I succeded to connect 10.0.0.50 (telnet) from
>RedHat Linux 9.0, I tried to use WinXP within VMware Workstation
>4.5.2 on RH9. Bridged network adapter. This combination worked
>flawless. Totally strange!!!
>
>Why same thing won't work with WinXP machine???


Because you have something configured incorrectly on the XP machine.
I'll assume you've eliminated a firewall as a possibility (XP has a
built-in firewall if you didn't realize it, may need to configure or
disable it...) Give us a printout of ipconfig /all on the XP system,
plus the IP and netmask of your router.

Jeff
 
Reply With Quote
 
Dalibor Krleza
Guest
Posts: n/a

 
      09-20-2004, 07:14 AM
Windows IP Configuration

Host Name . . . . . . . . . . . . : Dalibor
Primary Dns Suffix . . . . . . . : loc.xxx.xx
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : loc.xxx.xx

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : loc.xxx.xx
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-50-BA-C7-00-86
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 193.0.0.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 193.0.0.1
DHCP Server . . . . . . . . . . . : 193.0.0.222
DNS Servers . . . . . . . . . . . : 193.0.0.222
Lease Obtained. . . . . . . . . . : petak, 17.09.2004 13:57:45
Lease Expires . . . . . . . . . . : nedjelja, 17.10.2004 13:57:45

Firewall on WinXP machine is disabled.

Jeff, all these terms are not so much different from other OS.
Builtin firewall is default. Every serious OS comes with firewall,
so this was first thing I have checked.

I would say it's mine fault, but this happends on every WinXP
machine we have. What surprises me is fact that 11.0.0.*
subnet calls are working OK.

I have tried port mirroring on our switch. On mirrored port I have
connected another WinXP machine with sinffer. Now I have
tried to sniff TCP/IP traffic directly for machine I'm testing.
Another surprise: for 10.0.0.* subnet there was no outgoing
TCP/IP packets at all. On the other hand, for 11.0.0.* subnet
I have detected numerous outgoing TCP/IP packets.

Dalibor.

On Sun, 19 Sep 2004 04:31:34 +0000, Jeff Cochran wrote:
> Because you have something configured incorrectly on the XP machine.
> I'll assume you've eliminated a firewall as a possibility (XP has a
> built-in firewall if you didn't realize it, may need to configure or
> disable it...) Give us a printout of ipconfig /all on the XP system,
> plus the IP and netmask of your router.


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
NAT on a private network of a private network OM Windows Networking 5 04-28-2009 02:10 AM
private APN (in GSM network) bartek w Linux Networking 0 11-07-2007 03:16 PM
Private IP range not RFC. Jarryd Windows Networking 7 02-19-2005 07:43 AM
routing two private subnets? William Gill Linux Networking 5 01-28-2005 01:20 PM
Private network Geert-Jan van Leeuwen Linux Networking 6 09-23-2004 11:21 AM



1 2 3 4 5 6 7 8 9 10 11