Jump to content

Cannot PING Windows 2008 RRAS server IP

Guest N D

By Guest N D
in Windows 2003 Server

 Share

Recommended Posts

Guest N D

Guest N D

Posted
Posted

I hope somebody in here can assist as I am tearing my hair out.

 

We have three servers A B and C. All are running Windows Server 2003.

We use RRAS to setup demand dial between the servers to enable

"private" communication between them as opposed to the Internet facing

network traffic on the single network card in each. Each server has

it's own private (192.168) subnet on the demand dial interface.

 

This has worked fine for a couple of years but now we are going to

introduce a fourth server (Lets call it D) running Windows server

2008.

 

I have added the server role to get RRAS installed and configured.

 

I have added a Demand Dial link on the server to connect it to server

A above.

 

Both servers dial each other successfully. Without problem.

 

I have enabled the Windows Firewall rules to allow ICMP

 

As a "Belt and Braces" approach I even added two extra "Allow" rules

to allow IPV4 & IPV6 ICMP packets of type echo to pass through the

firewall.

 

There are no Filters on any of the interfaces in RRAS on either server

 

Server D (Win2008) can ping Server A. It can ping either the 192.168

private address or of course the external address.

 

Server A (Win2003) cannot ping Server D on its internal private

192.168 address but it can ping its external internet address (So I

know the firewall can't be the reason wouldn't you agree?)

 

After a day of this I thought maybe there was something wrong with

some obscure setting in Server A. So I created another demand dial

link between Server C (Win2003) and Server D (Win2008). Exactly the

same behaviour without exception.

 

Next, disable / delete the demand dial between Server A and Server D

and instead setup a simple VPN dialup connection to Serevr D from

Server A. BINGO! It can ping. So how come if I have a demand dial it

cannot ping the remote server but if I use a normal VPN dialup

connection it can?!?!

 

There must be something else blocking packets but I cannot for the

life of me work out what it is. There is no anti-virus on either box

to worry about so completely stumped now what to do. If I can't even

ping then I definitely haven't got a hope of getting network shares

etc going.

 

I wondered if there was perhaps a hotfix or something I might be

missing for either Win2003 or Win 2008?

 

BTW Win2003 on all the servers are up to SP2.

 

In case it's of any help I have quoted below the routing table from

Server A (Windows 2003). Server A is on subnect 192.168.166.0 (Server

is 192.168.166.1) and Server D is on 192.168.173.0 (Server is

192.168.173.1). The other 192.168 subjects listed are all for comms to

the other 2 servers B and C.

 

Many thanks in advance for any help you can give. It's much

appreciated.

 

Regards

Nick

 

 

IPv4 Route Table

===========================================================================

Interface List

0x1 ........................... MS TCP Loopback interface

0x10002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface

0x10003 ...00 0d 61 72 29 35 ...... Realtek RTL8139/810X Family PCI

Fast Ethernet NIC

0x20004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface

0x30005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface

0x40006 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface

0x90007 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface

0xd0008 ...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 81.27.99.1

81.27.99.113 20

81.27.96.161 255.255.255.255 81.27.99.1

81.27.99.113 20

81.27.96.168 255.255.255.255 81.27.99.1

81.27.99.113 20

81.27.99.0 255.255.255.0 81.27.99.113

81.27.99.113 20

81.27.99.113 255.255.255.255 127.0.0.1

127.0.0.1 20

81.27.106.26 255.255.255.255 81.27.99.1

81.27.99.113 20

81.27.106.27 255.255.255.255 81.27.99.1

81.27.99.113 20

81.255.255.255 255.255.255.255 81.27.99.113

81.27.99.113 20

127.0.0.0 255.0.0.0 127.0.0.1

127.0.0.1 1

192.168.164.0 255.255.255.0 192.168.166.2

192.168.164.2 1

192.168.164.2 255.255.255.255 127.0.0.1

127.0.0.1 50

192.168.164.255 255.255.255.255 192.168.164.2

192.168.164.2 50

192.168.165.0 255.255.255.0 192.168.166.3

192.168.165.2 1

192.168.165.2 255.255.255.255 127.0.0.1

127.0.0.1 50

192.168.165.255 255.255.255.255 192.168.165.2

192.168.165.2 50

192.168.166.1 255.255.255.255 127.0.0.1

127.0.0.1 50

192.168.166.2 255.255.255.255 192.168.164.2

192.168.164.2 1

192.168.166.3 255.255.255.255 192.168.165.2

192.168.165.2 1

192.168.166.4 255.255.255.255 192.168.173.2

192.168.173.2 1

192.168.166.5 255.255.255.255 192.168.174.2

192.168.174.2 1

192.168.173.0 255.255.255.0 192.168.166.4

192.168.173.2 1

192.168.173.2 255.255.255.255 127.0.0.1

127.0.0.1 50

192.168.173.4 255.255.255.255 127.0.0.1

127.0.0.1 50

192.168.173.255 255.255.255.255 192.168.173.2

192.168.173.2 50

192.168.173.255 255.255.255.255 192.168.173.4

192.168.173.4 50

192.168.174.0 255.255.255.0 192.168.166.5

192.168.174.2 1

192.168.174.2 255.255.255.255 127.0.0.1

127.0.0.1 50

192.168.174.255 255.255.255.255 192.168.174.2

192.168.174.2 50

224.0.0.0 240.0.0.0 81.27.99.113

81.27.99.113 20

224.0.0.0 240.0.0.0 192.168.164.2

192.168.164.2 50

224.0.0.0 240.0.0.0 192.168.165.2

192.168.165.2 50

224.0.0.0 240.0.0.0 192.168.173.2

192.168.173.2 50

224.0.0.0 240.0.0.0 192.168.173.4

192.168.173.4 50

224.0.0.0 240.0.0.0 192.168.174.2

192.168.174.2 50

255.255.255.255 255.255.255.255 81.27.99.113

81.27.99.113 1

255.255.255.255 255.255.255.255 192.168.164.2

192.168.164.2 1

255.255.255.255 255.255.255.255 192.168.165.2

192.168.165.2 1

255.255.255.255 255.255.255.255 192.168.173.2

192.168.173.2 1

255.255.255.255 255.255.255.255 192.168.173.4

192.168.173.4 1

255.255.255.255 255.255.255.255 192.168.174.2

192.168.174.2 1

Default Gateway: 81.27.99.1

===========================================================================

Persistent Routes:

