Re: Multiple server problems - HELP!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Jack,

Sorry, been away for a couple of days. I'd suggest a new thread for the VPN
(if you haven't already).

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !


"Jack_EFI" <JackEFI@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F1F0B523-A4F5-444A-9BDB-E9A0D1F07230@xxxxxxxxxxxxxxxx
> Les:
>
> Thanks VERY MUCH for all your help. I went in at the crack on dawn this
> morning and made all the changes and it worked like a champ! One thing I
> stumbled on was the DHCP server - it wasn't previously installed, so I
> installed it. When it came to defining the scope, I guessed it should be
> 192.168.16.0 to 192.168.16.149, reserving out 192.168.16.0 to
> 192.168.16.9.
> It seems to work fine.
>
> Now, my next issue is how to setup VPN access to the server... Can you
> help
> me with that?
>
> Thanks very much,
> Jack
>
> "Les Connor [SBS Community Member - SBS M" wrote:
>
>> Hi Jack,
>>
>> You shouldn't need to disable it (permanently). You won't need it's DHCP
>> for
>> the SBS external nic as that is configured to a static ip, but sometimes
>> it's useful so devices can get internet connectivity outside the lan.
>> (guests, for example).
>>
>> The main concern would be that the SBS doesn't see it, which would cause
>> the
>> SBS DHCP to shut down. That won't be the case once the networking is
>> configured and the CEICW is run, but it might cause a problem initially.
>> If
>> the SBS DHCP server shuts down and gives an error that another DHCP
>> server
>> is present, then shut it off.
>>
>> One other thing I didn't mention - in the router configuration - you'll
>> need
>> to forward the appropriate ports to the external IP of your SBS.
>>
>> Not sure what all you need, but these are common: only forward the ones
>> you
>> need.
>>
>> 25 - SMTP
>> 443 - SSL (OWA and RWW)
>> 1723 - VPN
>> 3389 - RDP
>> 4125 - RDP via RWW
>>
>> There should be ample assistance in the help or 'more information'
>> buttons
>> in SBS and in the CEICW.
>>
>> --
>> Les Connor [SBS Community Member - SBS MVP]
>> -----------------------------------------------------------
>> SBS Rocks !
>>
>>
>> "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
>> >> >
>> >> > Ethernet adapter Network Connection: (this is the one that is
>> >> > currently
>> >> > disabled)
>> >> > Connection-specific DNS Suffix . :
>> >> > Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
>> >> > Adapter(LNE100TX v4)
>> >> > Physical Address. . . . . . . . . : 00-0C-41-EE-82-9C
>> >> > DHCP Enabled. . . . . . . . . . . : Yes
>> >> > Autoconfiguration Enabled . . . . : Yes
>> >> > IP Address. . . . . . . . . . . . : 192.168.1.105
>> >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> >> > Default Gateway . . . . . . . . . : 192.168.1.1
>> >> > DHCP Server . . . . . . . . . . . : 192.168.1.1
>> >> > DNS Servers . . . . . . . . . . . : 192.168.1.2
>> >> > NetBIOS over Tcpip. . . . . . . . : Disabled
>> >> > Lease Obtained. . . . . . . . . . : Thursday, July 14, 2005
>> >> > 7:29:50
>> >> > AM
>> >> > Lease Expires . . . . . . . . . . : Friday, July 15, 2005 7:29:50
>> >> > AM
>> >> >
>> >> > Ethernet adapter Server Local Area Connection:
>> >> > Connection-specific DNS Suffix . :
>> >> > Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
>> >> > Adapter (10/100)
>> >> > Physical Address. . . . . . . . . : 00-06-5B-3E-83-0B
>> >> > DHCP Enabled. . . . . . . . . . . : No
>> >> > IP Address. . . . . . . . . . . . : 192.168.1.2
>> >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> >> > Default Gateway . . . . . . . . . : 192.168.1.1
>> >> > DNS Servers . . . . . . . . . . . : 192.168.1.2
>> >> > Primary WINS Server . . . . . . . : 192.168.0.6
>> >> >
>> >> > ipconfig/all for Win XP Client
>> >> >
>> >> > Windows IP Configuration
>> >> > Host Name . . . . . . . . . . . . : EFI-06-JC-LT
>> >> > Primary Dns Suffix . . . . . . . : efi.local
>> >> > Node Type . . . . . . . . . . . . : Hybrid
>> >> > IP Routing Enabled. . . . . . . . : No
>> >> > WINS Proxy Enabled. . . . . . . . : No
>> >> > DNS Suffix Search List. . . . . . : efi.local
>> >> > Ethernet adapter Wireless Network Connection:
>> >> > Media State . . . . . . . . . . . : Media disconnected
>> >> > Description . . . . . . . . . . . : Intel(R) PRO/Wireless
>> >> > 2200BG
>> >> > Network Connection
>> >> > Physical Address. . . . . . . . . : 00-0E-35-B3-27-B1
>> >> > Ethernet adapter Local Area Connection:
>> >> > Connection-specific DNS Suffix . :
>> >> > Description . . . . . . . . . . . : Broadcom 570x Gigabit
>> >> > Integrated
>> >> > Controller
>> >> > Physical Address. . . . . . . . . : 00-11-43-65-0B-5D
>> >> > Dhcp Enabled. . . . . . . . . . . : Yes
>> >> > Autoconfiguration Enabled . . . . : Yes
>> >> > IP Address. . . . . . . . . . . . : 192.168.1.103
>> >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0


.

Quantcast