Re: 2nd DHCP Scope?



In news:OLRstE3CGHA.740@xxxxxxxxxxxxxxxxxxxx,
Jack H <strangerx@xxxxxxxx> stated, which I commented on below:
> I think so.
>
> I only have one subnet. All the rest are different IP ranges
> depending on the location.
>
> I will make something like you are talking about.
>
> As far as the router, there is an eithernet port with the IP of
> 172.20.4.1. The serial port is 172.20.6.1 and that interfaces to the
> router on the .5.x at the other building.

Why would you connect a port configured on the .4 network to a switch on the
..6 network, unless that port is actually one of your VLAN ports???


>
> the firewall is a Fortigate 100.

Based on the drawing you emailed me, and which I may suggest to post it to
your website so others can follow the thread, here was my reply:
___________________________
I assume the default gate on the Dell Power Connect 5324 (172.20.4.33) is
172.20.4.1 in the middle of the drawing, but you have it shown twice??? You
should have just left it in the middle and connected a line to the boiler
room. Make sense? Drawings can make or break the understanding of an
infrastructure, hence my original confusion.

I assume the DHCP server at the top with the two scopes has connected with
an IP address on both the .4 and the .9 network and it's default gateway is
172.20.4.1.

The power connect 3048 (finance) has an IP of 172.20.9.4, but why does it
have a gateway of 4.1?? If the IT 5324 switch has the VLANs and one of the
VLANs is .9, then since it is connected to that port, it's gateway should be
9.1, assuming the VLAN port you configured on the 5324 is 9.1. Make sense?

Since the 5324 switch is directly connected to the .9 network, there is no
need to configure a static route to get to it since it is aware of it,
assuming you configured it properly. Make sense?

Did you post this to the groups too? I should post this to as well to keep
anyone else following the thread a chance to jump in and comment.

Ace


.



Relevant Pages

  • Re: discovering a service behind a nated network
    ... you could use nmap or some other port scanning program ... > SSH onto the firewall and try to access the server from there, ... > works then it could be the translation on the gateway device not working ... > Network Security Specialist ...
    (Security-Basics)
  • Re: Cannot connect with Enterprise Manager
    ... Your understanding is exactly right except that the gateway on the network ... Enterprise Manager, uses port 1061. ... >> I should also mention that I have no problem connecting to SQL server ...
    (microsoft.public.sqlserver.clients)
  • Re: Firewall trapping outbound probes to TCP 1120 from W2K gateway box
    ... it could be absolutely normal for your gateway computer ... Windows chooses an ephemeral port above 1024 as the source ... > I have a PC set up as an internet gateway for my small LAN. ... > network, never to external IPs. ...
    (microsoft.public.win2000.security)
  • RE: Printing from Win9x clients stops
    ... > and make sure this software does not interfere with SBS Server. ... > clients, please disable it and try again. ... Create a local printer and redirect the port to the network server. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003, ISA 2004
    ... ISA and IIS try listening on these two ports. ... by default the Web Proxy is listening on port 8080 ... of the local network adapter. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)