None

  • Replies 7
  • Created
  • Last Reply

Popular Days

Popular Days

Guest Robert L. \(MS-MVP\)

Guest Robert L. \(MS-MVP\)

Posted
Posted

Re: Cannot PING Windows 2008 RRAS server IP

 

It may help if you can post the result of routing table and ipconfig /all on

D server. Also the result of tracert 192.168.173.x from A.

 

--

Bob Lin, MS-MVP, MCSE & CNE

Networking, Internet, Routing, VPN Troubleshooting on

http://www.ChicagoTech.net

How to Setup Windows, Network, VPN & Remote Access on

http://www.HowToNetworking.com

"N D" <nick.dyer@evaware.com> wrote in message

news:6d7a47f6-dc73-43c3-9485-7250e9cdadff@r66g2000hsg.googlegroups.com...

>I hope somebody in here can assist as I am tearing my hair out.

>

> We have three servers A B and C. All are running Windows Server 2003.

> We use RRAS to setup demand dial between the servers to enable

> "private" communication between them as opposed to the Internet facing

> network traffic on the single network card in each. Each server has

> it's own private (192.168) subnet on the demand dial interface.

>

> This has worked fine for a couple of years but now we are going to

> introduce a fourth server (Lets call it D) running Windows server

> 2008.

>

> I have added the server role to get RRAS installed and configured.

>

> I have added a Demand Dial link on the server to connect it to server

> A above.

>

> Both servers dial each other successfully. Without problem.

>

> I have enabled the Windows Firewall rules to allow ICMP

>

> As a "Belt and Braces" approach I even added two extra "Allow" rules

> to allow IPV4 & IPV6 ICMP packets of type echo to pass through the

> firewall.

>

> There are no Filters on any of the interfaces in RRAS on either server

>

> Server D (Win2008) can ping Server A. It can ping either the 192.168

> private address or of course the external address.

>

> Server A (Win2003) cannot ping Server D on its internal private

> 192.168 address but it can ping its external internet address (So I

> know the firewall can't be the reason wouldn't you agree?)

>

> After a day of this I thought maybe there was something wrong with

> some obscure setting in Server A. So I created another demand dial

> link between Server C (Win2003) and Server D (Win2008). Exactly the

> same behaviour without exception.

>

> Next, disable / delete the demand dial between Server A and Server D

> and instead setup a simple VPN dialup connection to Serevr D from

> Server A. BINGO! It can ping. So how come if I have a demand dial it

> cannot ping the remote server but if I use a normal VPN dialup

> connection it can?!?!

>

> There must be something else blocking packets but I cannot for the

> life of me work out what it is. There is no anti-virus on either box

> to worry about so completely stumped now what to do. If I can't even

> ping then I definitely haven't got a hope of getting network shares

> etc going.

>

> I wondered if there was perhaps a hotfix or something I might be

> missing for either Win2003 or Win 2008?

>

> BTW Win2003 on all the servers are up to SP2.

>

> In case it's of any help I have quoted below the routing table from

> Server A (Windows 2003). Server A is on subnect 192.168.166.0 (Server

> is 192.168.166.1) and Server D is on 192.168.173.0 (Server is

> 192.168.173.1). The other 192.168 subjects listed are all for comms to

> the other 2 servers B and C.

>

> Many thanks in advance for any help you can give. It's much

> appreciated.

>

> Regards

> Nick

>

>

> IPv4 Route Table

> ===========================================================================

> Interface List

> 0x1 ........................... MS TCP Loopback interface

> 0x10002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface

> 0x10003 ...00 0d 61 72 29 35 ...... Realtek RTL8139/810X Family PCI

> Fast Ethernet NIC

> 0x20004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface

> 0x30005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface

> 0x40006 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface

> 0x90007 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface

> 0xd0008 ...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 81.27.99.1

> 81.27.99.113 20

> 81.27.96.161 255.255.255.255 81.27.99.1

> 81.27.99.113 20

> 81.27.96.168 255.255.255.255 81.27.99.1

> 81.27.99.113 20

> 81.27.99.0 255.255.255.0 81.27.99.113

> 81.27.99.113 20

> 81.27.99.113 255.255.255.255 127.0.0.1

> 127.0.0.1 20

> 81.27.106.26 255.255.255.255 81.27.99.1

> 81.27.99.113 20

> 81.27.106.27 255.255.255.255 81.27.99.1

> 81.27.99.113 20

> 81.255.255.255 255.255.255.255 81.27.99.113

> 81.27.99.113 20

> 127.0.0.0 255.0.0.0 127.0.0.1

> 127.0.0.1 1

> 192.168.164.0 255.255.255.0 192.168.166.2

> 192.168.164.2 1

> 192.168.164.2 255.255.255.255 127.0.0.1

> 127.0.0.1 50

> 192.168.164.255 255.255.255.255 192.168.164.2

> 192.168.164.2 50

> 192.168.165.0 255.255.255.0 192.168.166.3

> 192.168.165.2 1

> 192.168.165.2 255.255.255.255 127.0.0.1

> 127.0.0.1 50

> 192.168.165.255 255.255.255.255 192.168.165.2

> 192.168.165.2 50

> 192.168.166.1 255.255.255.255 127.0.0.1

> 127.0.0.1 50

> 192.168.166.2 255.255.255.255 192.168.164.2

> 192.168.164.2 1

> 192.168.166.3 255.255.255.255 192.168.165.2

> 192.168.165.2 1

> 192.168.166.4 255.255.255.255 192.168.173.2

> 192.168.173.2 1

> 192.168.166.5 255.255.255.255 192.168.174.2

> 192.168.174.2 1

> 192.168.173.0 255.255.255.0 192.168.166.4

> 192.168.173.2 1

> 192.168.173.2 255.255.255.255 127.0.0.1

> 127.0.0.1 50

> 192.168.173.4 255.255.255.255 127.0.0.1

> 127.0.0.1 50

> 192.168.173.255 255.255.255.255 192.168.173.2

> 192.168.173.2 50

> 192.168.173.255 255.255.255.255 192.168.173.4

> 192.168.173.4 50

> 192.168.174.0 255.255.255.0 192.168.166.5

> 192.168.174.2 1

> 192.168.174.2 255.255.255.255 127.0.0.1

> 127.0.0.1 50

> 192.168.174.255 255.255.255.255 192.168.174.2

> 192.168.174.2 50

> 224.0.0.0 240.0.0.0 81.27.99.113

