Anonymous_User Absent Member.
Absent Member.
1787 views

subnet not seeing router

I currently have a Netware file server and a bordermanager server. Both
w/ 6. I am going to be replacing the bordermanager server w/ a cisco pix
router. It will act as a router to the internet and as a DHCP server.
The routers address will be 192.168.1.1. I have everything working except
that I have a subnet that gets its IP addresses from my file server. The
subent is 192.168.2.0. The file servers ip address is 192.168.1.253. The
file server gets it's ip from the router and is able to ping the router.
Any pc on the 192.168.2.0 can not see the router but can ping the file
server. I need the pc's on the subnet to be able to see the router so
they can route through their to get their internet connection. What do I
need to do.
Labels (2)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: subnet not seeing router

On 8/8/2005 scramer@cusd3.com wrote:

> I am going to be replacing the bordermanager server w/ a cisco pix
> router. It will act as a router to the internet and as a DHCP server.


Sorry to disappoint you, PIX can't be a router. It's a firewall.

> The routers address will be 192.168.1.1. I have everything working except
> that I have a subnet that gets its IP addresses from my file server. The
> subent is 192.168.2.0. The file servers ip address is 192.168.1.253. The
> file server gets it's ip from the router and is able to ping the router.
> Any pc on the 192.168.2.0 can not see the router but can ping the file
> server. I need the pc's on the subnet to be able to see the router so
> they can route through their to get their internet connection. What do I
> need to do.


How is the 192.168.2.x subnet connected to your LAN ?
Is it connected to the same switch as the 192.168.1.x subnet ?
If you have a single switch servicing multiple subnets, are you breaking
the switch into multiple VLANs or single VLAN ?



--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: subnet not seeing router

I guess I am using the term router incorrectly.

I have a fiber card in my file server which is connected to a switch. All
of the connections on that switch are given a 192.168.2.1 ip. I also have
another nic card in my main server that plugs into my "main" switch. The
pix's router is also plugged into this switch. I guess what I am hoping
to accomplish is that if my 192.168.2.1 subnet can see the pix it will go
out through it to get to the internet.


> On 8/8/2005 scramer@cusd3.com wrote:
>
> > I am going to be replacing the bordermanager server w/ a cisco pix
> > router. It will act as a router to the internet and as a DHCP server.

>
> Sorry to disappoint you, PIX can't be a router. It's a firewall.
>
> > The routers address will be 192.168.1.1. I have everything working

except
> > that I have a subnet that gets its IP addresses from my file server.

The
> > subent is 192.168.2.0. The file servers ip address is 192.168.1.253.

The
> > file server gets it's ip from the router and is able to ping the

router.
> > Any pc on the 192.168.2.0 can not see the router but can ping the file
> > server. I need the pc's on the subnet to be able to see the router so
> > they can route through their to get their internet connection. What

do I
> > need to do.

>
> How is the 192.168.2.x subnet connected to your LAN ?
> Is it connected to the same switch as the 192.168.1.x subnet ?
> If you have a single switch servicing multiple subnets, are you breaking
> the switch into multiple VLANs or single VLAN ?
>
>
>
> --
> Edison Ortiz
> Novell Product Support Forum SysOp
> (No Email Support, Thanks !)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: subnet not seeing router

On 8/8/2005 scramer@cusd3.com wrote:

> I have a fiber card in my file server which is connected to a switch. All
> of the connections on that switch are given a 192.168.2.1 ip. I also have
> another nic card in my main server that plugs into my "main" switch. The
> pix's router is also plugged into this switch. I guess what I am hoping
> to accomplish is that if my 192.168.2.1 subnet can see the pix it will go
> out through it to get to the internet.


All devices in the 192.168.2.x should have the default gateway pointing
to the IP address of the NetWare server connected on that segment.
At the server, enable IP Routing within INETCFG
In the PIX, you need to have a 'route add' for the 192.168.2.x network
& the gateway on that route add should be the server NIC on 192.168.1.x
segment. Also in the PIX, you need to include the 192.168.2.x network
in the global NAT command.



--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.