Re: DHCP server and netgear router problems

Tech-Archive recommends: Fix windows errors by optimizing your registry

OK. thanks for your help so far. I have made copies of all the suggestions
and attempted some of them with some limited success.
I think the issue is complicated by the fact that I have 2 problems that are
going to affect each other to a small degree once either one of them is
resolved.
I am going to go back to a very simple question first.

1. My DHCP doesnt configure correctly even when it is installed and active..
(following reinstallation and confirming it is the using the localsystem
account)
2. My Netgear ADSL modem/Router DG834GT cannot be accessed through IP
192.168.0.1 which is its default address. So i am currently using the old
hardware setup.

Basically, which problem should be addresed first to save encountering more
difficulties later. Currently having the router problem fixed is more of a
priority.
And trying to deal with 2 problems at once is really not helping my sunday
evening..

And should I have mentioned that the system was previously setup to use
workgroups.., by whoever used to manage it when it was running server 2003.


"/kj" wrote:

> > IP Address. . . . . . . . . . . . : 172.16.1.170
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 172.16.1.1
> > DNS Servers . . . . . . . . . . . : 172.16.1.1
> > Primary WINS Server . . . . . . . : 172.16.1.170
>
>
> The SBS server should be pointing to itself for DNS. It's not likely to be
> much help with the DHCP problem but it will resolve DNS problems.
>
> /kj
>
>
> "Paul" <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:92024164-C0D9-4DF3-B397-7F9CA5797493@xxxxxxxxxxxxxxxx
> > C:\Documents and Settings\Administrator>ipconfig/all
> >
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : server
> > Primary Dns Suffix . . . . . . . : grahamdack.local
> > Node Type . . . . . . . . . . . . : Unknown
> > IP Routing Enabled. . . . . . . . : Yes
> > WINS Proxy Enabled. . . . . . . . : Yes
> > DNS Suffix Search List. . . . . . : grahamdack.local
> >
> > Ethernet adapter Server Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Network
> > Connection
> > Physical Address. . . . . . . . . : 00-0F-1F-64-16-C3
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 172.16.1.170
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 172.16.1.1
> > DNS Servers . . . . . . . . . . . : 172.16.1.1
> > Primary WINS Server . . . . . . . : 172.16.1.170
> >
> > C:\Documents and Settings\Administrator>
> >
> > Originally they had windows server 2003 installed. When they upgraded to
> > SBS2003 they had the option of installing SBS2003 DHCP server as part of
> > the
> > setup process. It appears during setup that they declined to do so.....
> >
> > Paul
> >
> >
> >
> >
> > "Merv Porter [SBS-MVP]" wrote:
> >
> >> And can you explain more about:
> >>
> >> > The first is that when they upgraded from server 2003 they opted to
> >> > keep
> >> > the existing setup instead of installing the SBS DHCP,
> >>
> >> --
> >> Merv Porter [SBS MVP]
> >> ===================================
> >>
> >> "Paul" <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:5F70308A-B515-418C-B614-9B558ECA8C6E@xxxxxxxxxxxxxxxx
> >> >I have recently walked into a company that has just installed small
> >> >business
> >> > server 2003. I have 2 problems which may be related. The first is that
> >> > when
> >> > they upgraded from server 2003 they opted to keep the existing setup
> >> > instead
> >> > of installing the SBS DHCP, this has caused numerous problems
> >> > connecting
> >> > clients to the domain and connecting to companyweb clearly. After many
> >> > attempts and much time on these forums and using the SBS 2003
> >> > Administrators
> >> > companion from Microsoft, the server still refuses to configure DHCP
> >> > for
> >> > SBS2003 correctly and always defaults back to its old settings even
> >> > though
> >> > the service has been shut down repeatedly and the scope has been set up
> >> > fpr
> >> > the new DHCP. This is really driving me crazy.
> >> > I have downloaded many many guides from microsoft and from these forums
> >> > on
> >> > how this should be corrected but all with no result. Either this server
> >> > is
> >> > just plain evil or I have missed something stupidly obvious along the
> >> > way.
> >> > What I really need is a step by step guide to performing this change
> >> > specifically for SBS2003. (I am not new to window server software in
> >> > general
> >> > but I admit SBS2003 is somewhat new to me).
> >> >
> >> > My second issue is that we currently use an adsl modem and a seperate
> >> > vpn
> >> > router/firewall device.
> >> > Due to requirements of the company that supplies some of our specialist
> >> > legal software we planned on replacing those items with a netgear
> >> > DG834GT
> >> > ADSL router as they have a conflict with our current hardware (d-link
> >> > router
> >> > - ok and wire2 adsl modem - the problem hardware)
> >> > However SBS refuses to connect to the netgear router (it is the same
> >> > model
> >> > we use for our remote VPN connections at the remote end and we have
> >> > never
> >> > had
> >> > a problem with either setting it up or using it).
> >> > We have contacted them and searched for weeks for a solution to these
> >> > problems and although we have received a lot of advice and 'how to'
> >> > troubleshooting guides none of them have yet solved our problem.
> >> > I would really like to hear from anyone that has actually solved either
> >> > of
> >> > these problems themselves or anyone that can provide a link or
> >> > information
> >> > that has ALL the steps necessary to complete this task.
> >> > I know this should not be this difficult and it is probably something
> >> > obvious that has been overlooked. Unfortunately the person who used to
> >> > manage
> >> > this server left no documentation about anything they did here,
> >> > settings/password lists/ nothing. We have pretty much had a nightmare
> >> > from
> >> > day 1.
> >> > If you require any further info about the system or setup please ask.
> >> > Thanks a lot in advance for any help you may offer.
> >> >
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: Domain Controller Down
    ... I am guessing you are correct about the 'tweaking', as this was setup a long ... I don't know enough about how to setup DNS, but it looks to me like there is ... The Domain Name System name recommendations for Small Business Server 2000 ... Ethernet adapter Local Area Connection: ...
    (microsoft.public.backoffice.smallbiz2000)
  • Configuring Active Directory & DNS
    ... Ok, I installed Windows Server 2003 Standard, activated Windows, no problems ... Configured printer, and setup the PrintServer, no problems there. ... needs DNS, so I let it automatically setup DNS. ...
    (microsoft.public.windows.server.active_directory)
  • DNS / Domain issues?
    ... Ok, I installed Windows Server 2003 Standard, activated Windows, no problems ... Configured printer, and setup the PrintServer, no problems there. ... needs DNS, so I let it automatically setup DNS. ...
    (microsoft.public.windows.server.dns)
  • Re: Single NIC DNS problem
    ... If the DHCP on the SBS is properly setup with the CEICW it should only be ... Your client is showing an additional IP of 192.168.1.1 ... I have a new Dell server preconfigured with SBS 2003. ... Ethernet adapter Server Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: How to configure for Two different IP subnets
    ... Active Directory will go haywire in a setup like that. ... AD integrates with the local DNS, so you cannot use the DNS at your ISP ... With Server 2003 Standard ... for its internal interface (ie the VPN endpoint). ...
    (microsoft.public.windows.server.networking)