Re: win2000as routing
- From: "Bill Grant" <not.available@online>
- Date: Fri, 3 Mar 2006 10:58:09 +1100
If it was a bug I think somebody else would have noticed it by now. It
has been in production for over six years.
Dejan Rodiger wrote:
Hi,
Does Win 2000 Advanced Server have some bugs in routing?
I have Ethernet card and modem on the server and I have created
Incoming connections. It gives IP address to the calling PC.
I have created permanent route (or even non persistant one) to the
calling network with modem as a gateway. After the calling PC
disconnects, and calls again, my routing doesn't work. I can only
ping remote IP address, but it is actually localhost (because routing
table is wrong).
For example:
Ethernet card IP address is 192.168.0.2 with default gateway on
192.168.0.1. Modem IF is 0x1000000.
After remote PC connects, my modem has IP 192.168.1.1 and the remote
has 192.168.1.2
Remote network has this parameters 192.168.2.0/24 and all PC's have
gateway 192.168.2.1 (the PC with the modem)
Now I create route:
route add 192.168.2.0 netmask 255.255.255.0 192.168.1.2 IF 0x10000000
Now I can ping remote network (192.168.2.1-254)
After I disconnects and connects again, my routing table is all wrong.
It says that my route for network 192.168.2.0 has gateway 127.0.0.1
Even after remote PC connects again, it doesn't resolve the routing
table.
For now the solution was:
route -f
route add 192.168.2.0 netmask 255.255.255.0 192.168.1.2 IF 0x10000000
But with this I don't have gateway for my ethernet card any more.
This is a bug!
.
- Follow-Ups:
- Re: win2000as routing
- From: Bill Grant
- Re: win2000as routing
- References:
- win2000as routing
- From: Dejan Rodiger
- win2000as routing
- Prev by Date: 2 Questions on RRAS routing
- Next by Date: Re: win2000as routing
- Previous by thread: win2000as routing
- Next by thread: Re: win2000as routing
- Index(es):
Relevant Pages
|
Loading