Re: SBS and 2 NICs

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



yes, I've also seen equipment that wouldn't work with 10.whatever/24. Must
admit, it has ben a while since I've experienced the problem, but that's
probably as much because 'I don't go there'.

Look at it enough and 192.168.16.x is enough different to 192.168.160.x, I
think my mind simply masks of it's own accord :-)

"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:uiZPfuXRIHA.1188@xxxxxxxxxxxxxxxxxxxxxxx
Kevin,

Just some feedback. I agree with you that 16 sometimes leads to confusion.
But we had several routing issues with 10.0.x subnets in more complex
networks at different clients. Even if the subnet mask is set to a C class
some older software tends to interpret it as an A class. Although we could
never figure out the exact reason, as soon as we switched them to a
192.168.x those issues went away. Based on that we normally now use
192.168.200.x for the internal subnet and never had an issue.

--
Claus
"Kevin Weilbacher" <kw@xxxxxxxxxxxxxxxxxxx> wrote in message
news:2096B7DB-954D-4AB2-BCB9-F0ECB17CF0D9@xxxxxxxxxxxxxxxx
Your Public NIC should be connected to your DSL modem/router. The DSL
modem should have both a WAN and LAN IP address listed. For a Linksys,
for example the LAN IP is usually set to 192.168.1.1. In which case I set
the IP address for the Public NIC to 192.168.1.2

Your Private NIC should be connected to a switch -- the same switch all
your internal workstations are connected to. You want to make your IP
range different than what you used for the Public NIC. Some people will
use 192.168.16.x.

For me personally, the 192.168.16.x range is too close (visibily
speaking) to the 192.168.1.x range for the Public NIC. So I generally
prefer to use a 10.0.x.x range so that it is visibly different.

--
Kevin Weilbacher [SBS MVP]
"The days pass by so quickly now, the nights are seldom long"
*

"JD" <JD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1CADDB43-3659-4FC4-8310-C28771013F4C@xxxxxxxxxxxxxxxx
OK I am at the end of my limited knowledge. I have a SBS with 2 NICs
and I
just can't seem to get it working. It is killing me...

Private NIC
192.168.1.200
DSL Modem 63.224.85.150

Public NIC
address as assigned by ISP

I am stuck!! I will read if I can find anything that will show me what
I am
doing wrong.





.



Relevant Pages

  • Re: [SLE] DSL problem
    ... If the DSL modem ... assigned a valid external IP by the ISP and then route IPs in your subnet to ... the inet facing NIC in your firewall box or alternately to a hub/switch. ... private IPs on the lan to the internet. ...
    (SuSE)
  • Re: SBS and 2 NICs
    ... The DSL modem should have both a WAN and LAN IP address listed. ... for example the LAN IP is usually set to 192.168.1.1. ... Your Private NIC should be connected to a switch -- the same switch all your internal workstations are connected to. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS and 2 NICs
    ... 192.168.200.x for the internal subnet and never had an issue. ... modem should have both a WAN and LAN IP address listed. ... Your Private NIC should be connected to a switch -- the same switch all ... DSL Modem 63.224.85.150 ...
    (microsoft.public.windows.server.sbs)
  • Re: Active Directory New Site
    ... Would it be as simple as putting the router between the existing switch, ... Sites and Services to create a new site, then inside that, the server ... and subnet object for that server? ... VLAN and then physically link into that VLAN somehow? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Adjunto 24k ! Error conexión remota 2003 SBS
    ... "David" schreef in bericht ... > He habilitado la conexión remota de sbs 2003 para trabajadores que acceden ... > Servidor 2003 SBS con 1 tarjeta de red, IP de clase C, conectada a switch ... > Internamente desde Lan funciona todo a las 1000 maravillas. ...
    (microsoft.public.windows.server.sbs)