Re: SBS 2003 Misconfigured?
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 12 Aug 2008 09:38:50 -0400
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.
What about the DNS suffix & WINS?
Are there a set of diagnostics I can run that will help me pinpoint
my issue? Thanks in advance.
This is a lovely and informative level of detail, but you haven't
told us the exact symptoms of the problem is yet. What precisely
happens when you try to use DHCP & get a lease on a workstation?
When you set up the server, did you install & configure DHCP right
off the bat, or did you have another device on the LAN with an
active DHCP server (and hence SBS would skip DHCP setup)?
.
- Follow-Ups:
- Re: SBS 2003 Misconfigured?
- From: Mark Grantom
- Re: SBS 2003 Misconfigured?
- References:
- SBS 2003 Misconfigured?
- From: Mark Grantom
- Re: SBS 2003 Misconfigured?
- From: Lanwench [MVP - Exchange]
- Re: SBS 2003 Misconfigured?
- From: Cliff Galiher
- SBS 2003 Misconfigured?
- Prev by Date: RE: Posting to the group
- Next by Date: Re: Posting to the group
- Previous by thread: Re: SBS 2003 Misconfigured?
- Next by thread: Re: SBS 2003 Misconfigured?
- Index(es):
Relevant Pages
|
