Re: Clients connecting to server
From: Marina Roos [SBS-MVP] (marina_at_roos.nodontwantspam.nl.com)
Date: 11/28/04
- Next message: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]: "Re: Errors during SBS2003 setup wizard"
- Previous message: Bill: "Re: Thank You - 12 Companies 1 Server"
- In reply to: heart: "Re: Clients connecting to server"
- Next in thread: heart: "Re: Clients connecting to server"
- Reply: heart: "Re: Clients connecting to server"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 28 Nov 2004 23:28:50 +0100
Hi Heart,
Every dsl router is capable of turning of DHCP, else get another one.
DNS on your external nic should point to your server IP.Your external nic
doesn't make sense at all. The IP and gateway should be in the same subnet.
Where does this domain_not_valid come from?
-- Regards, Marina Microsoft SBS-MVP "heart" <heart@discussions.microsoft.com> schreef in bericht news:CCF2CBF2-1A17-4E24-A8FC-25BBEF83CB1F@microsoft.com... > Yes, 192.169.2.x for my internal network. > > My external NIC is assigned a dynamic IP, my internal is a static IP. I > don't have an option in my dsl router config to turn on or off DHCP, > here is the 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 > > Ethernet adapter Internal: > > Connection-specific DNS Suffix . : > Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network Connection > Physical Address. . . . . . . . . : 00-0F-1F-F7-D7-71 > DHCP Enabled. . . . . . . . . . . : No > IP Address. . . . . . . . . . . . : 192.168.2.1 > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Default Gateway . . . . . . . . . : > DNS Servers . . . . . . . . . . . : 192.168.2.1 > Primary WINS Server . . . . . . . : 192.168.2.1 > > Ethernet adapter External: > > Connection-specific DNS Suffix . : domain_not_set.invalid > Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet > Adapter (Generic) > Physical Address. . . . . . . . . : 00-00-C0-D7-E7-F9 > 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 . . . . . . . . . . . : 65.43.19.26 > NetBIOS over Tcpip. . . . . . . . : Disabled > Lease Obtained. . . . . . . . . . : Sunday, November 28, 2004 4:08:23 PM > Lease Expires . . . . . . . . . . : Monday, November 29, 2004 4:08:23 PM > ==I had to set the DNS to that static ISP assigned DNS to access the net== > > "SuperGumby [SBS MVP]" wrote: > > > OK. we're going wrong here. > > > > Do you know what a subnet is? Two devices must be on the same subnet to > > directly talk to each other, otherwise they need to talk through a gateway. > > > > I think your internal and external networks may be mixed up. What SBS thinks > > is internal you have connected to the router, what SBS thinks is external > > you have on your switch. > > > > Even if a little light globe lights above your head, please don't change > > anything for a few moments. except this... > > > > Call up your network properties and rename the two NICs. Name the one you > > expect to be used internally 'Internal', name the one going to the router > > 'External'. Don't worry if both these names don't stick. Then give us the > > output of 'ipconfig /all > c:\ipconfig.txt' > > > > I think we'll be running the 'Change Server IP' wizard a couple of times, > > then the 'Connect to the internet' wizard. > > > > There's a reasonable chance that the router, though configured in the > > 192.168.0.x/255.255.255.0 subnet has a DHCP server in it handing out > > 192.168.1.x addresses, this should be easy to change but is not a major > > problem. > > > > I take it you wish to use 192.168.2.x/255.255.255.0 for your internal > > network, yes? > > > > > > "heart" <heart@discussions.microsoft.com> wrote in message > > news:BB9225F1-C3F5-42F7-9D3D-16C7902F4A55@microsoft.com... > > > I cannot have 192.168.1.64 as the IP of my static nic (the one _not_ > > directly > > > connected to the internet) because the one that is connected to the net > > (my > > > DSL router) is automatically assigned an IP of 192.168.1.64 > > > > > > so my dsl router has a local ip of 192.168.0.1, and assigns my server a > > > dynamic address of 192.168.1.64 and the CEIWC thingy automatically gives > > my > > > dynamic address a net mask of 255.255.0.0, is this an issue? > > > ===latest ipconfig attempt===== > > > Ethernet adapter Local Area Connection: > > > > > > Connection-specific DNS Suffix . : > > > DHCP Enabled. . . . . . . . . . . : No > > > IP Address. . . . . . . . . . . . : 192.168.2.1 > > > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > > > Default Gateway . . . . . . . . . : > > > DNS Servers . . . . . . . . . . . : 192.168.2.1 > > > Primary WINS Server . . . . . . . : 192.168.2.1 > > > > > > Ethernet adapter Server Local Area Connection: > > > > > > Connection-specific DNS Suffix . : domain_not_set.invalid > > > 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.2.1 > > > NetBIOS over Tcpip. . . . . . . . : Disabled > > > =====attempt gave me same error configuring component on CEIWC====== > > > > > > "Marina Roos [SBS-MVP]" wrote: > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
- Next message: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]: "Re: Errors during SBS2003 setup wizard"
- Previous message: Bill: "Re: Thank You - 12 Companies 1 Server"
- In reply to: heart: "Re: Clients connecting to server"
- Next in thread: heart: "Re: Clients connecting to server"
- Reply: heart: "Re: Clients connecting to server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading
