Re: DNS problem, clients can't connect
From: Phydeux (phydeux_at_phydeux.com)
Date: 05/19/04
- Next message: clevere: "Re: ISA + 403 errors"
- Previous message: James: "Companyweb's data"
- In reply to: Les Connor [SBS MVP]: "Re: DNS problem, clients can't connect"
- Next in thread: Marina Roos [SBS-MVP]: "Re: DNS problem, clients can't connect"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 May 2004 21:24:49 -0400
Well, I got it up and running like clockwork. It required reformatting
and reinstalling followed by using the default settings. Here's the "tree"
now:
DSL modem (local IP 10.133.135.225)
||
Server (external IP 10.133.135.226 DHCP, internal IP 192.168.16.2)
||
Switch
||
Clients (192.168.16.10+)
But of course not everything could go perfectly. But that's how these
things go. :) Nothing I can't handle. Thanks everyone for the help. The
advice given was invaluable.
"Les Connor [SBS MVP]" <les.connor@DEL.cfive.ca> wrote in message
news:OAPa5IPPEHA.3096@TK2MSFTNGP09.phx.gbl...
> If you turn off dhcp on the router and let the sbs do it as designed, your
> life will be sweet :-).
>
> --
> Les Connor [SBS MVP]
> -------------------------------------
> SBS Rocks !
>
>
>
> "Phydeux" <phydeux@phydeux.com> wrote in message
> news:%230cDjHOPEHA.3264@tk2msftngp13.phx.gbl...
> > That's how we've been doing it, they give me leeway to disconnect them.
> > Turning off the DHCP within the DSL modem is a possibility via Telnet,
but
> > tedious. Plus the client's workstations would likely detect the DHCP
> server
> > within the server and change their IPs to suit, effectively cutting
> everyone
> > off from one another THAT way. So yeah, I have to play a bit of a
> balancing
> > act.
> >
> > I kinda wish I could hook up one of their spare DSL modems without
> > connecting it to the internet to act as an internal DHCP. But without
> > training up to a DSLAM it won't give out IPs.
> >
> > Anyhow, I'm off to their office, more details later if the tips thus far
> > don't pan out.
> >
> > "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in
> message
> > news:%23e85ztLPEHA.1312@TK2MSFTNGP12.phx.gbl...
> > > Users don't get knocked of just like that. You will have to make sure
> the
> > > dsl-modem has its dhcp-server turned off before you connect the sbs
> > server.
> > > If you can't work on this problem after working hours, the client will
> > have
> > > to give in a bit and give you the opportunity to get everything
> connected
> > > the way it should.
> > >
> > > --
> > > Regards,
> > >
> > > Marina
> > > Microsoft SBS-MVP
> > >
> > > "Phydeux" <phydeux@phydeux.com> schreef in bericht
> > > news:uxuK6XJPEHA.1392@TK2MSFTNGP09.phx.gbl...
> > > > I will be at my client's tomorrow and Wednesday to hopefully get
this
> > > > resolved. I've tried using the Change IP wizard before, but
tomorrow
> I
> > > plan
> > > > to do so again and set it to 192.168.16.1 as per Alun's tips. I
will
> > also
> > > > try to post the ipconfig /all for the server tomorrow as well.
> > > >
> > > > The biggest problem in all this has been testing the server without
> > > > disrupting their existing peer-to-peer workgroup. While they do
have
> a
> > > > 24-port switch downstream of their DSL modem, the modem is only
> allowed
> > to
> > > > give out 5 IPs, so if I hook up the server I either knock someone
off
> > the
> > > > network, or have to take them off the internet entirely, but this
> > > > disconnects everyone from one another and brings office productivity
> to
> > a
> > > > standstill (and gets me a lot of nasty looks).
> > > >
> > > > Though they do have one client I can hook up to the server directly
> via
> > a
> > > > 5-port switch they have lying around. But this configuration can
only
> > be
> > > > done without the internet, otherwise I'd have to knock someone off
the
> > > > network in order to get their DHCP spot.
> > > >
> > > > "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in
> > > message
> > > > news:%23h6Rh%23BPEHA.1620@TK2MSFTNGP12.phx.gbl...
> > > > > Have you tried my suggestion by using the Change IP wizard from
the
> > > > > Servermanagement console?
> > > > >
> > > > > --
> > > > > Regards,
> > > > >
> > > > > Marina
> > > > > Microsoft SBS-MVP
> > > > >
> > > > > "Phydeux" <phydeux@phydeux.com> schreef in bericht
> > > > > news:%23QiueXBPEHA.1340@TK2MSFTNGP12.phx.gbl...
> > > > > > Its not that I don't have a clue, its that my knowledge has
gaps.
> I
> > > > tend
> > > > > to
> > > > > > learn the best by actually doing. Sitting through lectures and
> > theory
> > > > > > lessons does me no good. Getting out there and doing, that's
much
> > > more
> > > > my
> > > > > > style. And my client is fine with this. He and I go way back
and
> > he
> > > > > knows
> > > > > > that while I know most things front to back, there are spots
where
> I
> > > > need
> > > > > to
> > > > > > learn a bit more. As it is, I understand DHCP and DNS, I just
> don't
> > > > > > understand internal/external addressing and the intricacies of
> > > routing.
> > > > > > Forgive me if I don't follow the same path to enlightenment
> everyone
> > > > else
> > > > > > did. But right now I'm simply trying to understand why the
client
> > > > > computers
> > > > > > can't see the server. Once I get a clue to figure that out, the
> > > > > > underpinnings of why that happened will be apparent and my
> knowledge
> > > > that
> > > > > > much greater. So, can ya give me a hint?
> > > > > >
> > > > > > "Molnir" <molnir@hotmail.comNoSpam> wrote in message
> > > > > > news:d87d01c43ab4$fbeb4280$a101280a@phx.gbl...
> > > > > > >
> > > > > > > >-----Original Message-----
> > > > > > > >Unfortunately that's not an option. I have neither the
> > > > > > > funds or resources
> > > > > > > >to hire someone else, and I'd rather not lose this
> > > > > > > account by failing to get
> > > > > > > >this server up and running. Do you think correcting the
> > > > > > > IP address of the
> > > > > > > >server will resolve the matter? Or would you prefer to
> > > > > > > further insult my
> > > > > > > >already obvious ignorance in this area?
> > > > > > >
> > > > > > > Let me make sure that I understand this correctly... You
> > > > > > > don't have a clue about the difference between public and
> > > > > > > private IP addressing, routing, DNS, DHCP, the basics of
> > > > > > > the OSI model, and you have never worked with servers
> > > > > > > before? Then you have the nerve to say that you don't
> > > > > > > want to lose your account because you can't get this to
> > > > > > > work? How can you possibly be charging a client to do
> > > > > > > something for them when you don't know even the
> > > > > > > elementary concepts?
> > > > > > >
> > > > > > > Take Mark's advice, hire a professional, and start
> > > > > > > studying.
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: clevere: "Re: ISA + 403 errors"
- Previous message: James: "Companyweb's data"
- In reply to: Les Connor [SBS MVP]: "Re: DNS problem, clients can't connect"
- Next in thread: Marina Roos [SBS-MVP]: "Re: DNS problem, clients can't connect"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
