Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Routing network return (Routing & Remote Access)

Status
Not open for further replies.

MichaelLaursen

IS-IT--Management
May 25, 2005
16
DK
Hi There!

I have a Windows 2003 server with 2 NIC’s installed on one Subnet, and another subnet with a XP client.
I have with Routing & Remote Access made a connection with NIC2 on my Server 2003, so I can connect with it to the other subnet, that also provides me access to the Internet. That works and I can from my Server 2003 ping my XP client on the other subnet. But I can't ping my server from my XP client! Why not? How can I make some king at routing return so my XP will get access to the subnet where my Server 2003 is running?

Thanks
 
can your XP ping other pcs on the other subnet?
what does it have in its routing table?
can it access internet?

can other pcs on the same subnet ping the server?

Aftertaf
________
Regain control of your PC, at
 
Hi!

My XP can ping other computers on it's subnet. Og also access the internet.
Other computeres on the subnet with the XP can't ping the server.
Clients on the servers subnet can ping the server and computers on the other subnet.

You wrote:
What does it have in its routing table?

Where do I find this?

Thanks!
 
Ohh! :) I'll get back to you later today. Unfortunately i'm at work now! :)
 
you DO have a routing problem then.

the router linking the 2 subnets is your RRAS server with 2 NICs;

Can you list the subnets and IP addresses for each NIC?

you have probably got an error in your config in one of the NIcs.
paste us the Ipconfig /all for both...



Aftertaf
________
Regain control of your PC, at
 
Server:
NIC1 : 192.168.2.120 (255.255.255.0)
NIC2 : 192.168.1.22 (255.255.255.0)

XP:
NIC1 : 192.168.1.20 (255.255.255.0)


I think I need to make a route from (XP) 192.168.1.20 to (SERVER) 192.168.1.22

BUT HOW???

Here is the information you asked for.

XP : IPconfig /ALL
Windows IP Configuration

Host Name . . . . . . . . . . . . : knold
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Netw
ion
Physical Address. . . . . . . . . : 00-0B-DB-72-BB-88
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 194.239.134.83
193.162.153.164
Lease Obtained. . . . . . . . . . : 26. maj 2005 15:46:38
Lease Expires . . . . . . . . . . : 29. maj 2005 15:46:38

**********************XP = Router Print***********************************
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 56 c0 00 08 ...... VMware Virtual Ethernet Adapter for VMnet8
0x3 ...00 50 56 c0 00 01 ...... VMware Virtual Ethernet Adapter for VMnet1
0x4 ...00 0b db 72 bb 88 ...... Intel(R) PRO/1000 MT Network Connection - Packet
Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.20 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.20 192.168.1.20 20
192.168.1.20 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.20 192.168.1.20 20
192.168.2.0 255.255.255.0 192.168.2.1 192.168.2.1 20
192.168.2.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.2.255 255.255.255.255 192.168.2.1 192.168.2.1 20
192.168.5.0 255.255.255.0 192.168.5.1 192.168.5.1 20
192.168.5.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.5.255 255.255.255.255 192.168.5.1 192.168.5.1 20
219.95.11.41 255.255.255.255 192.168.1.1 192.168.1.20 20
224.0.0.0 240.0.0.0 192.168.1.20 192.168.1.20 20
224.0.0.0 240.0.0.0 192.168.2.1 192.168.2.1 20
224.0.0.0 240.0.0.0 192.168.5.1 192.168.5.1 20
255.255.255.255 255.255.255.255 192.168.1.20 192.168.1.20 1
255.255.255.255 255.255.255.255 192.168.2.1 192.168.2.1 1
255.255.255.255 255.255.255.255 192.168.5.1 192.168.5.1 1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
None

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

SERVER = Config /ALL

Windows IP Configuration

Host Name . . . . . . . . . . . . : server
Primary Dns Suffix . . . . . . . : M.AD
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : M.AD

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-BA-01-38
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.120
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.2.120

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-BA-01-42
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.22
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 194.239.134.83
193.162.153.164
Lease Obtained. . . . . . . . . . : 26. maj 2005 15:53:31
Lease Expires . . . . . . . . . . : 29. maj 2005 15:53:31

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


SERVER = Route Print

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c 29 ba 01 38 ...... VMware Accelerated AMD PCNet Adapter
0x10004 ...00 0c 29 ba 01 42 ...... VMware Accelerated AMD PCNet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.22 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.22 192.168.1.22 10
192.168.1.22 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.1.255 255.255.255.255 192.168.1.22 192.168.1.22 10
192.168.2.0 255.255.255.0 192.168.2.120 192.168.2.120 1
192.168.2.120 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.2.255 255.255.255.255 192.168.2.120 192.168.2.120 1
224.0.0.0 240.0.0.0 192.168.1.22 192.168.1.22 10
224.0.0.0 240.0.0.0 192.168.2.120 192.168.2.120 1
255.255.255.255 255.255.255.255 192.168.1.22 192.168.1.22 1
255.255.255.255 255.255.255.255 192.168.2.120 192.168.2.120 1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
None
 
on the XP machine, you are running VMWare, yeah?

what are the IP addresses for the VMNets 1 & 8?
guessing 192.168.5.1 - 255.255.255.0
192.168.2.1 - 255.255.255.0

is this right?
you shouldnt have your XP machine with the same net address, even a virtual address, as the 192.168.2/24 net to which your server is connected...

It thinks it can contact it locally.
if you run a tracert or pathping to the 192.168.2.120 server IP, i bet it doesn't find it, this right?

The default gateway, 192.168.1.1 is your DHCP server. Why are you using this as the default gateway? Does it use NAT to give you internet access?
________
Network Destination Netmask Gateway Interface
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.22
this line in your route table seems to indicate so. Is this how it should be?

you should have a local dns server too, and have your clients querying it for resolution, instead of giving them your ISPs dns servers directly.

you should set the 192.168.1.22 address as the default gateway, and if your net access does pass thru your dhcp server, then add a route (if not already present) to your RRAS server to point to the DHCP/NAT server:
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.22

Your server should reference itself for dns, and have the ISP as forwarders...
And it seems it is on 2 LANs with VMWare. the problem is surely here!
to make it properly multihomed, it needs 2 real NICs, otherwise your problem is with your vmware virtual LAN setup...
hope this makes sense...

Aftertaf
________
Regain control of your PC, at
 
Thanks a lot!

I could not delay the project anymore, so I made some network changes just to make it work, but when I but an hour or two, I will check out what you wrote. I spend 5 hours last night trying to fix it. I think the problem could rely on the physical router, but I'm not sure.

Again thanks
 
your routing tables on the XP box dont seem logical.
is it your server that is the router between the 192.168.1 & 192.168.2 subnets? or a physical router?

and a multihomed pc cant communicate with other pcs on the same net address subnet if there is a router between them, it has to send its packets to the default gateway(=router) for it to send them on.

better delaying a project than reaching launch time to meet deadlines with things not yet working correctly, saves you headaches later on...
;)

Aftertaf
________
Regain control of your PC, at
 
:)
Well it's actually a home project, I just needed it to work, so I could connect my Exchange to the Internet <->
But it only worked the one way, so I disabled the Server 2003 DHCP and changed the network conf. So now it's not an issue anymore. But I’m not giving up, I just need to learn Exchange before anything else.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top