> 81.27.99.113 20

> 224.0.0.0 240.0.0.0 192.168.164.2

> 192.168.164.2 50

> 224.0.0.0 240.0.0.0 192.168.165.2

> 192.168.165.2 50

> 224.0.0.0 240.0.0.0 192.168.173.2

> 192.168.173.2 50

> 224.0.0.0 240.0.0.0 192.168.173.4

> 192.168.173.4 50

> 224.0.0.0 240.0.0.0 192.168.174.2

> 192.168.174.2 50

> 255.255.255.255 255.255.255.255 81.27.99.113

> 81.27.99.113 1

> 255.255.255.255 255.255.255.255 192.168.164.2

> 192.168.164.2 1

> 255.255.255.255 255.255.255.255 192.168.165.2

> 192.168.165.2 1

> 255.255.255.255 255.255.255.255 192.168.173.2

> 192.168.173.2 1

> 255.255.255.255 255.255.255.255 192.168.173.4

> 192.168.173.4 1

> 255.255.255.255 255.255.255.255 192.168.174.2

> 192.168.174.2 1

> Default Gateway: 81.27.99.1

> ===========================================================================

> Persistent Routes:

> None

>

>

Guest N D

Guest N D

Posted
Posted

Re: Cannot PING Windows 2008 RRAS server IP

 

Hi Bob,

 

Here you go.

 

First the Tracert, not much too it really, one hop:

 

Tracing route to D [192.168.173.1]

over a maximum of 30 hops:

 

1 * * * Request timed out.

2 *

 

 

Then pathping just in case you find it useful. Pathping 192.168.173.1

 

Tracing route to D [192.168.173.1]

over a maximum of 30 hops:

0 A.xxx.com [192.168.173.2]

1 * * *

Computing statistics for 25 seconds...

 

 

Now IPCONFIG /all from D (The Win2008 box)

 

 

Windows IP Configuration

 

Host Name . . . . . . . . . . . . : D

Primary Dns Suffix . . . . . . . : xxx.com

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : xxx.com

 

PPP adapter A:

 

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : A

