Re: NAT on SBS2003 not working

From: Randall Arnold (rgarnold_at_cathartis.com_)
Date: 06/14/04 

Date: Mon, 14 Jun 2004 18:00:52 -0500

Thanks, Tony, and I actually tried that. I stripped everything down to
brass tacks after the first failed attempt at NAT. Got internet connection
working via PPPoE to DSL: modem, then started using wizards again to enable
NAT. No go. Tried again-- still no go. After that was when I tried the
info in the MSKB-- again no go. After that, I brought the issue here.
Nothing has worked.

Randall Arnold

"Tony Su" <anonymous@discussions.microsoft.com> wrote in message
news:1c00501c45229$fd6c81a0$a301280a@phx.gbl...
> Randall,
> Another suggestion here.
>
> Assume from what you describe you're dealing with an SBS
> Standard configuration (even if you eventually decide to
> add Premium components later).
>
> I wonder about your original IPCONFIG, the
> autoconfiguration setting... Would it be expected to be
> configured with a 169.xxx.xxx.xxx address? - I think not.
>
> So, I recommend you simplify what you're looking at... and
> <forget> about NAT, clients, etc.
>
> Deal with only your Internet Connection... You probably
> have two main approaches... to configure using your PPoE
> device instructions or the SBS CEICW. I highly recommend
> trying the SBS CEICW first.
>
> After that, test your most basic network connectivity
> first... ping the ISP default gateway and DNS. Only after
> you can do that successfully, move on to any other
> functions.
>
> IMO.
>
> Good Luck,
> Tony Su
>
>
>
>
>
>
> >-----Original Message-----
> >Thanks Gumby. To answer your questions:
> >
> >-Gave up on ICS. Mariana says it's not available on
> SBS2003 (!!!), even
> >though Help claims it is. Typical Microsoft.
> >
> >-Former setup was 3 workstations (no server) accessing
> internet via SMC
> >Barricade SMC7004ABR (a great little router until it
> crapped out). Server
> >added to network very recently; I've been converting
> workstations over to
> >roaming profiles. All PCs and server were succesful
> accessing internet
> >through SMS switch to SMC router to ZyXel DSL modem. SMC
> router set itself
> >up as 192.168.2.1 and was also providing DHCP-- I
> switched this to SBS2003
> >box when it was introduced to LAN. No problems in that
> areas; transition
> >was seamless. I setup SBS2003 box (fs1) as 192.168.2.199
> since this was
> >outside the router's range at the time.
> >
> >-I will follow your advice on external NIC.
> >
> >-Something I did caused DHCP service to die, and refuse
> to restart. Error
> >claims another server has same IP. I don't see how.
> Regardless, I'll give
> >this *one last shot* before giving up and scrapping this
> install. It's
> >giving me enormous headaches over this stupid NAT
> business, which I thought
> >would be a piece of cake. Problem is every procedure I
> find conflicts with
> >other procedures of the same goal and I'm sure that in
> going from one failed
> >effort to another I've truly mucked this box up. I'm
> also having trouble
> >with SMTP (another story) so I'm beyond frustrated at the
> moment. Sigh.
> >
> >Thanks,
> >
> >Randall Arnold
> >
> >
> >"SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
> >news:ufHoU8ZUEHA.760@TK2MSFTNGP12.phx.gbl...
> >> Hi Randall,
> >>
> >> you seem to be having a much harder time of this
> than you should.
> >>
> >> FORGET THE TERM ICS and undo whatever you have
> attempted to do along
> >> those lines.
> >>
> >> It seems you previously had a couple of
> workstations accessing the
> >> internet through an ADSL modem/router (single device,
> right?) which model?
> >I
> >> note you mention an SMC Barricade.
> >>
> >> your old config would have been
> >>
> >> ADSL Public IP
> >> modem/router LAN IP 192.168.2.something/255.255.255.0
> (please confirm the
> >> IP)
> >> |
> >> |
> >> switch or ports on router
> >> |
> >> |
> >> couple of PC's in 192.168.2.x space
> >>
> >> you need to change this and as you have the router
> available I suggest you
> >> want:
> >>
> >> ADSL Public IP
> >> modem/router LAN IP 192.168.3.1/255.255.255.0
> >> (NOTE: change of router IP subnet)
> >> |
> >> |
> >> SBS External NIC 192.168.3.2/255.255.255.0
> >> SBS Internal NIC 192.168.2.199/255.255.255.0
> >> |
> >> |
> >> network switch
> >> |
> >> |
> >> client PC's
> >>
> >> How close to this are you currently?
> >>
> >> If you do this you want to set the external IP of SBS
> manually, it doesn't
> >> matter whether DHCP is enabled on the router.
> >> You DO NOT need, or want, RASPPPoE on the server,
> remove it. The router
> >will
> >> look after the ADSL connection, same as it did for your
> workgroup.
> >>
> >>
> >>
> >> "Randall Arnold" <rgarnold@cathartis.com_> wrote in
> message
> >> news:uoyRDeZUEHA.644@tk2msftngp13.phx.gbl...
> >> > Well, I've run that wizard three times so far, and it
> hasn't done the
> >> trick.
> >> > :(
> >> >
> >> > I'm starting to think my MCSE brother gave me bad
> advice on the NIC
> >going
> >> to
> >> > the DSL modem-- he said let it get an IP from
> earthlink. However, I
> >pored
> >> > through some books today and they all agree that the
> NIC IP should be
> >> within
> >> > the same range as those provided by local DHCP (I'm
> using class 3
> >> > addresses). So I'll be changing that next.
> >> >
> >> > I'm also perplexed at why ICS isn't showing. The
> book I bought (Teach
> >> > yourself Windows Server 2003) goes into decent detail
> and explains that
> >> > there are three methods of sharing the connection:
> ICS, NAT and ISA
> >Server
> >> > (in order of lower to greater security). I would
> like to test ICS since
> >> > it's the easiest to configure, but it isn't even
> available on my server
> >> > right now. I'm going to check the installed
> components next and see if
> >> > that's where the problem lies, but there's skimpy
> info on ICS in every
> >> book
> >> > I've seen (and the Help) so if that's not the case
> I'm stumped. ISA
> >> Server
> >> > is never mentioned in any book I've seen so far that
> even addresses home
> >> > offices. In fact, that's what I'd really like to
> find: a big fat book
> >on
> >> > using SBS2003 in a home office environ. Maybe I'll
> check Amazon... but
> >> I'd
> >> > sure like to get this shared network back up tonight!
> >> >
> >> > Randall Arnold
> >> >
> >> > "Susan Bradley, CPA aka Ebitz SBS Rocks [MVP] "
> <sbradcpa@pacbell.net>
> >> wrote
> >> > in message
> news:#GtIw4WUEHA.2544@TK2MSFTNGP10.phx.gbl...
> >> > > That's a Windows 2003 article. You are running the
> internet
> >connection
> >> > > wizard right? It does all this stuff for you.
> >> > >
> >> > >
> >> > > Forget that KB and follow the CEICW wizard [see the
> connect to the
> >> > > internet wizard under the to do list?]
> >> > >
> >> > > Forget this KB... throw it out the window. You
> don't need this. Run
> >> > > the wizard.
> >> > >
> >> >
> >>
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;324264&Product=sbserv2003
> >> > >
> >> > > Randall Arnold wrote:
> >> > >
> >> > > > Yeah, Frank, that's the setup I had before-- like
> I said, the modem
> >> died
> >> > a
> >> > > > couple of days ago and I'm scrambling to get
> something working now.
> >> > > >
> >> > > > The comunication between NIC and DSL: modem isn't
> an issue. In
> >fact,
> >> > right
> >> > > > after logging in after reboot I'm conencted (it's
> that seamless).
> >> From
> >> > the
> >> > > > server I can access the internet and newsgroups
> just fine
> >(obviously--
> >> > lol).
> >> > > > It's just that the clients aren't seeing the
> server's connection.
> >> > > >
> >> > > > I swear I've followed Microsoft's instructions as
> correctly as I can
> >> > figure.
> >> > > > There are a few places where their steps omit
> some detail that may
> >or
> >> > may
> >> > > > not be crucial (such as the vague instructions
> regarding DNS
> >> forwarders:
> >> > > > "type ANY remote IP address")-- I don't know.
> But the setup Susan
> >> > provided
> >> > > > is vastly different than what's in the MSKB and
> Help (main KB
> >article
> >> is
> >> > > > 324264). I had an SBS2000 Best Practices book
> that covered this in
> >> > great
> >> > > > detail, but a former employer kept it.
> >> > > >
> >> > > > I'll try Susan's method today and see how that
> goes. Thanks.
> >> > > >
> >> > > > Randall Arnold
> >> > > >
> >> > > > "Frank McCallister"
> <anonymous@discussions.microsoft.com> wrote in
> >> > message
> >> > > > news:#ncVfyVUEHA.2988@TK2MSFTNGP10.phx.gbl...
> >> > > >
> >> > > >>Hi Randall
> >> > > >>
> >> > > >>I have had some difficulty with PPPoE connections
> direct from server
> >> NIC
> >> > > >
> >> > > > to
> >> > > >
> >> > > >>DSL modem due to timing errors on server restart
> with connection
> >being
> >> > > >>established quick enough. Note the time and do a
> server restart.
> >Look
> >> in
> >> > > >
> >> > > > the
> >> > > >
> >> > > >>event viewers for any Binding errors after the
> restart. I always put
> >> an
> >> > > >>inexpensive router between the DSL modem and the
> NIC for two
> >purposes.
> >> > It
> >> > > >>maintains the DSL connection during restarts and
> it gives your
> >> External
> >> > > >
> >> > > > NIC
> >> > > >
> >> > > >>a static IP address. It can also provede some
> additional Firewall
> >> > > >
> >> > > > protection
> >> > > >
> >> > > >>but you have to be careful with ports in that
> case.
> >> > > >>
> >> > > >>Frank
> >> > > >>"Randall Arnold" <rgarnold@cathartis.com_> wrote
> in message
> >> > > >>news:ey5cwRRUEHA.4048@TK2MSFTNGP12.phx.gbl...
> >> > > >>
> >> > > >>>First one is the external NIC. Second one is
> the actual PPPOE
> >> > > >
> >> > > > connector.
> >> > > >
> >> > > >>I
> >> > > >>
> >> > > >>>found it strange that I needed it setup this
> way, but internet
> >access
> >> > > >>>wouldn't work any other way. Both internal and
> external NIC
> >> connectors
> >> > > >>
> >> > > >>were
> >> > > >>
> >> > > >>>established during Windows Setup, and the
> broadband (pppoe)
> >connector
> >> > > >
> >> > > > was
> >> > > >
> >> > > >>>setup by the email & internet connection
> wizard. Once the
> >Broadband
> >> > > >>>connector was setup, internet access was
> immediately available. I
> >> then
> >> > > >>>continued following the MSKB instructions for
> routing and NAT but,
> >as
> >> > > >>
> >> > > >>noted,
> >> > > >>
> >> > > >>>no access was available to clients when I was
> done even though the
> >> > > >
> >> > > > server
> >> > > >
> >> > > >>>had full access.
> >> > > >>>
> >> > > >>>I looked at your diagram for 2 NICs, ISA,
> RasPPPOE and no router
> >(my
> >> > > >>>situation) and see several differences between
> it and what the MSKB
> >> and
> >> > > >>>SBS2003 Help articles were recommending.
> Tomorrow I'll scrap this
> >> > third
> >> > > >>>attempt at doing it the Microsoft way and give
> your method a try.
> >> I'm
> >> > > >>>surprised at the need for RasPPPOE given that
> the capability is
> >> > built-in
> >> > > >>
> >> > > >>to
> >> > > >>
> >> > > >>>SBS2003 but maybe it's the built-in service
> that's the culprit
> >here.
> >> > Am
> >> > > >
> >> > > > I
> >> > > >
> >> > > >>>correct in assuming the NAT stuff isn't needed
> with your setup?
> >> > > >>>
> >> > > >>>Thanks,
> >> > > >>>
> >> > > >>>Randall Arnold
> >> > > >>>
> >> > > >>>"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
> >> <sbradcpa@pacbell.net>
> >> > > >>>wrote in message
> news:#eb$fHRUEHA.2716@tk2msftngp13.phx.gbl...
> >> > > >>>
> >> > > >>>>Ethernet adapter DSL Modem Connection:
> >> > > >>>>
> >> > > >>>> Connection-specific DNS Suffix . :
> >> > > >>>> Description . . . . . . . . . . . :
> Macronix MX98715-Based
> >> > > >
> >> > > > Ethernet
> >> > > >
> >> > > >>>>Adapter (
> >> > > >>>>Generic)
> >> > > >>>> Physical Address. . . . . . . . . : 00-80-
> C6-F2-2B-6C
> >> > > >>>> DHCP Enabled. . . . . . . . . . . : Yes
> >> > > >>>> Autoconfiguration Enabled . . . . : Yes
> >> > > >>>> Autoconfiguration IP Address. . . :
> 169.254.233.231
> >> > > >>>> Subnet Mask . . . . . . . . . . . :
> 255.255.0.0
> >> > > >>>> Default Gateway . . . . . . . . . :
> >> > > >>>> DNS Servers . . . . . . . . . . . :
> 207.69.188.185
> >> > > >>>>
> 207.69.188.186
> >> > > >>>> NetBIOS over Tcpip. . . . . . . . : Disabled
> >> > > >>>>
> >> > > >>>>PPP adapter Small Business Broadband Connection
> 1:
> >> > > >>>>
> >> > > >>>> Connection-specific DNS Suffix . :
> >> > > >>>> Description . . . . . . . . . . . : WAN
> (PPP/SLIP) Interface
> >> > > >>>> Physical Address. . . . . . . . . : 00-53-
> 45-00-00-00
> >> > > >>>> DHCP Enabled. . . . . . . . . . . : No
> >> > > >>>> IP Address. . . . . . . . . . . . :
> 68.166.204.29
> >> > > >>>> Subnet Mask . . . . . . . . . . . :
> 255.255.255.255
> >> > > >>>> Default Gateway . . . . . . . . . :
> 68.166.204.1
> >> > > >>>> DNS Servers . . . . . . . . . . . :
> 207.69.188.185
> >> > > >>>>
> 207.69.188.186
> >> > > >>>> NetBIOS over Tcpip. . . . . . . . : Disabled
> >> > > >>>>
> >> > > >>>>What are those two?
> >> > > >>>>
> >> > > >>>>Randall Arnold wrote:
> >> > > >>>>
> >> > > >>>>>2 adapters (see original post). Thanks for
> the link-- I'll give
> >> > > >
> >> > > > that
> >> > > >
> >> > > >>>one a
> >> > > >>>
> >> > > >>>>>shot. I'm getting desperate...
> >> > > >>>>>
> >> > > >>>>>Randall Arnold
> >> > > >>>>>
> >> > > >>>>>"Susan Bradley, CPA aka Ebitz - SBS Rocks
> [MVP]"
> >> > > >>
> >> > > >><sbradcpa@pacbell.net>
> >> > > >>
> >> > > >>>>>wrote in message
> news:O5U3F9QUEHA.3976@TK2MSFTNGP09.phx.gbl...
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>How many adapters are on this Server?
> >> > > >>>>>>
> >> > > >>>>>>And Mariette's site is offline right now...
> >> > > >>>>>>
> >> > > >>>>>>http://www.sbslinks.com/network.htm
> >> > > >>>>>>Try those pictures.... pick a 2 nic SBS 2000
> setup.
> >> > > >>>>>>
> >> > > >>>>>>Randall Arnold wrote:
> >> > > >>>>>>
> >> > > >>>>>>
> >> > > >>>>>>>Frank:
> >> > > >>>>>>>
> >> > > >>>>>>>I set the server high because it was a late
> addition to the
> >> > > >
> >> > > > network.
> >> > > >
> >> > > >>I
> >> > > >>
> >> > > >>>>>was
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>running 3 clients serviced by an SMC
> Barricade router with no
> >> > > >
> >> > > > server
> >> > > >
> >> > > >>at
> >> > > >>
> >> > > >>>>>all
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>and 2 networked printers. I recently built
> the server and
> >added
> >> it
> >> > > >>
> >> > > >>in;
> >> > > >>
> >> > > >>>>>I
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>selected .199 because it was well out of the
> range of IPs being
> >> > > >
> >> > > > used
> >> > > >
> >> > > >>at
> >> > > >>
> >> > > >>>>>the
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>time (I may change it though; I blocked out
> the lower 10
> >> numbers).
> >> > > >>
> >> > > >>The
> >> > > >>
> >> > > >>>>>SMC
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>router just bought the farm and I'm
> scrambling to get internet
> >> > > >
> >> > > > access
> >> > > >
> >> > > >>>>>back
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>to the clients, hopefully w/o buying another
> router... but
> >that's
> >> > > >>>>>
> >> > > >>>>>looking
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>doubtful right now.
> >> > > >>>>>>>
> >> > > >>>>>>>Server IPCONFIG as follows (note that I may
> have some portions
> >> > > >>>>>
> >> > > >>>>>misconfigured
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>due to experimentation when default settings
> wouldn't work):
> >> > > >>>>>>>
> >> > > >>>>>>>---------------------------------------------
> ------
> >> > > >>>>>>>Windows IP Configuration
> >> > > >>>>>>>
> >> > > >>>>>>> Host Name . . . . . . . . . . . . : fs1
> >> > > >>>>>>> Primary Dns Suffix . . . . . . . :
> cathartis.local
> >> > > >>>>>>> Node Type . . . . . . . . . . . . : Unknown
> >> > > >>>>>>> IP Routing Enabled. . . . . . . . : Yes
> >> > > >>>>>>> WINS Proxy Enabled. . . . . . . . : Yes
> >> > > >>>>>>> DNS Suffix Search List. . . . . . :
> cathartis.local
> >> > > >>>>>>>
> >> > > >>>>>>>PPP adapter RAS Server (Dial In) Interface:
> >> > > >>>>>>>
> >> > > >>>>>>> Connection-specific DNS Suffix . :
> >> > > >>>>>>> Description . . . . . . . . . . . : WAN
> (PPP/SLIP) Interface
> >> > > >>>>>>> Physical Address. . . . . . . . . : 00-53-
> 45-00-00-00
> >> > > >>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >> > > >>>>>>> IP Address. . . . . . . . . . . . :
> 192.168.2.11
> >> > > >>>>>>> Subnet Mask . . . . . . . . . . . :
> 255.255.255.255
> >> > > >>>>>>> Default Gateway . . . . . . . . . :
> >> > > >>>>>>> NetBIOS over Tcpip. . . . . . . . :
> Disabled
> >> > > >>>>>>>
> >> > > >>>>>>>Ethernet adapter Server Local Area
> Connection:
> >> > > >>>>>>>
> >> > > >>>>>>> Connection-specific DNS Suffix . :
> >> > > >>>>>>> Description . . . . . . . . . . . :
> Macronix MX987xx Family
> >> Fast
> >> > > >>>>>
> >> > > >>>>>Ethernet
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>Ada
> >> > > >>>>>>>pter
> >> > > >>>>>>> Physical Address. . . . . . . . . : 00-80-
> C6-F7-28-2C
> >> > > >>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >> > > >>>>>>> IP Address. . . . . . . . . . . . :
> 192.168.2.199
> >> > > >>>>>>> Subnet Mask . . . . . . . . . . . :
> 255.255.255.0
> >> > > >>>>>>> Default Gateway . . . . . . . . . :
> >> > > >>>>>>> DNS Servers . . . . . . . . . . . :
> 192.168.2.199
> >> > > >>>>>>> Primary WINS Server . . . . . . . :
> 192.168.2.199
> >> > > >>>>>>>
> >> > > >>>>>>>Ethernet adapter DSL Modem Connection:
> >> > > >>>>>>>
> >> > > >>>>>>> Connection-specific DNS Suffix . :
> >> > > >>>>>>> Description . . . . . . . . . . . :
> Macronix MX98715-Based
> >> > > >>
> >> > > >>Ethernet
> >> > > >>
> >> > > >>>>>>>Adapter (
> >> > > >>>>>>>Generic)
> >> > > >>>>>>> Physical Address. . . . . . . . . : 00-80-
> C6-F2-2B-6C
> >> > > >>>>>>> DHCP Enabled. . . . . . . . . . . : Yes
> >> > > >>>>>>> Autoconfiguration Enabled . . . . : Yes
> >> > > >>>>>>> Autoconfiguration IP Address. . . :
> 169.254.233.231
> >> > > >>>>>>> Subnet Mask . . . . . . . . . . . :
> 255.255.0.0
> >> > > >>>>>>> Default Gateway . . . . . . . . . :
> >> > > >>>>>>> DNS Servers . . . . . . . . . . . :
> 207.69.188.185
> >> > > >>>>>>>
> 207.69.188.186
> >> > > >>>>>>> NetBIOS over Tcpip. . . . . . . . :
> Disabled
> >> > > >>>>>>>
> >> > > >>>>>>>PPP adapter Small Business Broadband
> Connection 1:
> >> > > >>>>>>>
> >> > > >>>>>>> Connection-specific DNS Suffix . :
> >> > > >>>>>>> Description . . . . . . . . . . . : WAN
> (PPP/SLIP) Interface
> >> > > >>>>>>> Physical Address. . . . . . . . . : 00-53-
> 45-00-00-00
> >> > > >>>>>>> DHCP Enabled. . . . . . . . . . . : No
> >> > > >>>>>>> IP Address. . . . . . . . . . . . :
> 68.166.204.29
> >> > > >>>>>>> Subnet Mask . . . . . . . . . . . :
> 255.255.255.255
> >> > > >>>>>>> Default Gateway . . . . . . . . . :
> 68.166.204.1
> >> > > >>>>>>> DNS Servers . . . . . . . . . . . :
> 207.69.188.185
> >> > > >>>>>>>
> 207.69.188.186
> >> > > >>>>>>> NetBIOS over Tcpip. . . . . . . . :
> Disabled
> >> > > >>>>>>>--------------------------------------
> >> > > >>>>>>>
> >> > > >>>>>>>Test client 1 IPCONFIG:
> >> > > >>>>>>>
> >> > > >>>>>>>-------------------------------------
> >> > > >>>>>>>Windows IP Configuration
> >> > > >>>>>>>
> >> > > >>>>>>>Host Name . . . . . . . . . . . . : pc2
> >> > > >>>>>>>
> >> > > >>>>>>>Primary Dns Suffix . . . . . . . :
> cathartis.local
> >> > > >>>>>>>
> >> > > >>>>>>>Node Type . . . . . . . . . . . . : Hybrid
> >> > > >>>>>>>
> >> > > >>>>>>>IP Routing Enabled. . . . . . . . : No
> >> > > >>>>>>>
> >> > > >>>>>>>WINS Proxy Enabled. . . . . . . . : No
> >> > > >>>>>>>
> >> > > >>>>>>>DNS Suffix Search List. . . . . . :
> cathartis.local
> >> > > >>>>>>>
> >> > > >>>>>>>Ethernet adapter Local Area Connection:
> >> > > >>>>>>>
> >> > > >>>>>>>Connection-specific DNS Suffix . :
> cathartis.local
> >> > > >>>>>>>
> >> > > >>>>>>>Description . . . . . . . . . . . : SiS 900
> PCI Fast Ethernet
> >> > > >
> >> > > > Adapter
> >> > > >
> >> > > >>>>>>>Physical Address. . . . . . . . . : 00-0A-E6-
> B8-A8-4C
> >> > > >>>>>>>
> >> > > >>>>>>>Dhcp Enabled. . . . . . . . . . . : Yes
> >> > > >>>>>>>
> >> > > >>>>>>>Autoconfiguration Enabled . . . . : Yes
> >> > > >>>>>>>
> >> > > >>>>>>>IP Address. . . . . . . . . . . . :
> 192.168.2.82
> >> > > >>>>>>>
> >> > > >>>>>>>Subnet Mask . . . . . . . . . . . :
> 255.255.255.0
> >> > > >>>>>>>
> >> > > >>>>>>>Default Gateway . . . . . . . . . :
> 192.168.2.199
> >> > > >>>>>>>
> >> > > >>>>>>>DHCP Server . . . . . . . . . . . :
> 192.168.2.199
> >> > > >>>>>>>
> >> > > >>>>>>>DNS Servers . . . . . . . . . . . :
> 192.168.2.199
> >> > > >>>>>>>
> >> > > >>>>>>>Primary WINS Server . . . . . . . :
> 192.168.2.199
> >> > > >>>>>>>
> >> > > >>>>>>>Lease Obtained. . . . . . . . . . :
> Saturday, June 12, 2004
> >> 6:46:21
> >> > > >>
> >> > > >>PM
> >> > > >>
> >> > > >>>>>>>Lease Expires . . . . . . . . . . : Sunday,
> June 20, 2004
> >6:46:21
> >> > > >
> >> > > > PM
> >> > > >
> >> > >
> >> >
> >>
> >>>>-------------------------------------------------------
> ------------------
> >> > -
> >> > > >>>
> >> > > >>>>>--
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>--------
> >> > > >>>>>>>
> >> > > >>>>>>>I am also testing another WinXP client, but
> it's IP info is so
> >> > > >>
> >> > > >>bizarre
> >> > > >>
> >> > > >>>>>I'm
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>not even messing with it right now.
> >> > > >>>>>>>
> >> > > >>>>>>>I can't see anything in this list that would
> prevent the client
> >> > > >
> >> > > > from
> >> > > >
> >> > > >>>>>>>connecting. In fact, the client's info is
> virtually unchanged
> >> from
> >> > > >>>
> >> > > >>>when
> >> > > >>>
> >> > > >>>>>it
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>was workign with the hardware router
> (emphasis on "working").
> >> > > >>>>>>>
> >> > > >>>>>>>Hope this helps though...
> >> > > >>>>>>>
> >> > > >>>>>>>Randall Arnold
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>"Frank McCallister"
> <anonymous@discussions.microsoft.com> wrote
> >> in
> >> > > >>>>>
> >> > > >>>>>message
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>>>news:#GnwaWQUEHA.3988@tk2msftngp13.phx.gbl...
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>>Hi Randall
> >> > > >>>>>>>>
> >> > > >>>>>>>>Post your ipconfig /all from the server and
> one of your
> >> > > >>
> >> > > >>Workstations.
> >> > > >>
> >> > > >>>>>>>>Curious why you set your server so high an
> IP (.199) ?
> >> > > >>>>>>>>
> >> > > >>>>>>>>Frank McCallister
> >> > > >>>>>>>>COMPUMAC
> >> > > >>>>>>>>"Randall Arnold" <rgarnold@cathartis.com_>
> wrote in message
> >> > >
> >>>>>>>>news:uyBrqKQUEHA.2028@TK2MSFTNGP11.phx.gbl...
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>>Also, as I noted in another post, I get an
> error when trying
> >to
> >> > > >>>
> >> > > >>>connect
> >> > > >>>
> >> > > >>>>>>>to
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>>>that site:
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>DotNetNuke Upgrade Error
> >> > > >>>>>>>>>The Assembly Version ( [ASSEMBLYVERSION] )
> does not match the
> >> > > >>>
> >> > > >>>Database
> >> > > >>>
> >> > > >>>>>>>>>Version ( [DATABASEVERSION] )
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>ERROR: Could not connect to database.
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>SQL Server does not exist or access denied.
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>Continue
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>Randall Arnold
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>"Susan Bradley, CPA aka Ebitz - SBS Rocks
> [MVP]"
> >> > > >>>
> >> > > >>><sbradcpa@pacbell.net>
> >> > > >>>
> >> > > >>>>>>>>>wrote in message
> >news:uZgz2FQUEHA.2484@TK2MSFTNGP11.phx.gbl...
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>Let them pick up their DHCP address from
> the server. They
> >> > > >
> >> > > > aren't
> >> > > >
> >> > > >>>>>>>>>>pointing their DNS to the server and thus
> can't find the
> >> > > >
> >> > > > internet
> >> > > >
> >> > > >>>>>>>>>>www.smallbizserver.net is a great
> resource.
> >> > > >>>>>>>>>>
> >> > > >>>>>>>>>>Randall Arnold wrote:
> >> > > >>>>>>>>>>
> >> > > >>>>>>>>>>
> >> > > >>>>>>>>>>
> >> > > >>>>>>>>>>>I'm having the most difficult time
> trying to share my
> >> internet
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>connection on
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>Small Business Server 2003.
> >> > > >>>>>>>>>>>
> >> > > >>>>>>>>>>>I have the recommended 2 NICs, one for
> LAN and the other
> >> > > >>
> >> > > >>connected
> >> > > >>
> >> > > >>>>>>>to
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>>>the
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>DSL modem. The internet connection on
> the server works
> >> > > >>
> >> > > >>flawlessly.
> >> > > >>
> >> > > >>>>>>>I
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>>>used
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>the internet and router wizards to setup
> routing and NAT,
> >> > > >>
> >> > > >>following
> >> > > >>
> >> > > >>>>>>>>the
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>>>>instruction in the MSKB to the "T".
> However, my Windows XP
> >> > > >>
> >> > > >>clients
> >> > > >>
> >> > > >>>>>>>>can
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>>not
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>access the internet using the server as
> a gateway, even
> >> though
> >> > > >>
> >> > > >>they
> >> > > >>
> >> > > >>>>>>>>find
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>>it
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>on the LAN just fine.
> >> > > >>>>>>>>>>>
> >> > > >>>>>>>>>>>I have racked my brain on this, trying
> every possible
> >option
> >> I
> >> > > >>
> >> > > >>can
> >> > > >>
> >> > > >>>>>>>>think
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>>of,
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>but so far nothing has resolved this. I
> am on my third
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>uninstall/reinstall
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>of the required services and just about
> ready to trash the
> >> > > >
> >> > > > whole
> >> > > >
> >> > > >>>>>>>thing
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>>>out
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>of frustration. The clients accessed
> the internet just
> >fine
> >> > > >
> >> > > > when
> >> > > >
> >> > > >>I
> >> > > >>
> >> > > >>>>>>>>used
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>>a
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>hardware router; unfortunately it died
> and so I figured I'd
> >> > > >
> >> > > > give
> >> > > >
> >> > > >>>NAT
> >> > > >>>
> >> > > >>>>>>>a
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>>>shot
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>to see if it would do the trick as
> advertised. ICS does
> >not
> >> > > >>
> >> > > >>appear
> >> > > >>
> >> > > >>>>>>>to
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>>>be an
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>option, since (contrary to what's stated
> in Help) I can
> >find
> >> no
> >> > > >>
> >> > > >>way
> >> > > >>
> >> > > >>>>>>>to
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>>>>>enable it.
> >> > > >>>>>>>>>>>
> >> > > >>>>>>>>>>>Can anyone point me to a best practices
> guide that would be
> >> > > >>>>>>>>
> >> > > >>>>>>>>beneficial?
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>>So
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>far I haven't found much for SBS 2003,
> and even Microsoft's
> >> > > >
> >> > > > info
> >> > > >
> >> > > >>>>>>>>doesn't
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>>>>cover the topic thoroughly enough.
> >> > > >>>>>>>>>>>
> >> > > >>>>>>>>>>>Something that may be relevant: running
> Repair on the 2 NIC
> >> > > >>>>>>>>
> >> > > >>>>>>>>connections
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>>>>fails with an error that arp could not
> be updated. So far
> >I
> >> > > >
> >> > > > have
> >> > > >
> >> > > >>>>>>>>found
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>>>>nothing to resolve that. Also, running
> Repair on the NIC
> >> > > >>>
> >> > > >>>connecting
> >> > > >>>
> >> > > >>>>>>>>to
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>>the
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>DSL modem returns an error about DHCP,
> saying the address
> >was
> >> > > >>>>>>>
> >> > > >>>>>>>invalid
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>
> >> > > >>>>>>>>>(I'm
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>getting its address from the ISP as
> recommended). IMO,
> >local
> >> > > >>
> >> > > >>DHCP
> >> > > >>
> >> > > >>>>>>>>>shouldn't
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>even care about that NIC, so I'm lost on
> that one.
> >> > > >>>>>>>>>>>
> >> > > >>>>>>>>>>>Anyway, any and all advice appreciated!
> If I had the funds
> >> I'd
> >> > > >>>
> >> > > >>>just
> >> > > >>>
> >> > > >>>>>>>>buy
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>
> >> > > >>>>>>>>>a
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>>>new router but I need my shared 'net up
> before the funds
> >will
> >> > > >
> >> > > > be
> >> > > >
> >> > > >>>>>>>>>>>available...
> >> > > >>>>>>>>>>>
> >> > > >>>>>>>>>>>Randall Arnold
> >> > > >>>>>>>>>>>
> >> > > >>>>>>>>>>>
> >> > > >>>>>>>>>>
> >> > > >>>>>>>>>>--
> >> > > >>>>>>>>>>http://www.sbslinks.com/really.htm
> >> > > >>>>>>>>>
> >> > > >>>>>>>>>
> >> > > >>>>>>--
> >> > > >>>>>>http://www.sbslinks.com/really.htm
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>>
> >> > > >>>>--
> >> > > >>>>http://www.sbslinks.com/really.htm
> >> > > >>>
> >> > > >>>
> >> > > >>
> >> > > >
> >> > > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
> >
> >.
> >

Relevant Pages

  • Re: Outgoing POP3 email missing/lost/not received
    ... ISP's mail server instead of the domain name on the ... SUMMARY OF SETTINGS FOR CONFIGURE E-MAIL AND INTERNET ... Internet Connection Wizard. ... After the wizard completes, the following network connection ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Anyway the Server Ipconfig /all is this... ... Server Local Area Connection: ... Les Connor [SBS Community Member - SBS MVP] ... First Page of the Internet Connection Wizard, ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... I checked the binding order and the Server Local area connection is at the top. ... I should have been more clear about internet connection.. ... I wonder if I may have missed a firewall setting on the router as well. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN breaks after installing patches
    ... Now I understand that you are using the PPPoE connection and no router is ... a virtual network adapter will be ... 825763 How to configure Internet access in Windows Small Business Server ... Run the Change Server IP Address to change the internal IP address. ...
    (microsoft.public.windows.server.sbs)
  • Re: Non-domain connection problem
    ... Ethernet adapter Local Area Connection: ... Connection-specific DNS Suffix. ... I hard coded the DNS server to a known DNS on the internet: ... Again this had no effect on the ability to connect to the internet. ...
    (microsoft.public.windows.server.sbs)