Re: Clients connecting to server

From: Marina Roos [SBS-MVP] (marina_at_roos.nodontwantspam.nl.com)
Date: 11/27/04 

Date: Sun, 28 Nov 2004 00:49:44 +0100

Hi Heart,

Your config is totally wrong.

Your internal nic should be on static IP and be something like this:

IP: 192.168.1.64
GW: blank
DNS: 192.168.1.64
WINS: 192.168.1.64
Netbios over TCP should be enabled.

External nic:
IP: 192.168.0.2
GW: 192.168.0.1
DNS: 192.168.1.64

You don't specify the AD domainname on either nic. 

-- 
Regards,
Marina
Microsoft SBS-MVP
"heart" <heart@discussions.microsoft.com> schreef in bericht
news:808D8F51-A5FC-4A1E-90D7-C75B60E43C73@microsoft.com...
> I tried to set up my IP scheme like the one on the site you suggested.
when I
> do the CEIWC wizard, It detects my DSL router (the one that turns my phone
> line into a Ethernet connection) which has an ip of 192.168.0.1. The
> speadstream DSL router will assign dynamically an address between the
ranges
> of 192.168.1.64 - 1.64 so pretty much my "server local area connection"
will
> have an ip of 1.64 but after I complete the CEIWC wizard, I get an error
> configuring component.
>
> so I've got internet => speadstream router => server nic 1 => server nic 2
> => wireless router => client computer (only one at the moment)
>
> I also do not know how to set up DHCP on the SBS and have the Clients
point
> to it.
>
> I get an internet connection on the server, but cannot complete the CEIWC
> Here is my ipconfig /all
>
> Windows IP Configuration
>
>    Host Name . . . . . . . . . . . . : RUDY-SERVER1
>    Primary Dns Suffix  . . . . . . . : winkhaus.local
>    Node Type . . . . . . . . . . . . : Unknown
>    IP Routing Enabled. . . . . . . . : Yes
>    WINS Proxy Enabled. . . . . . . . : Yes
>    DNS Suffix Search List. . . . . . : winkhaus.local
>                                        domain_not_set.invalid  //is this a
> problem?
>
> Ethernet adapter Local Area Connection:
>
>    Connection-specific DNS Suffix  . :
>    Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
> Adapt
> er (Generic)
>    Physical Address. . . . . . . . . : 00-00-C0-D7-E7-F9
>    DHCP Enabled. . . . . . . . . . . : No
>    IP Address. . . . . . . . . . . . : 192.168.16.1
>    Subnet Mask . . . . . . . . . . . : 255.255.255.0
>    Default Gateway . . . . . . . . . :
>    DNS Servers . . . . . . . . . . . : 192.168.1.64
>    NetBIOS over Tcpip. . . . . . . . : Disabled
>
> Ethernet adapter Server Local Area Connection:
>
>    Connection-specific DNS Suffix  . : domain_not_set.invalid
>    Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network
Connection
>    Physical Address. . . . . . . . . : 00-0F-1F-F7-D7-71
>    DHCP Enabled. . . . . . . . . . . : Yes
>    Autoconfiguration Enabled . . . . : Yes
>    IP Address. . . . . . . . . . . . : 192.168.1.64
>    Subnet Mask . . . . . . . . . . . : 255.255.0.0
>    Default Gateway . . . . . . . . . : 192.168.0.1
>    DHCP Server . . . . . . . . . . . : 192.168.0.1
>    DNS Servers . . . . . . . . . . . : 192.168.0.1
>    NetBIOS over Tcpip. . . . . . . . : Disabled
>    Lease Obtained. . . . . . . . . . : Saturday, November 27, 2004 4:57:24
PM
>    Lease Expires . . . . . . . . . . : Sunday, November 28, 2004 4:57:24
PM
> "Chad A. Gross [SBS MVP]" wrote:
>
> > Hi H . . .
> >
> > First, bookmark Mariette's site - www.smallbizserver.net
> >
> > Second - I prefer to use a dual nic setup, with all intenet access going
> > through the SBS.  Take a look at the network setup diagrams on
> > smallbizserver.net for IP schemes, etc.
> >
> > If you can't get the clients to resolve the server name, I'm guessing
that
> > you're letting the router handle DHCP, and clients are getting your
ISP's
> > DNS servers.  The recommended setup is to have your SBS handling DHCP,
and
> > all of your clients should be pointing to your SBS (and only your SBS)
for
> > DNS resolution.
> >
> > Also - make sure you finish the items on the To Do List.  And be sure to
> > take advantage of the wizards available to you - specifically the CEICW
> > (Configure Email and Internet Connection Wizard).  The SBS wizards will
make
> > your life much easier in the long run.
> >
> > As for remote access - be sure to check out the Remote Web Workplace
> > functionality . . .
> >
> > -- 
> >
> > Chad A. Gross - SBS MVP
> > SBS ROCKS!
> >
> > www.msmvps.com/cgross
> > www.gosbs.org
> >
> >
> > heart wrote:
> > > My employer purchased SBS2003 for his home network. I am having
> > > troubles setting up his client computers to connect to the server via
> > > server usernames and passwords. My network has 2 options (not sure
> > > which one would work best) for topology. There is the internet
> > > connection that can either go directly into the SBS (w/ 2 NICs) and
> > > out into a wireless router. Or it can go into the wireless router,
> > > and then into the SBS. Like I said, which ever is better, it doesn't
> > > matter. The wireless router has an IP of 192.168.2.1 and the server
> > > probably will have an address like 2.2
> > >
> > > My questions are, should I have the internet connection go directly
> > > into the server and out into the router's "Internet" port for the
> > > clients to access, or should I have the clients and the server
> > > connected to the "Node" ports on the router, and have the internet
> > > come into the "Internet" port of the router.
> > >
> > > Next, with whatever setup is decided above, what should the IP scheme
> > > be? server ip, default gateway (i'm assuming would be the router) and
> > > the DNS (i'm not sure how to set up a DNS).
> > >
> > > and lastly, when the LAN is set up, how do I add client computers to
> > > log-into the server. I've gotten the client to recognize the IP
> > > address of the server, like http://ip-of-server/ConnectComputer, but
> > > not http://serverName/ConnectComputer. And when I type in an admin
> > > login/pword in the connectcomputer screen, it doesn't recognize them.
> > >
> > > Ultimatly, I want remote access through VPN. Some shared network
> > > space to backup important files onto the server. I want POP3 e-mail
> > > accounts to follow each user on the server. And the SBS to host a
> > > network printer that any client has acess to on the network. Any
> > > comments or suggestions would be greatly appreciated. I'll be working
> > > on this for the rest of the weekend. Thanks!
> > >
> > > -h
> >
> >
> >

Relevant Pages

  • Re: Urgent! New router and big disaster
    ... Les Connor [SBS Community Member - SBS MVP] ... No DNS Name Resolution If DHCP Client Service Is Not Running ... You have a full-time broadband connection. ... Next I Select a local router device with an ip address. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... seleting full time broadband connection. ... Les Connor [SBS Community Member - SBS MVP] ... Anyway the Server Ipconfig /all is this... ... Connection-specific DNS Suffix: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... seleting full time broadband connection. ... Les Connor [SBS Community Member - SBS MVP] ... Anyway the Server Ipconfig /all is this... ... Connection-specific DNS Suffix: ...
    (microsoft.public.windows.server.sbs)
  • Re: Does this sound like a bad nic?
    ... The ISP's DNS addresses must be removed on both interfaces, only use the SBS for the DNS IPs, and configure a forwarder to the ISP's or external DNS servers that support recursion. ... As for bringing down the production server, I would rather think removing the ISP's DNS would make the thing work. ... >>> Server Area Connection ...
    (microsoft.public.windows.server.sbs)
  • RE: Cant remote desktop to clients connected via VPN
    ... the SBS 2003, but from your IP configuration, I found your DNS server is ... not point to the SBS server when establish VPN connection from remote ... you could not establish RDP connection also from ... internal clients, it might be occur on the client side, that the port 3389 ...
    (microsoft.public.windows.server.sbs)