Re: DHCP server and netgear router problems

I don't know if this is related to your problem, but I will relate an
experience similar in that an SBS (Premium) server would not connect to
Netgear routers (both FVM and FVS series). The system in question had ADSL
with a static IP, but the static IP was via a NATed DSL modem. ISA (both
2000 and 2004) would not allow the system to see the Netgear. I solved the
problem only by having the ADSL recofigured to supply a block of routable
IPs. The DSL Modem was set up to use one of the IPs as a gateway, and the
server External connecton used another of the IPs as its external address.
Once rid of the double NATing, the server could see the Netgear, and
everything else worked fine.

Re your DHCP issue--two things to check you may have overlooked: Is there a
hosts/lmhosts file? Is the DHCP set up to use DHCP reservations?

GaryK

"Paul" <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1B7692E4-EE6C-48CE-A560-1E15FA18DE5F@xxxxxxxxxxxxxxxx
> It has no difficulty connecting to any of the workstation computers.
> It only refuses to connect via the server.
>
> "Gary Karasik" wrote:
>
>> Can you connect to the Netgear router at 192.168.0.1 if you wire it
>> directly
>> to a workstation and set the workstation IP address to 192.168.0.2?
>>
>> GaryK
>>
>> "Paul" <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:B37653B1-6B16-4774-BA17-7D588B82722C@xxxxxxxxxxxxxxxx
>> > The netgear problem is that when the new hardware is installed it
>> > should
>> > default (after software installation) so you can access the router
>> > setup
>> > at
>> > IP 192.168.0.1. Even if you manually set it up to do so it refuses to
>> > connect
>> > and then defaults back to the old settings.
>> > I am currently using the old hardware setup but it is important that it
>> > is
>> > changed asap.
>> >
>> > 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: HP ML350 G5 SERVER + WINDOWS SBS 2003 R2 SP2
    ... This is the ipconfig from another workstation in the network. ... If you see the first attached file, it was the server and another ... workstation DHCP config, ...
    (microsoft.public.windows.server.sbs)
  • Re: DHCP not working right after server restore from backup
    ... The whole problem seemed to be linked to old information in both DHCP and ... But from your message (the part about the DNS) I got the bright idea ... Make sure you do not test from just one workstation. ... from the server then I know thew network is goofed up. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... Yeah, maybe it's not that different from the Netgear, for all that. ... that when I first used the Netgear router with SBS 2003, ... tech spend 4+ hours on my system, and then tell me to enable DHCP ... more than one SBS server in a company makes no sense. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... I've thrown quite a bit at them, and just have to disagree that they are inherently less secure than the netgear. ... setup DHCP and I have also gone in and manually created a new scope ... when I first used the Netgear router with SBS 2003, ... than one SBS server in a company makes no sense. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... The netgear has a setting for the Internet IP which is set to the ... DNS server address is set to SBS server's ip 192.168.5.109 ... but something else is clearly awry if you can't get DHCP ... Which, based on the configuration you gave, is part of the problem. ...
    (microsoft.public.windows.server.sbs)