   Longhorn Server & DHCP confusing!!!!
  I am used to the windows server 2003 ent. setup with DHCP. It was easy, just authorize the server, add the scope, etc. This new DHCP is just downright annoying. I hope someone knows what's going on with it b/c first of all, when I opened the DHCP managment console, it didn't even have a server on there listed like it does with 2003. So I clicked add a server and put the servers name and then it added it. But then it said it couldn't find DHCP services on it. Also, I couldn't even find the Add Scope option. Also, what in the heck is IPv4 and IPv6, Internet Protocol version 6 yea but I have never seen that before as an option.   
  IPv6 is the new version of IP; it allows for much larger IP addresses (I think somewhere on the order of 16 trillion) than IPv4.Is your DHCP server down?   ;Quote:Original post by Ravuya(I think somewhere on the order of 16 trillion).If it's 16 trillions of anything, it would be the number of adresses per square centimeter of the earths surface. IPv6 uses 128 bit adresses, meaning approximately 3.4×1038 adresses. Earths surface is about 5×1018 square centimeters unless I did some maths wrong or got the radius wrong. Just to get a feeling of the insane about of adresses [rolleyes]   ;Quote:Original post by Brother BobQuote:Original post by Ravuya(I think somewhere on the order of 16 trillion).If it's 16 trillions of anything, it would be the number of adresses per square centimeter of the earths surface. IPv6 uses 128 bit adresses, meaning approximately 3.4×1038 adresses. Earths surface is about 5×1018 square centimeters unless I did some maths wrong or got the radius wrong. Just to get a feeling of the insane about of adresses [rolleyes]I have enough trouble remembering my phone number. [crying]   ;  Remember that on a Windows server you are not permitted to run a local DHCP server if any of your network interfaces have dynamic addresses. Make sure all of your NICs have static addresses and you should be able to add the DHCP server role.   ;Quote:Original post by ApochPiQRemember that on a Windows server you are not permitted to run a local DHCP server if any of your network interfaces have dynamic addresses. Make sure all of your NICs have static addresses and you should be able to add the DHCP server role.You don't have to make the IP address of every interface static, merely the one the DCHP server is bound to (naturally).   ;  You're right - I'm thinking of WINS servers, where they will crap up if the NIC with your default route is configured by DHCP.   ;  Open the DHCP settings and check your bindings. I had a similar problem on Windows 2003, and it appeared to had binded to both NICs, where the internet NIC had a dynamic address.toolmaker   ;Quote:Hey everyone, I am about to go insane. Longhorn is the biggest waste/techno junk on the planet. You're wrong. Longhorn isn't a piece of shit: You're bad system administrator. Windows longhorn's DNS and DHCP probably work fine, where you just misconfigured it. A bad syst. admin/programmer always blames the tools.Quote:I have a vista computer and a Longhorn server. The vista keeps saying it can't connect with the remote host DNS server when I'm trying to get it to access the internet with the server having DHCP enabeled.How is the Vista machine connecting? Does it obtain an IP address from the server? Or does it get the IP from the router itself?Quote:I have 2 network adapters one is the internet one is the one to the private network. Private Network is set to 192.168.0.2Router: 192.168.0.2DNS Server: 192.168.0.1DNS Domain Name: dtslabcorp.comOk... That's a rather weird configuration. From what I can tell, you probably have RRAS enabled(Routing and Remote Access) where the Longhorn server acts as the router. It connects to a router on one NIC, and to the network on the other. However, you shouldn't put both NICs in the same subnet. It will only confuse you and probably prevent the server from working properly.My server(Windows 2003) uses this(Between '' is the actual name in the Network Connections window):NIC 'Internet':IP address: 10.0.0.1   (10.0.0.138 is my router's IP, static IP)Subnet mask: 255.0.0.0Default Gateway: 10.0.0.138Preferred DNS server: 10.0.0.138 <- This is important!NIC 'Network':IP address: 192.168.1.1Subnet mask: 255.255.255.0Default gateway: <empty>  <- It's important it's emptyPreferred DNS Server: 10.0.0.1 <- Important you enter the IP of your internet NICBoth have no alternate DNS server.If you're not running RRAS, go to the configure this server, open the RRAS plugin and configure the server from 'Remote Access and NAT'(Or just NAT if you don't want a VPN). If the server is behind a router, disable the simple firewall, or if you want extra safety, enable it. I run ISA, so it's disabled.In your DHCP settings, select your server, right click -> properties -> advanced and click bindings. Remove the Internet NIC check, press OK and close the window(s). Unfold the server and the scope, and go to Scope Options. In the options, you'll add DNS Server and Router, and set both to the IP address of your NETWORK NIC. Restart your DHCP server.Quote:And I can connect to the vista computers network for file sharing. Any ideas?And one last thing, my network adapter on my vista is set to obtain automatically and here is what it has:DHCP Server: 192.168.0.2Gateway: 192.168.0.2IP: 192.168.0.11Make sure you use 2 IP ranges, where 192.168.0.x is for server -> router, and 192.168.1.x is for server -> network. The whole reason file sharing probably works is because it hands out IP address from the server. Could also be the router that hands out IP addresses because both the internet and network are on the same range.Also, make sure you can use internet from the server itself. If you did setup DHCP and RRAS with NAT, you probably messed up with the default gateways.Toolmaker   ;  If you're using RRAS, you also have to reconfigure your router to act as a bridge alone, and establish the PPPoE connection through RRAS. In Windows Server 2003 at least, you also need to manually add the default route, and point it to your PPPoE connection. In this environment, I'd also setup an internal DNS server, which forwards queries onto your ISP's DNS servers. You'll also need to make sure NAT is enabled, and once everything is working, you should enable the firewall on this interface to protect your machine from outside attack.As a sidenote, under the RRAS scenario, I'd enable DHCP on the router, and have it supply the public interface of your server with an IP.If you don't want to run with RRAS, the first thing you need to do is disable the DHCP server your router is running. You then either need to connect the router to your network directly, or you need to create a bridge between the two interfaces on your server, assign the router a fixed IP, and add it as the gateway in your DHCP server. You'll also need to enter the IP addresses of your ISP's DNS servers into your DCHP server, as your router will no longer be serving you that information.And yeah, either option requires quite a bit of work to setup if you haven't done it before. Expect to go without a working internet connection for a week or more if you want to have a crack at RRAS (even if you're familiar with Windows Server), although there's little point routing your internet connection through your server without it. Either way, I wouldn't recommend attempting this on Longhorn until you've done it on Windows Server 2003 first. You'll find support much easier to come by when you run into trouble with Server 2003, not least of all because it's not still in beta.   