Re: Multiple server problems - HELP!
- From: Tez <Tez@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 20 May 2008 17:16:58 -0700
Hi guys
I don't know what was wrong, but it works now! Thanks so much for your
help. I am also getting my performance reports now. Must say that the BPA
is a great tool.
Thanks again
"Larry Struckmeyer [SBS-MVP]" wrote:
HI Tez:.
We have to start somewhere. Please post back the results of:
ipconfig /all > c:\iptest.txt
from the server and a workstation. You can alter the names if you must, but
be consistent. The numbers you already posted. <g>
Also, the event id and source of any errors in your event logs... a few that
appear relevant.
And download, install, and run the sbs best practices analyzer and fix what
ever it finds.
www.sbspba.com
--
Larry
Please post the resolution to
your issue so that all can benefit.
"Tez" <Tez@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2260807A-3AA9-472D-8C7B-5C21ABEDDC57@xxxxxxxxxxxxxxxx
Hi
I have the exact same setup (except my external NIC is 192.168.20.1,
modem/router 192.168.20.254, internal NIC 192.168.10.100, WAP
192.168.10.50).
DHCP on server is 192.168.10.101 to .254. Firewall settings on
modem/router
are directed through 192.168.20.1. Clients are able to pick up IP address
but no access to internet or to shared drive on server. I have re-run
CEIW
for the dual NICS & all settings look right to me.
What am I doing wrong?
"Brett Smith" wrote:
With the configuration that Les suggested then yes you can turn it off,
but
in reality it doesn't matter because the only device logically or
physically
connected to it will be the SBS box which has it's IP set statically.
If your access point is capable of being a DHCP Server then you must
disable
it. You can only have one DHCP server on each physical network bus. and
in
SBS's LAN NIC case that DHCP server REALLLLLY should be the SBS server.
It
sounds like this may be why you had problems once you introduced the
wireless, but I could be wrong on that :)
Good Luck!
"Jack_EFI" <JackEFI@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5E98FECC-3E8E-48F2-93F4-8CCB9C356454@xxxxxxxxxxxxxxxx
Thanks Les - I'll try it tonight when all the users go home. SO - i
assume
I
should disable the DHCP server on the DSL router - is that correct?
"Les Connor [SBS Community Member - SBS M" wrote:
Hi Jack,
Configure the external nic (the one currently disabled) manually.
IP Address (Static) 192.168.1.2
Subnet: 255.255.255.0
Default Gateway: 192.168.1.1 (your router lan IP)
DNS: 192.168.16.2
Connect this nic to the lan side of your router.
Run the Change Server IP wizard, located in Server Management |
Standard
Management | Internet and Email. Change the IP to 192.168.16.2
You want to end up with an internal nic configuration like this:
IP Address (Static) 192.168.16.2
Subnet 255.255.255.0
Default Gateway: <blank>
DNS: 192.168.16.2
Connect this nic to a hub/switch - all of your wokstations will be
connected
here as well, (not to the router).
Run the Connect to the Internet wizard from the same page as the
Change
Server IP wizard (above). Specify which nic is your internal nic, and
which
is your external nic. When asked for DNS forwarder addresses, you can
enter
your ISP's DNS server addy(s) if you know them, or leave them blank if
you
don't.
The net result of the above is that you should end up with a corrected
DNS,
DHCP, and WINS configuration on the SBS server.
Connect a workstation to the same hub/switch as the SBS internal nic,
and
change the networking configuration to a full DHCP client. Run
ipconfig
/release ipconfig/renew, or restart the workstation to get the correct
settings from the SBS dhcp server.
That should correct most of your issues, if not all. You may have some
devices (printers, possibly) with static IPs that you'll have to
attend
to.
I'm not sure what device you're using for wireless, but you'll likely
need
to move it to the internal hub/switch as well, and configure it as an
Access
Point, so the SBS DHCP can pass through it.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
"Jack_EFI" <JackEFI@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:01D3B756-7B4B-4F04-89FC-C6BC926C58E3@xxxxxxxxxxxxxxxx
Sigh... where to start??
Well, let me start by saying I'm not an IT professional - just the
person
w/
the most experience in the office. As such, this post will probably
be
a
bit
windy and possibly confusing - please bear with me.
Hardware/OS Description
We have Windows 2003 SBS Standard running on a Dell PowerEdge 2500
server
(it was loaded pretty "vanilla" out of the box). We have 8 client
workstations all running Win XP Pro, service pack 2 (all P4s w/
ample
RAM,
HD
space, etc.).
Internet Connectivity
We have DSL thru SBC. The DSL modem is connected to a Linksys
Etherfast®
Cable/DSL Router (BEFSR41 V3) with a static IP supplied by the ISP.
Local
DHCP server is enabled on this router(though all IP addresses on the
clients
are manually configured). The IP of the router is 192.168.1.1 and
the
DHCP
address range is 192.168.1.100 to 192.168.1.149. The internet
connection
is not directly routed to SBS. While there are 2 NICS on the server,
only
one
is use to connect to the LAN. SBS is not used as a DHCP server. So,
in
cases
(see "Problems" below) where the clients can not connect to the
server,
they
are still able to connect to the Internet. Our "network" consists of
a
bunch
of hubs (3-4), the 8 client machines and the server.
Problems
Almost like clock work, our client computers run into an extreme
slowdown
daily (at the same time every day) when attempting to save files on
the
server, or access anything on the server for that matter (our
financial
software data is stored there which is accessed by the locally
installed
software on the clients). If we are lucky (and have the patience to
wait
it
out), connectivity is re-established after what seems like an
eternity
and
files are saved, etc.
Mapped network drives are randomly dropped throughout the course of
the
day.
Sometimes clicking on the "disconnected network drive" through My
Computer
will cause it to immediately reconnect, but at other times it just
causes
My
Computer to freeze up, necessitating a reboot.
Client machine routinely lose the trust relationship to our domain,
which
I
remedy by removing it temporarily from the domain, adding it to a
generic
workgroup, then re-add it to the domain again. (The trust is
reestablished
at
the point.)
When we installed a wireless access point, we immediately had
connectivity
problems from all clients (not just the wireless machines.) The IP
addresses
defaulted over to Windows' Automatic Private IP Addressing that
assigned
IP
addresses like 169.254.x.x My only recourse around this was to
either
remove
the WAP or assign static IPs to each client. I chose to do both to
be
sure
that it wouldn't happen again (though in looking at my own client, I
noticed
I'm still DHCP enabled). A bandaid fix I'm sure...
Observations
I've searched the Internet ad nauseum to try to figure these issues
out.
I've read through quite a lot of forums like this one (yours seemed
the
most
thorough) but still haven't found any real solutions for our
problems -
and I
know this is most likely due to my limited knowledge of networking,
TCP/IP,
etc.). A couple of ideas that came up seem to be related to how the
SBS
DNS
server is set up as well as DHCP on SBS, which, as mentioned above,
we
don't
run. In checking the event logs for the DNS server, there's nothing
but
errors listed - specifically event ID 7063. After reading theough
the
forums,
I looked at the configuration of the DNS server on SBS and found
that
is
does
have a DNS forwarder setup (to an IP I have no idea where it came
from -
24.93.x.x). The error message recommended that I either disable
recursion
on
the forwarder, or get rid of the forwarder all together. I elected
to
disable
recursion since I had no idea where the forwarded IP came from. I
have
yet
to
stop and then restart the DNS service since it is in the middle of
the
workday (I assume connectivity would be lost for the clients).
I have a sneaky feeling that a lot of the problems we are having may
be
from
the following:
Not having the Internet go through SBS (using the 2nd NIC on the
server,
which is currently disabled) and using all of its services and/or
controls.
Using the DHCP server on the DSL router instead of SBS.
Since I know I'll be asked, below are ipconfig/all details on both
the
server and one of the clients:
ipconfig/all for SBS server:
Windows IP Configuration
Host Name . . . . . . . . . . . . : efiserver
Primary Dns Suffix . . . . . . . : efi.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : efi.local
- References:
- Re: Multiple server problems - HELP!
- From: Tez
- Re: Multiple server problems - HELP!
- From: Larry Struckmeyer [SBS-MVP]
- Re: Multiple server problems - HELP!
- Prev by Date: Re: Restore Public Folder
- Next by Date: Re: Event Viewer events
- Previous by thread: Re: Multiple server problems - HELP!
- Next by thread: Outlook installation problem
- Index(es):
Relevant Pages
|
