Re: SBS 2003 Misconfigured?

Mark Grantom <mgrantom@xxxxxxxxxx[no spam]> wrote:
What part of my configuration do you need to know? As I stated,
there is no setting for NAT on the netopia. Sorry if you can't help
me, I appreciate the effort.

It's called PAT there, I believe. But I wouldn't do it. The Netgear you've
got is not bombproof but I think it's a better security appliance than the
Netopia, and much easier to manage.


Unfortunately, since you don't know your configuration, asking us
for help is kinda like asking someone to bulls-eye a target
blindfolded. Some people can do so, and might even enjoy it...but
most don't and won't. And it can be dangerous.

I could 'guess' that the configuration, as you described it, is the
netopia configured as a bridge and the netgear as the NAT device.
It is also possible the netgear is not properly passing LAN traffic.

So, I stand by my previous recommendation. Remove the netgear,
configure the netopia as the NAT device (I prefer the Netopia
firewall anyways, for a basic firewall), and add a switch to the
netopia for the other devices.

-Cliff

"Mark Grantom" <mgrantom@xxxxxxxxxx[no spam]> wrote in message
news:D2B234DE-8886-44E7-BF74-9DA23387B206@xxxxxxxxxxxxxxxx
I went back and looked at the Netgear. I don't see anything that
allows you
to turn NAT on or off. I based my post on the notes that a tech I
hired left
me. I DO know that NAT is off on the Netopia. The netgear has a
setting for
the Internet IP which is set to the static IP given to me by AT&T.
It also
has a setting for the LAN ip which is set to 192.168.5.2 if this
helps. The
additonal information on how my workstations are manuall configured:
WINS is set to the SBS server's ip 192.168.5.109
DNS server address is set to SBS server's ip 192.168.5.109
Append primary and connection specific DNS suffixes is selected
DNS suffix for this connection is set to "grantomlaw.local"
Register this connections addresses in DNS is checked
Use this connection's DNS suffix in DNS registration is checked
IP Settings
192.168.5.101 Subnet mask of 255.255.255.0
Gateway is set to 192.168.5.2 (address of the netgear router)
Automatic metric is checked
--
Mark G


"Cliff Galiher" wrote:

Inline:

-Cliff

"Mark Grantom" <mgrantom@xxxxxxxxxx[no spam]> wrote in message
news:63AFF1B0-E929-40DB-B7FF-ED1377D9BC69@xxxxxxxxxxxxxxxx
Thanks for all the quick responses! I apologize for not getting
back sooner
but I had to be out of the office today unexpectedly. The
Netopia IS a router/modem, it is just not setup up for routing.
I wanted to use the Netgear router because it has 8 ports,
utilizes UPNP (at least it did it
ONCE
then quit) and is brand new (well almost).
UPnP is useful for a very limited subset of applications, none of
which apply in an office setting.

NAT is turned off on both devices.
Which, based on the configuration you gave, is part of the
problem. You mentioned that you assigned the ISP IP to netopia
AND the netgear. That itself will cause a problem. You *can*
configure the netopia to operate in
bridged mode, but in this configuration, it is literally acting as
modem, converting DSL/ATM traffic to ethernet and would not hold a
public IP of its
own. Again, it would have to be configured properly to pass ALL
traffic to
the netgear...tricky if you aren't sure EXACTLY what you are doing.

Secondly, the netgear SHOULD be configured to NAT unless you are
running SBS
in a 2-nic configuration in which case SBS would be handling NAT.
But, if
SBS were in a 2-nic configuration, you'd still need a switch on the
internal-facing NIC. You could use the netgear for this, but at
that point
you'd configure the netgear without an external IP...and basically
not be using the routing functions at all. So basically, from
where I stand, you
still have configuration issues.