Physical Address. . . . . . . . . :

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 192.168.166.4(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 192.168.166.1

NetBIOS over Tcpip. . . . . . . . : Enabled

 

Ethernet adapter Local Area Connection:

 

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit

Ethernet

Physical Address. . . . . . . . . : 00-1E-C9-42-51-CA

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 81.27.106.26(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 81.27.106.1

DNS Servers . . . . . . . . . . . : 127.0.0.1

81.27.99.113

NetBIOS over Tcpip. . . . . . . . : Enabled

 

PPP adapter RAS (Dial In) Interface:

 

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : RAS (Dial In) Interface

Physical Address. . . . . . . . . :

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 192.168.173.1(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . :

NetBIOS over Tcpip. . . . . . . . : Disabled

 

 

Finally the routing table from D

 

===========================================================================

Interface List

17 ........................... INETC492

10 ...00 1e c9 42 51 ca ...... Broadcom NetXtreme Gigabit Ethernet

16 ........................... RAS (Dial In) Interface

1 ........................... Software Loopback Interface 1

===========================================================================

 

IPv4 Route Table

===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface

Metric

0.0.0.0 0.0.0.0 81.27.106.1

81.27.106.26 281

81.27.106.0 255.255.255.0 On-link

81.27.106.26 281

81.27.106.26 255.255.255.255 On-link

81.27.106.26 281

81.27.106.255 255.255.255.255 On-link

81.27.106.26 281

127.0.0.0 255.0.0.0 On-link

127.0.0.1 306

127.0.0.1 255.255.255.255 On-link

127.0.0.1 306

127.255.255.255 255.255.255.255 On-link

127.0.0.1 306

192.168.166.0 255.255.255.0 192.168.173.2

192.168.166.4 21

192.168.166.4 255.255.255.255 On-link

192.168.166.4 276

192.168.173.1 255.255.255.255 On-link

192.168.173.1 306

224.0.0.0 240.0.0.0 On-link

127.0.0.1 306

224.0.0.0 240.0.0.0 On-link

81.27.106.26 281

224.0.0.0 240.0.0.0 On-link

192.168.173.1 306

255.255.255.255 255.255.255.255 On-link

127.0.0.1 306

255.255.255.255 255.255.255.255 On-link

81.27.106.26 281

255.255.255.255 255.255.255.255 On-link

192.168.173.1 306

255.255.255.255 255.255.255.255 On-link

192.168.166.4 276

===========================================================================

Persistent Routes:

Network Address Netmask Gateway Address Metric

0.0.0.0 0.0.0.0 81.27.106.1 Default

===========================================================================

 

IPv6 Route Table

===========================================================================

Active Routes:

If Metric Network Destination Gateway

1 306 ::1/128 On-link

1 306 ff00::/8 On-link

===========================================================================

Persistent Routes:

None

 

 

 

On Jun 26, 2:32 pm, "Robert L. \(MS-MVP\)" <findem...@chicagotech.net>

wrote:

> It may help if you can post the result of routing table and ipconfig /all on

> D server. Also the result of tracert 192.168.173.x from A.

>

> --

> Bob Lin, MS-MVP, MCSE & CNE

> Networking, Internet, Routing, VPN Troubleshooting onhttp://www.ChicagoTech.net

> How to Setup Windows, Network, VPN & Remote Access onhttp://www.HowToNetworking.com"N D" <nick.d...@evaware.com> wrote in message

>

> news:6d7a47f6-dc73-43c3-9485-7250e9cdadff@r66g2000hsg.googlegroups.com...

Guest Robert L. \(MS-MVP\)

Guest Robert L. \(MS-MVP\)

Posted
Posted

Re: Cannot PING Windows 2008 RRAS server IP

 

is it possible you can turn off the firewall on the windows 2008 for a test?

 

--

Bob Lin, MS-MVP, MCSE & CNE

Networking, Internet, Routing, VPN Troubleshooting on

http://www.ChicagoTech.net

How to Setup Windows, Network, VPN & Remote Access on

http://www.HowToNetworking.com

"N D" <nick.dyer@evaware.com> wrote in message

news:6dd3b26b-3f18-4a97-b9c1-71da6b26abc1@8g2000hse.googlegroups.com...

Hi Bob,

 

Here you go.

 

First the Tracert, not much too it really, one hop:

 

Tracing route to D [192.168.173.1]

over a maximum of 30 hops:

 

1 * * * Request timed out.

2 *

 

 

Then pathping just in case you find it useful. Pathping 192.168.173.1

 

Tracing route to D [192.168.173.1]

over a maximum of 30 hops:

0 A.xxx.com [192.168.173.2]

1 * * *

Computing statistics for 25 seconds...

 

 

Now IPCONFIG /all from D (The Win2008 box)

 

 

Windows IP Configuration

 

Host Name . . . . . . . . . . . . : D

Primary Dns Suffix . . . . . . . : xxx.com

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : xxx.com

 

PPP adapter A:

 

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : A

Physical Address. . . . . . . . . :

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 192.168.166.4(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 192.168.166.1

NetBIOS over Tcpip. . . . . . . . : Enabled

 

Ethernet adapter Local Area Connection:

 

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit

Ethernet

Physical Address. . . . . . . . . : 00-1E-C9-42-51-CA

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 81.27.106.26(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 81.27.106.1

DNS Servers . . . . . . . . . . . : 127.0.0.1

81.27.99.113

NetBIOS over Tcpip. . . . . . . . : Enabled

 

PPP adapter RAS (Dial In) Interface:

 

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : RAS (Dial In) Interface

Physical Address. . . . . . . . . :

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 192.168.173.1(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . :

NetBIOS over Tcpip. . . . . . . . : Disabled

 

 

Finally the routing table from D

 

===========================================================================

Interface List

17 ........................... INETC492

10 ...00 1e c9 42 51 ca ...... Broadcom NetXtreme Gigabit Ethernet

16 ........................... RAS (Dial In) Interface

1 ........................... Software Loopback Interface 1

===========================================================================

 

IPv4 Route Table

===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface

Metric

0.0.0.0 0.0.0.0 81.27.106.1

81.27.106.26 281

81.27.106.0 255.255.255.0 On-link

81.27.106.26 281

81.27.106.26 255.255.255.255 On-link

81.27.106.26 281

81.27.106.255 255.255.255.255 On-link

81.27.106.26 281

127.0.0.0 255.0.0.0 On-link

127.0.0.1 306

127.0.0.1 255.255.255.255 On-link

127.0.0.1 306

127.255.255.255 255.255.255.255 On-link

127.0.0.1 306

192.168.166.0 255.255.255.0 192.168.173.2

192.168.166.4 21

192.168.166.4 255.255.255.255 On-link

192.168.166.4 276

192.168.173.1 255.255.255.255 On-link

192.168.173.1 306

224.0.0.0 240.0.0.0 On-link

127.0.0.1 306

224.0.0.0 240.0.0.0 On-link

81.27.106.26 281

224.0.0.0 240.0.0.0 On-link

192.168.173.1 306

255.255.255.255 255.255.255.255 On-link

127.0.0.1 306

255.255.255.255 255.255.255.255 On-link

81.27.106.26 281

255.255.255.255 255.255.255.255 On-link

192.168.173.1 306

255.255.255.255 255.255.255.255 On-link

192.168.166.4 276

===========================================================================

Persistent Routes:

Network Address Netmask Gateway Address Metric

0.0.0.0 0.0.0.0 81.27.106.1 Default

===========================================================================

 

IPv6 Route Table

===========================================================================

Active Routes:

If Metric Network Destination Gateway

1 306 ::1/128 On-link

1 306 ff00::/8 On-link

===========================================================================

Persistent Routes:

None

 

 

 

On Jun 26, 2:32 pm, "Robert L. \(MS-MVP\)" <findem...@chicagotech.net>

wrote:

> It may help if you can post the result of routing table and ipconfig /all

> on

> D server. Also the result of tracert 192.168.173.x from A.

>

> --

> Bob Lin, MS-MVP, MCSE & CNE

> Networking, Internet, Routing, VPN Troubleshooting

> onhttp://www.ChicagoTech.net

> How to Setup Windows, Network, VPN & Remote Access

> onhttp://www.HowToNetworking.com"N D" <nick.d...@evaware.com> wrote in

> message

>

> news:6d7a47f6-dc73-43c3-9485-7250e9cdadff@r66g2000hsg.googlegroups.com...

Guest Bill Grant

Guest Bill Grant

Posted
Posted

Re: Cannot PING Windows 2008 RRAS server IP

 

In addition, why do you need to ping the router itself? Can you connect to

the servers in this site from workstations in other sites?

 

"Robert L. (MS-MVP)" <findemail@chicagotech.net> wrote in message

news:ur$Tj981IHA.2068@TK2MSFTNGP05.phx.gbl...

> is it possible you can turn off the firewall on the windows 2008 for a

> test?

>

> --

> Bob Lin, MS-MVP, MCSE & CNE

> Networking, Internet, Routing, VPN Troubleshooting on

> http://www.ChicagoTech.net

> How to Setup Windows, Network, VPN & Remote Access on

> http://www.HowToNetworking.com

> "N D" <nick.dyer@evaware.com> wrote in message

> news:6dd3b26b-3f18-4a97-b9c1-71da6b26abc1@8g2000hse.googlegroups.com...

> Hi Bob,

>

> Here you go.

>

> First the Tracert, not much too it really, one hop:

>

> Tracing route to D [192.168.173.1]

> over a maximum of 30 hops:

>

> 1 * * * Request timed out.

> 2 *

>

>

> Then pathping just in case you find it useful. Pathping 192.168.173.1

>

> Tracing route to D [192.168.173.1]

> over a maximum of 30 hops:

> 0 A.xxx.com [192.168.173.2]

> 1 * * *

> Computing statistics for 25 seconds...

>

>

> Now IPCONFIG /all from D (The Win2008 box)

>

>

> Windows IP Configuration

>

> Host Name . . . . . . . . . . . . : D

> Primary Dns Suffix . . . . . . . : xxx.com

> Node Type . . . . . . . . . . . . : Hybrid

> IP Routing Enabled. . . . . . . . : Yes

> WINS Proxy Enabled. . . . . . . . : No

> DNS Suffix Search List. . . . . . : xxx.com

>

> PPP adapter A:

>

> Connection-specific DNS Suffix . :

> Description . . . . . . . . . . . : A

> Physical Address. . . . . . . . . :

> DHCP Enabled. . . . . . . . . . . : No

> Autoconfiguration Enabled . . . . : Yes

> IPv4 Address. . . . . . . . . . . : 192.168.166.4(Preferred)

> Subnet Mask . . . . . . . . . . . : 255.255.255.255

> Default Gateway . . . . . . . . . :

> DNS Servers . . . . . . . . . . . : 192.168.166.1

> NetBIOS over Tcpip. . . . . . . . : Enabled

>

> Ethernet adapter Local Area Connection:

>

> Connection-specific DNS Suffix . :

> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit

> Ethernet

> Physical Address. . . . . . . . . : 00-1E-C9-42-51-CA

> DHCP Enabled. . . . . . . . . . . : No

> Autoconfiguration Enabled . . . . : Yes

> IPv4 Address. . . . . . . . . . . : 81.27.106.26(Preferred)

> Subnet Mask . . . . . . . . . . . : 255.255.255.0

> Default Gateway . . . . . . . . . : 81.27.106.1

> DNS Servers . . . . . . . . . . . : 127.0.0.1

> 81.27.99.113

> NetBIOS over Tcpip. . . . . . . . : Enabled

>

> PPP adapter RAS (Dial In) Interface:

>

> Connection-specific DNS Suffix . :

> Description . . . . . . . . . . . : RAS (Dial In) Interface

> Physical Address. . . . . . . . . :

> DHCP Enabled. . . . . . . . . . . : No

> Autoconfiguration Enabled . . . . : Yes

> IPv4 Address. . . . . . . . . . . : 192.168.173.1(Preferred)

> Subnet Mask . . . . . . . . . . . : 255.255.255.255

> Default Gateway . . . . . . . . . :

> NetBIOS over Tcpip. . . . . . . . : Disabled

>

>

> Finally the routing table from D

>

> ===========================================================================

> Interface List

> 17 ........................... INETC492

> 10 ...00 1e c9 42 51 ca ...... Broadcom NetXtreme Gigabit Ethernet

> 16 ........................... RAS (Dial In) Interface

> 1 ........................... Software Loopback Interface 1

> ===========================================================================

>

> IPv4 Route Table

> ===========================================================================

> Active Routes:

> Network Destination Netmask Gateway Interface

> Metric

> 0.0.0.0 0.0.0.0 81.27.106.1

> 81.27.106.26 281

> 81.27.106.0 255.255.255.0 On-link

> 81.27.106.26 281

> 81.27.106.26 255.255.255.255 On-link

> 81.27.106.26 281

> 81.27.106.255 255.255.255.255 On-link

> 81.27.106.26 281

> 127.0.0.0 255.0.0.0 On-link

> 127.0.0.1 306

> 127.0.0.1 255.255.255.255 On-link

> 127.0.0.1 306

> 127.255.255.255 255.255.255.255 On-link

> 127.0.0.1 306

> 192.168.166.0 255.255.255.0 192.168.173.2

> 192.168.166.4 21

> 192.168.166.4 255.255.255.255 On-link

> 192.168.166.4 276

> 192.168.173.1 255.255.255.255 On-link

> 192.168.173.1 306

> 224.0.0.0 240.0.0.0 On-link

> 127.0.0.1 306

> 224.0.0.0 240.0.0.0 On-link

> 81.27.106.26 281

> 224.0.0.0 240.0.0.0 On-link

> 192.168.173.1 306

> 255.255.255.255 255.255.255.255 On-link

> 127.0.0.1 306

> 255.255.255.255 255.255.255.255 On-link

> 81.27.106.26 281

> 255.255.255.255 255.255.255.255 On-link

> 192.168.173.1 306

> 255.255.255.255 255.255.255.255 On-link

> 192.168.166.4 276

> ===========================================================================

> Persistent Routes:

> Network Address Netmask Gateway Address Metric

> 0.0.0.0 0.0.0.0 81.27.106.1 Default

> ===========================================================================

>

> IPv6 Route Table

> ===========================================================================

> Active Routes:

> If Metric Network Destination Gateway

> 1 306 ::1/128 On-link

> 1 306 ff00::/8 On-link

> ===========================================================================

> Persistent Routes:

> None

>

>

>

> On Jun 26, 2:32 pm, "Robert L. \(MS-MVP\)" <findem...@chicagotech.net>

> wrote:

>> It may help if you can post the result of routing table and ipconfig /all

>> on

>> D server. Also the result of tracert 192.168.173.x from A.

>>

>> --

>> Bob Lin, MS-MVP, MCSE & CNE

>> Networking, Internet, Routing, VPN Troubleshooting

>> onhttp://www.ChicagoTech.net

>> How to Setup Windows, Network, VPN & Remote Access

>> onhttp://www.HowToNetworking.com"N D" <nick.d...@evaware.com> wrote in

>> message

>>

>> news:6d7a47f6-dc73-43c3-9485-7250e9cdadff@r66g2000hsg.googlegroups.com...

>

  • 3 weeks later...
Guest smposter

Guest smposter

Posted
Posted

Re: Cannot PING Windows 2008 RRAS server IP

 

This problem is likely due to a "feature" in server 2008. I had the exact

same problem. Your clue will be to look at the differences between the route

tables for 2003 - 2003 and 2003 - 2008. You will note that on 2008 there is

no route back to the other rras server through the demand-dial link assigned

IP interface, yet this exists on 2003 by default. What blows is that you

have to add this as a static route (route add) every time the dd interface is

assigned a new ip through reboots or re-dials. Still waiting for MS to fix

this crap. Once you get the routes in there, you will be able to ping the

other rras server and devices on the other networks from the rras server.

 

"Bill Grant" wrote:

> In addition, why do you need to ping the router itself? Can you connect to

> the servers in this site from workstations in other sites?

>

> "Robert L. (MS-MVP)" <findemail@chicagotech.net> wrote in message

> news:ur$Tj981IHA.2068@TK2MSFTNGP05.phx.gbl...

> > is it possible you can turn off the firewall on the windows 2008 for a

> > test?

> >

> > --

> > Bob Lin, MS-MVP, MCSE & CNE

> > Networking, Internet, Routing, VPN Troubleshooting on

> > http://www.ChicagoTech.net

> > How to Setup Windows, Network, VPN & Remote Access on

> > http://www.HowToNetworking.com

> > "N D" <nick.dyer@evaware.com> wrote in message

> > news:6dd3b26b-3f18-4a97-b9c1-71da6b26abc1@8g2000hse.googlegroups.com...

> > Hi Bob,

> >

> > Here you go.

> >

> > First the Tracert, not much too it really, one hop:

> >

> > Tracing route to D [192.168.173.1]

> > over a maximum of 30 hops:

> >

> > 1 * * * Request timed out.

> > 2 *

> >

> >

> > Then pathping just in case you find it useful. Pathping 192.168.173.1

> >

> > Tracing route to D [192.168.173.1]

> > over a maximum of 30 hops:

> > 0 A.xxx.com [192.168.173.2]

> > 1 * * *

> > Computing statistics for 25 seconds...

> >

> >

> > Now IPCONFIG /all from D (The Win2008 box)

> >

> >

> > Windows IP Configuration

> >

> > Host Name . . . . . . . . . . . . : D

> > Primary Dns Suffix . . . . . . . : xxx.com

> > Node Type . . . . . . . . . . . . : Hybrid

> > IP Routing Enabled. . . . . . . . : Yes

> > WINS Proxy Enabled. . . . . . . . : No

> > DNS Suffix Search List. . . . . . : xxx.com

> >

> > PPP adapter A:

> >

> > Connection-specific DNS Suffix . :

> > Description . . . . . . . . . . . : A

> > Physical Address. . . . . . . . . :

> > DHCP Enabled. . . . . . . . . . . : No

> > Autoconfiguration Enabled . . . . : Yes

> > IPv4 Address. . . . . . . . . . . : 192.168.166.4(Preferred)

> > Subnet Mask . . . . . . . . . . . : 255.255.255.255

> > Default Gateway . . . . . . . . . :

> > DNS Servers . . . . . . . . . . . : 192.168.166.1

> > NetBIOS over Tcpip. . . . . . . . : Enabled

> >

> > Ethernet adapter Local Area Connection:

> >

> > Connection-specific DNS Suffix . :

> > Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit

> > Ethernet

> > Physical Address. . . . . . . . . : 00-1E-C9-42-51-CA

> > DHCP Enabled. . . . . . . . . . . : No

> > Autoconfiguration Enabled . . . . : Yes

> > IPv4 Address. . . . . . . . . . . : 81.27.106.26(Preferred)

> > Subnet Mask . . . . . . . . . . . : 255.255.255.0

> > Default Gateway . . . . . . . . . : 81.27.106.1

> > DNS Servers . . . . . . . . . . . : 127.0.0.1

> > 81.27.99.113

> > NetBIOS over Tcpip. . . . . . . . : Enabled

> >

> > PPP adapter RAS (Dial In) Interface:

> >

> > Connection-specific DNS Suffix . :

> > Description . . . . . . . . . . . : RAS (Dial In) Interface

> > Physical Address. . . . . . . . . :

> > DHCP Enabled. . . . . . . . . . . : No

> > Autoconfiguration Enabled . . . . : Yes

> > IPv4 Address. . . . . . . . . . . : 192.168.173.1(Preferred)

> > Subnet Mask . . . . . . . . . . . : 255.255.255.255

> > Default Gateway . . . . . . . . . :

> > NetBIOS over Tcpip. . . . . . . . : Disabled

> >

> >

> > Finally the routing table from D

> >

> > ===========================================================================

> > Interface List

> > 17 ........................... INETC492

> > 10 ...00 1e c9 42 51 ca ...... Broadcom NetXtreme Gigabit Ethernet

> > 16 ........................... RAS (Dial In) Interface

> > 1 ........................... Software Loopback Interface 1

> > ===========================================================================

> >

> > IPv4 Route Table

> > ===========================================================================

> > Active Routes:

> > Network Destination Netmask Gateway Interface

> > Metric

> > 0.0.0.0 0.0.0.0 81.27.106.1

> > 81.27.106.26 281

> > 81.27.106.0 255.255.255.0 On-link

> > 81.27.106.26 281

> > 81.27.106.26 255.255.255.255 On-link

> > 81.27.106.26 281

> > 81.27.106.255 255.255.255.255 On-link

> > 81.27.106.26 281

> > 127.0.0.0 255.0.0.0 On-link

> > 127.0.0.1 306

> > 127.0.0.1 255.255.255.255 On-link

> > 127.0.0.1 306

> > 127.255.255.255 255.255.255.255 On-link

> > 127.0.0.1 306

> > 192.168.166.0 255.255.255.0 192.168.173.2

> > 192.168.166.4 21

> > 192.168.166.4 255.255.255.255 On-link

> > 192.168.166.4 276

> > 192.168.173.1 255.255.255.255 On-link

> > 192.168.173.1 306

> > 224.0.0.0 240.0.0.0 On-link

> > 127.0.0.1 306

> > 224.0.0.0 240.0.0.0 On-link

> > 81.27.106.26 281

> > 224.0.0.0 240.0.0.0 On-link

> > 192.168.173.1 306

> > 255.255.255.255 255.255.255.255 On-link

> > 127.0.0.1 306

> > 255.255.255.255 255.255.255.255 On-link

> > 81.27.106.26 281

> > 255.255.255.255 255.255.255.255 On-link

> > 192.168.173.1 306

> > 255.255.255.255 255.255.255.255 On-link

> > 192.168.166.4 276

> > ===========================================================================

> > Persistent Routes:

> > Network Address Netmask Gateway Address Metric

> > 0.0.0.0 0.0.0.0 81.27.106.1 Default

> > ===========================================================================

> >

> > IPv6 Route Table

> > ===========================================================================

> > Active Routes:

> > If Metric Network Destination Gateway

> > 1 306 ::1/128 On-link

> > 1 306 ff00::/8 On-link

> > ===========================================================================

> > Persistent Routes:

> > None

> >

> >

> >

> > On Jun 26, 2:32 pm, "Robert L. \(MS-MVP\)" <findem...@chicagotech.net>

> > wrote:

> >> It may help if you can post the result of routing table and ipconfig /all

> >> on

> >> D server. Also the result of tracert 192.168.173.x from A.

> >>

> >> --

> >> Bob Lin, MS-MVP, MCSE & CNE

> >> Networking, Internet, Routing, VPN Troubleshooting

> >> onhttp://www.ChicagoTech.net

> >> How to Setup Windows, Network, VPN & Remote Access

> >> onhttp://www.HowToNetworking.com"N D" <nick.d...@evaware.com> wrote in

> >> message

> >>

> >> news:6d7a47f6-dc73-43c3-9485-7250e9cdadff@r66g2000hsg.googlegroups.com...

> >

>

  • 2 months later...
Guest Mitchel Hudson

Guest Mitchel Hudson

Posted
Posted

Workaround to use Windows 2008 RRAS

 

Workaround to use Windows 2008 RRAS

 

I have noticed several people experiencing the problem described below. I was also having the same issue. I opened a case with Microsoft. After getting through 3 levels, I finally got to an engineer, Barry, who duplicated the error and found the solution.

 

Problem: When establishing a Demand Dial connection to a Windows 2008 server with the RRAS Service Role, you cannot ping the RRAS (Windows 2008) server nor access its resources. You can, however, ping and access resources on either side of the tunnel. I specifically had an issue where I could ping from my Windows 2008 RRAS server to my Windows 2003 RRAS server and access resources on the Windows 2003 but not vice versa.

 

Cause: The Microsoft developers decided not to automatically populate a route from a Windows 2008 RRAS server back to the server on the other side of the tunnel. This decision was made based on a perceived best practice: an RRAS server should not fill any other role and, therefore, no other machine should need to access resources on the RRAS server.

 

Discussion: Obviously, in real life, this is not the case. Not many people use a Windows server as a router only; this would incur unnecessary expenses in time to manage a server and money to buy and maintain software and hardware (even a virtual server incurs some hardware and software expense). Generally, if a Windows server is used as a router, it is an additional role for a server that is already in use.

 

Solution: Here is the recommended work around that worked very well for me. You should look for the official Microsoft workaround to be posted very soon on this blog: http://blogs.technet.com/networking.

 

1. On each server’s demand dial connection set the TCPIPv4 network properties to use a static IP address. Use an address from the opposite side of the tunnel. Use a DNS server from the near side of the tunnel.

 

2. On Windows 2008 servers, place a static route to the opposite RRAS server using this command:

 

route –p add <IP address assigned to the far side server> mask 255.255.255.255 <IP address assigned to the 2008 server>

 

3. Set only one of the connections to automatically re-dial.

 

Example: In my example, I had a Windows 2003 server in Indiana and a Windows 2008 server in Colorado.

 

Indiana

Windows 2003 R2 Enterprise x64

External IP 65.65.65.65

Internal IP 10.10.10.200

Internal network 10.10.10.0 mask 255.255.255.0

Internal DNS 10.10.10.200

 

Indiana DoD Connection

Interface Name and User Name: companyrouter

Host to dial: 70.70.70.70

Static IP: 10.20.20.3 mask 255.255.255.0

DNS: 10.10.10.200

Redial 99 times

 

Colorado

Windows 2008 Enterprise x64

External IP 70.70.70.70

Internal IP 10.20.20.200

Internal network 10.20.20.0 mask 255.255.255.0

Internal DNS 10.20.20.200

 

Colorado DoD Connection

Interface Name and User Name: companyrouter

Host to dial: 65.65.65.65

Static IP: 10.10.10.3 mask 255.255.255.0

DNS: 10.20.20.200

Redial 0 times

 

I hope this helps you and others suffering from the same frustration I did for months trying to figure this one out.

 

Mitchel Hudson

Hudson Computer Services

877-399-0003

Guest HCS-Mitch

Guest HCS-Mitch

Posted
Posted

Re: Cannot PING Windows 2008 RRAS server IP

 

I have noticed several people experiencing the problem described below. I

was also having the same issue. I opened a case with Microsoft. After

getting through 3 levels, I finally got to an engineer, Barry, who duplicated

the error and found the solution.

 

Problem: When establishing a Demand Dial connection to a Windows 2008

server with the RRAS Service Role, you cannot ping the RRAS (Windows 2008)

server nor access its resources. You can, however, ping and access resources

on either side of the tunnel. I specifically had an issue where I could ping

from my Windows 2008 RRAS server to my Windows 2003 RRAS server and access

resources on the Windows 2003 but not vice versa.

 

Cause: The Microsoft developers decided not to automatically populate a

route from a Windows 2008 RRAS server back to the server on the other side of

the tunnel. This decision was made based on a perceived best practice: an

RRAS server should not fill any other role and, therefore, no other machine

should need to access resources on the RRAS server.

 

Discussion: Obviously, in real life, this is not the case. Not many people

use a Windows server as a router only; this would incur unnecessary expenses

in time to manage a server and money to buy and maintain software and

hardware (even a virtual server incurs some hardware and software expense).

Generally, if a Windows server is used as a router, it is an additional role

for a server that is already in use.

 

Solution: Here is the recommended work around that worked very well for me.

You should look for the official Microsoft workaround to be posted very soon

on this blog: http://blogs.technet.com/networking.

 

1. On each server’s demand dial connection set the TCPIPv4 network

properties to use a static IP address. Use an address from the opposite side

of the tunnel. Use a DNS server from the near side of the tunnel.

 

2. On Windows 2008 servers, place a static route to the opposite RRAS

server using this command:

 

route –p add <IP address assigned to the far side server> mask

255.255.255.255 <IP address assigned to the 2008 server>

 

3. Set only one of the connections to automatically re-dial.

 

Example: In my example, I had a Windows 2003 server in Indiana and a

Windows 2008 server in Colorado.

 

Indiana

Windows 2003 R2 Enterprise x64

External IP 65.65.65.65

Internal IP 10.10.10.200

Internal network 10.10.10.0 mask 255.255.255.0

Internal DNS 10.10.10.200

 

Indiana DoD Connection

Interface Name and User Name: companyrouter

Host to dial: 70.70.70.70

Static IP: 10.20.20.3 mask 255.255.255.0

DNS: 10.10.10.200

Redial 99 times

 

Colorado

Windows 2008 Enterprise x64

External IP 70.70.70.70

Internal IP 10.20.20.200

Internal network 10.20.20.0 mask 255.255.255.0

Internal DNS 10.20.20.200

 

Colorado DoD Connection

Interface Name and User Name: companyrouter

Host to dial: 65.65.65.65

Static IP: 10.10.10.3 mask 255.255.255.0

DNS: 10.20.20.200

Redial 0 times

 

I hope this helps you and others suffering from the same frustration I did

for months trying to figure this one out.

 

Mitchel Hudson

Hudson Computer Services

877-399-0003

 

 

"Robert L. (MS-MVP)" wrote:

> is it possible you can turn off the firewall on the windows 2008 for a test?

>

> --

> Bob Lin, MS-MVP, MCSE & CNE

> Networking, Internet, Routing, VPN Troubleshooting on

> http://www.ChicagoTech.net

> How to Setup Windows, Network, VPN & Remote Access on

> http://www.HowToNetworking.com

> "N D" <nick.dyer@evaware.com> wrote in message

> news:6dd3b26b-3f18-4a97-b9c1-71da6b26abc1@8g2000hse.googlegroups.com...

> Hi Bob,

>

> Here you go.

>

> First the Tracert, not much too it really, one hop:

>

> Tracing route to D [192.168.173.1]

> over a maximum of 30 hops:

>

> 1 * * * Request timed out.

> 2 *

>

>

> Then pathping just in case you find it useful. Pathping 192.168.173.1

>

> Tracing route to D [192.168.173.1]

> over a maximum of 30 hops:

> 0 A.xxx.com [192.168.173.2]

> 1 * * *

> Computing statistics for 25 seconds...

>

>

> Now IPCONFIG /all from D (The Win2008 box)

>

>

> Windows IP Configuration

>

> Host Name . . . . . . . . . . . . : D

> Primary Dns Suffix . . . . . . . : xxx.com

> Node Type . . . . . . . . . . . . : Hybrid

> IP Routing Enabled. . . . . . . . : Yes

> WINS Proxy Enabled. . . . . . . . : No

> DNS Suffix Search List. . . . . . : xxx.com

>

> PPP adapter A:

>

> Connection-specific DNS Suffix . :

> Description . . . . . . . . . . . : A

> Physical Address. . . . . . . . . :

> DHCP Enabled. . . . . . . . . . . : No

> Autoconfiguration Enabled . . . . : Yes

> IPv4 Address. . . . . . . . . . . : 192.168.166.4(Preferred)

> Subnet Mask . . . . . . . . . . . : 255.255.255.255

> Default Gateway . . . . . . . . . :

> DNS Servers . . . . . . . . . . . : 192.168.166.1

> NetBIOS over Tcpip. . . . . . . . : Enabled

>

> Ethernet adapter Local Area Connection:

>

> Connection-specific DNS Suffix . :

> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit

> Ethernet

> Physical Address. . . . . . . . . : 00-1E-C9-42-51-CA

> DHCP Enabled. . . . . . . . . . . : No

> Autoconfiguration Enabled . . . . : Yes

> IPv4 Address. . . . . . . . . . . : 81.27.106.26(Preferred)

> Subnet Mask . . . . . . . . . . . : 255.255.255.0

> Default Gateway . . . . . . . . . : 81.27.106.1

> DNS Servers . . . . . . . . . . . : 127.0.0.1

> 81.27.99.113

> NetBIOS over Tcpip. . . . . . . . : Enabled

>

> PPP adapter RAS (Dial In) Interface:

>

> Connection-specific DNS Suffix . :

> Description . . . . . . . . . . . : RAS (Dial In) Interface

> Physical Address. . . . . . . . . :

> DHCP Enabled. . . . . . . . . . . : No

> Autoconfiguration Enabled . . . . : Yes

> IPv4 Address. . . . . . . . . . . : 192.168.173.1(Preferred)

> Subnet Mask . . . . . . . . . . . : 255.255.255.255

> Default Gateway . . . . . . . . . :

> NetBIOS over Tcpip. . . . . . . . : Disabled

>

>

> Finally the routing table from D

>

> ===========================================================================

> Interface List

> 17 ........................... INETC492

> 10 ...00 1e c9 42 51 ca ...... Broadcom NetXtreme Gigabit Ethernet

> 16 ........................... RAS (Dial In) Interface

> 1 ........................... Software Loopback Interface 1

> ===========================================================================

>

> IPv4 Route Table

> ===========================================================================

> Active Routes:

> Network Destination Netmask Gateway Interface

> Metric

> 0.0.0.0 0.0.0.0 81.27.106.1

> 81.27.106.26 281

> 81.27.106.0 255.255.255.0 On-link

> 81.27.106.26 281

> 81.27.106.26 255.255.255.255 On-link

> 81.27.106.26 281

> 81.27.106.255 255.255.255.255 On-link

> 81.27.106.26 281

> 127.0.0.0 255.0.0.0 On-link

> 127.0.0.1 306

> 127.0.0.1 255.255.255.255 On-link

> 127.0.0.1 306

> 127.255.255.255 255.255.255.255 On-link

> 127.0.0.1 306

> 192.168.166.0 255.255.255.0 192.168.173.2

> 192.168.166.4 21

> 192.168.166.4 255.255.255.255 On-link

> 192.168.166.4 276

> 192.168.173.1 255.255.255.255 On-link

> 192.168.173.1 306

> 224.0.0.0 240.0.0.0 On-link

> 127.0.0.1 306

> 224.0.0.0 240.0.0.0 On-link

> 81.27.106.26 281

> 224.0.0.0 240.0.0.0 On-link

> 192.168.173.1 306

> 255.255.255.255 255.255.255.255 On-link

> 127.0.0.1 306

> 255.255.255.255 255.255.255.255 On-link

> 81.27.106.26 281

> 255.255.255.255 255.255.255.255 On-link

> 192.168.173.1 306

> 255.255.255.255 255.255.255.255 On-link

> 192.168.166.4 276

> ===========================================================================

> Persistent Routes:

> Network Address Netmask Gateway Address Metric

> 0.0.0.0 0.0.0.0 81.27.106.1 Default

> ===========================================================================

>

> IPv6 Route Table

> ===========================================================================

> Active Routes:

> If Metric Network Destination Gateway

> 1 306 ::1/128 On-link

> 1 306 ff00::/8 On-link

> ===========================================================================

> Persistent Routes:

> None

>

>

>

> On Jun 26, 2:32 pm, "Robert L. \(MS-MVP\)" <findem...@chicagotech.net>

> wrote:

> > It may help if you can post the result of routing table and ipconfig /all

> > on

> > D server. Also the result of tracert 192.168.173.x from A.

> >

> > --

> > Bob Lin, MS-MVP, MCSE & CNE

> > Networking, Internet, Routing, VPN Troubleshooting

> > onhttp://www.ChicagoTech.net

> > How to Setup Windows, Network, VPN & Remote Access

> > onhttp://www.HowToNetworking.com"N D" <nick.d...@evaware.com> wrote in

> > message

> >

> > news:6d7a47f6-dc73-43c3-9485-7250e9cdadff@r66g2000hsg.googlegroups.com...

>

>

 Share
Go to topic listing
×
×
  • Create New...