Windows 2000 - XP Pro- Adding static route or default gw to "Incoming Connections"

  • Thread starter Thread starter Dimitris Chrysaidis
  • Start date Start date
D

Dimitris Chrysaidis

I have the following problem:

When using "Incoming Connections" on a Windows 2000 or XP Pro machine,
ipconfig
shows the following interface:

PPP adapter RAS Server (Dial In) Interface:



Connection-specific DNS Suffix . :

IP Address. . . . . . . . . . . . : 192.168.104.198

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

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


The machine that calls the W2K PC is a Cisco router. I need to add a default
gateway to this
connections or even a static route, in order for the PC to be able to access
IP addresses on
the Ethernet LAN of the Cisco router:

[Win 2000 PC] <--> [Cisco Router] <- (Ethernet IP subnet) -> [Target Host]

All my tries for "route add" give out an error message, probably because of
the subnet mask
255.255.255.255. The two addresses that I have provided to

"Incoming Connections" -> "Networking" -> "Internet Protocol (TCP/IP)"

are 192.168.104.198 and 192.168.104.199

The Cisco box somehow manages to always have 192.168.104.1 assigned to it
when it calls
the W2K PC (!).

Any suggestions would be most welcome !

Thank you.
 
You can't do this easily with Pro. With a server running RRAS, you can
set up a demand-dial interface and then set up a static route back to the
calling subnet, using the demand-dial interface as the symbolic name for the
connection. (You do this with the New Static Route wizard in RRAS).

With Pro, you cannot set up the route in advance, because the interface
doesn't exist until the connection is made! After the connection is up, you
should be able to add a static route using the tunnel endpoint (ie the
"virtual" IP) as the interface for the route.
 
Adding the static route after the connection is made would be acceptable
for the solution I am developing. The problem is that any "route add"
command
fails on this specific "interface". Following the "ipconfig" output:

PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :

IP Address. . . . . . . . . . . . : 192.168.104.198
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :

I enter:

route add 0.0.0.0 mask 0.0.0.0 192.168.104.198

(which fails with some message for unaceptable gateway)

The above is typical gateway for dial-out interfaces, yet W2K Pro RAS does
not behave
like a dial-out interface :-(

Any ideas ?

Bill Grant said:
You can't do this easily with Pro. With a server running RRAS, you can
set up a demand-dial interface and then set up a static route back to the
calling subnet, using the demand-dial interface as the symbolic name for the
connection. (You do this with the New Static Route wizard in RRAS).

With Pro, you cannot set up the route in advance, because the interface
doesn't exist until the connection is made! After the connection is up, you
should be able to add a static route using the tunnel endpoint (ie the
"virtual" IP) as the interface for the route.

Dimitris Chrysaidis said:
I have the following problem:

When using "Incoming Connections" on a Windows 2000 or XP Pro machine,
ipconfig
shows the following interface:

PPP adapter RAS Server (Dial In) Interface:



Connection-specific DNS Suffix . :

IP Address. . . . . . . . . . . . : 192.168.104.198

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

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


The machine that calls the W2K PC is a Cisco router. I need to add a default
gateway to this
connections or even a static route, in order for the PC to be able to access
IP addresses on
the Ethernet LAN of the Cisco router:

[Win 2000 PC] <--> [Cisco Router] <- (Ethernet IP subnet) -> [Target Host]

All my tries for "route add" give out an error message, probably because of
the subnet mask
255.255.255.255. The two addresses that I have provided to

"Incoming Connections" -> "Networking" -> "Internet Protocol (TCP/IP)"

are 192.168.104.198 and 192.168.104.199

The Cisco box somehow manages to always have 192.168.104.1 assigned to it
when it calls
the W2K PC (!).

Any suggestions would be most welcome !

Thank you.
Click to expand...
Click to expand...
 
Back
Top