Thank you everyone for the feedback. Although configuring the default
gateway on PC2 with its own IP address allowed me to ping from PC1 to PC2,
it caused some other problems in a part of the network that I omitted, so I
had to re-configure it back without a default gateway. Let me re-draw the
diagram to include the omitted part:
|-------Private Network--------| ------Public Network----------|
e0 e1 e0 e1 e0 e1 e0 e1
PC1---routerA----routerB---------PC2-----routerC-----Internet
So, basically PC2 is a server with interfaces in a public and a private
network. Router A and router B connect an office to the hosting center via
a T1 line, that's why we need the router. Otherwise, there is no need for
the router on the private interface, since they can communicate via NetBIOS
names without any security concerns. What happened when I configured PC2
with it's own IP on the default gateway was that the public interface
stopped responding away (Windows 2000 server). When I configure the default
GW as routerB's address, the same thing happen but is sporadic and only
starts after a week or so. Weird!
As far as setting a default route, I don't think this will work on Windows
2000 unless it is acting as a router itself.
-Henrique
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=44281&t=44108
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
