Re: Multihomed server 2000
- From: "DPM" <dm@xxxxxxxx>
- Date: Tue, 28 Mar 2006 08:19:22 -0500
Bill,
Thanks for responding.
Please let me clarify: I have a server with 2 NICs; one NIC is set to
192.168.0.5, and everything on this NIC is normal and active; I can ping it
from a computer attached to this interface.
I have a second NIC set to 192.168.200.1; if I attach a computer to this
interface, give the computer an address of 192.168.200.200 and from it ping
192.168.200.1 I get no reply.
Note that I'm not trying to ping the 192.168.200 net from 192.168.0 net; I'm
simply trying to ping the 192.168.200.1 server on that net, and it's not
responding. Setting a default gateway address of 192.168.200.1 in the
192.168.200.200 machine does not fix the problem.
If I run Network Monitor on the 192.168.200 NIC, I see the ping requests
arrive at the server, but the server doesn't respond. If I ping the .200
machine from the server, NM records nothing, although ping reports a
timeout. If I ping 192.168.200.1 from the server console, ping records a
normal response.
This seems like it should be clear and straightforward - what am I missing
here?
Thanks for your help.
Regards,
Dean
"Bill Grant" <not.available@online> wrote in message
news:OJPS8$fUGHA.1728@xxxxxxxxxxxxxxxxxxxxxxx
Default routing falls down when there are multiple routers involved.The
main reason you cannot ping a machine in 192.168.200 froma workstation insubnet
192.168.0 is that the default route is to 192.168.0.1, not to the RRAS
router. To get to 192.168.200 you need a specific route to get the traffic
to the RRAS router. You can add this route to each machine in 192.168.0 or
add it to the router at 192.168.0.1 . In either case this gets the traffic
for 192.168.200 to the RRAS router.
192.168.200.0 255.255.255.0 192.168.0.5
The second reason is that the machine in 192.168.200 does not have a
default gateway set. Set this to be the RRAS router interface in that
(192.168.200.1) so that there is a route back to the RRAS router for the
reply.
DPM wrote:
Bob,
I supplied ipconfig reports in my reply to Bill, but no, I did not
enable NAT on the second interface. I did enable LAN routing.
Regards,
Dean
"Robert L [MS-MVP]" <noreply@xxxxxxxxxxx> wrote in message
news:OzMKKr5TGHA.4540@xxxxxxxxxxxxxxxxxxxxxxx
We need more information to help. Do you enable NAT since you have
two NICs? Posting the results of VPN server and client ipconfig /all
here may help.
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
"DPM" <dm@xxxxxxxx> wrote in message
news:%231ghH43TGHA.5500@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
I've got a Win2K server with 2 NICs; one is set to 192.168.0.5
and is
connected to the LAN, the other is set to 192.168.200.1 (both
masks
255.255.255.0). The first works fine; I want to use the second
for VPNs,
but I can't ping it. It's enabled, I can see pings arriving, but
no
response. Any idea why? (No firewalls, BTW).
Thanks for any suggestions.
--
Regards,
Dean
.
- References:
- Multihomed server 2000
- From: DPM
- Re: Multihomed server 2000
- From: Robert L [MS-MVP]
- Re: Multihomed server 2000
- From: Bill Grant
- Multihomed server 2000
- Prev by Date: RRAS persistent demand-dial connection fails on system startup, but works afterwards
- Next by Date: Re: RRAS persistent demand-dial connection fails on system startup, but works afterwards
- Previous by thread: Re: Multihomed server 2000
- Next by thread: Re: Multihomed server 2000
- Index(es):
Relevant Pages
|
|