I am NOT a techie I just figured out a lot by myself in the last
30 years that I have been building / using computers ( I started
in 1978). Initially when I installed SBS 2003 I was using the
netgear router with a
DSL
modem. When I changed over to a static IP, AT&T sent me the
netopia router/modem so I was forced to use it, but since it only
has 4 ports, I
had
a tech help me to set it up so it only obtains the ip (so it does
operate
as
only a modem).
If it is properly configures as "only" a modem, then it won't
obtain the IP.
It will let the netgear handle that task. See above.

I then linked it to the netgear router. DHCP is configured
on the server, but if I set a workstation to "obtain ip
automatically" that
WS cannot get onto the internet. If I manually set the ip's
there are no
problems.
A perfect example of why I think you have fundamental network
issues. Until
you get DHCP working, you can't expect other things to work. DHCP
isn't an
overly complex protocol. If it is broke...well....you need to
concentrate
on fixing it. Don't even *worry* about trying to fix the printing
issue yet. When you fix DHCP, I suspect you'll find other things
magically start
working.

The specific problem I have at the moment is that I have to run
Quickbooks on my server (I know, I shouldn't but I HAVE to because
another
application I use Time Matters "Quickbooks Server, requires it.)
You know you shouldn't. We know you shouldn't. Suffice it to
say, you should look at addressing this. I'm familiar with Time
Matters and have my
own opinions on how to resolve this issue, but as tempted as I am
to do so,
I think it'd only fracture the thread and frankly does not directly
relate
to the problem you have right now.

When I try
to print from the server using the laser printer on one of the
workstations,
the printer does not show up. Everything else seems to work.
Everything except DHCP. You can't ignore problems and expect
everything else to work. Sorry if that comes across harshly, but
it is true. To say
"everything else seems to work" blatantly ignores the other
problems you've
posted here.

I can browse
files on the workstations etc. The printer is properly shared on
the workstation and the box checked that says to "list in
directory".
The "list in directory" is nice if you are using AD to find
printers. It is
not necessary though. If you've shared the printer, then you can
always fall back to 'classic' file and printer sharing. And since
that does not appear to be working, you have other problems.

I'm not
sure, but I believe it MAY be related to my having "moved" the
workstations
in the Active Directory to the "my company" computers folder, if
I'm making
sense.
Possible, if a GPO is configured to stop file and printer sharing
or setting
firewall rules to block such communications. Why did you move the
computer
to a different OU? For SBS, the default setup with
/connectcomputer is good
99% of the time. There *are* legitimate reasons to move machines,
but I find many people do so when it is unnecessary as well.
There is usually a
better way...

Thanks for all of the help.
--
Mark G


"Lanwench [MVP - Exchange]" wrote:

Cliff Galiher <cgaliher@xxxxxxxxx> wrote:
Lanwench brings up good points, but I'm going to go a step
further and say I'm concerned about your current device
configuration.

If I read this properly, you have the WAN port of your netgear
device
plugged into one of the LAN ports of your netopia.

Yes, that was my understanding as well.

The netopia 3300
series (I'm guessing the model based on the specs given)
default to a
NAT routing configuration,

But not necessarily. I have several clients running Netopias. I
merely tell
the ISP that I have my own firewall appliance & don't want NAT
or any filtering. The NetGear FVS318 is not the greatest
firewall on the planet,
but it's a decent little device - and it has an integrated
Ethernet swtich,
which I presume he's using.

Even if the Netopia were configured to do NAT, the worst thing
that would
happen is that his LAN would be 'double NATted' - which might
cause problems
with *inbound* traffic but wouldn't cause any problems with LAN
traffic
or
outbound Internet connectivity.

Guess we'll have to wait til the OP posts back to find out.

so essentially you've segmented your
network if you have equipment plugged into both devices. This
could cause all sorts of problems if you haven't carefully
configured the equipment. I'd personally pull the netgear out
of the equation. No need for two peices of equipment that do
the same job.

I would instead pick up a switch (not a router), such as a 3com
OfficeConnect (they come in managed and unmanaged varieties) or
a Linksys and plug it into the netopia. No worrying about WAN
ports, no
configuration, just plug and play. I think you'll find
administration and troubleshooting much easier if you don't
have to worry about network communications traversing multiple
routable devices.
-Cliff

"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:OpNPcrA$IHA.3964@xxxxxxxxxxxxxxxxxxxxxxx
Mark Grantom <mgrantom@xxxxxxxxxx[no spam]> wrote:
I apologize in advance for the length of this post, however I
wanted
to furnish as much information as possible to help me solve
this problem. I have spent a great deal of time trying to
solve this myself but I am at a complete roadblock at this
point. I really need to get my system up and functional
again. My SBS 2003 is setup with 1 NIC & 3 Win XP
workstations. I am using a Netopia ADSL2/2+ 4pt Managed
Switch that is connected to a netgear router. I
needed the Netgear router because it has 8 ports and I have
several printers besides my 3 workstations and server that I
wanted
to connect to it. My SBS 2003 Server and 3 workstations are
all connected to the router. I am having trouble not being
able to print from the server to a printer connected on one
of the workstations. I get an "access denied, unable to
connect" type message. I also lose connectivity between the
WS and the server from time to time. I believe I have
something misconfigured but I cannot figure it out. Any help
in getting this resolved would be much appreciated. The
configuration of the devices is as follows: Netopia router

(this is really a modem)

DHCP "OFF"
Manually configured static IP from ISP
DNS set to ISP DNS-1 & DNS-2

Netgear FVG318 router
WAN IP set to one of the static IP's assigned by ISP
LAN IP of router manually set to 192.168.5.2
DHCP turned off
Primary and Secondary DNS setup to my ISP's DNS


SBS 2003 Server
Computer name is MSGSRV
IP of server is 192.168.5.109

That's fine, but for reasons of tidiness & organization it's
usually
best to assign your static IP addresses from the lowest or
highest range of your IP subnet. I set exclusions - such as,
from .1 to .50 and from 200 - .250. I set the gateway/router
appliance to .1, and set my servers to use between .10 and
.20, etc. You don't have to do
this, but I find it tidier.
TCP/IP is configured so that DNS point to itself

Good

The alternate DNS is blank, should I set it to the ISP DNS-1?

Nope.

Default gateway is set to router 192.168.5.2

DHCP is configured, but I manually configured all IP's on all
computers after I started having problems.

OK - you shouldn't need that, but see below.

DHCP scope 192.168.5.100 to 192.168.5.150

OK.

IP's on Workstations was Manually configured as 192.168.5.101,
192.168.5.110, and 192.168.5.108 because DHCP will not work.
Each WS has its DNS pointed to the server local ip.



.

Relevant Pages

  • Re: SBS 2003 Misconfigured?
    ... I agree, with what I could have / should have done as far as the router, ... Why didn't you just disconnect the Netgear and not touch the Netopia? ... Which, based on the configuration you gave, is part of the ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... I went back and looked at the Netgear. ... I DO know that NAT is off on the Netopia. ... DNS server address is set to SBS server's ip 192.168.5.109 ... Which, based on the configuration you gave, is part of the problem. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... I could 'guess' that the configuration, as you described it, is the netopia ... configured as a bridge and the netgear as the NAT device. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... Unfortunately, since you don't know your configuration, asking us for help is kinda like asking someone to bulls-eye a target blindfolded. ... I could 'guess' that the configuration, as you described it, is the netopia configured as a bridge and the netgear as the NAT device. ... Remove the netgear, configure the netopia as the NAT device, and add a switch to the netopia for the other devices. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... NAT and made sure DHCP was turned off. ... Why didn't you just disconnect the Netgear and not touch the Netopia? ... Gateway is set to 192.168.5.2 (address of the netgear router) ...
    (microsoft.public.windows.server.sbs)