Curv Boll

HI, Yes i think the problem has been solved but as i tried to say, there 2 options to correct it.... 1. Increase the scope as agreed or 2. edit the registry on the server that specifies the default setting of 10 addresses held back for rras remote clients. I am choosing the latter for thew time being but i'll let you know how it goes. Thanks for input. C.B

Hi there, As i stated earlier i think some1 gave me the answer from another source but im always pleased to see people respond. In answer to your questions 1. The scope is a private non routable scope and it has only ten addresses as i have only a few clients. I am using rras for nat so that each client can reach the web and can be managed from the web. I dont want to increase the scope for other reasons but i can tweak the default rras lease from 10 resses to just a few. Should be trying it out tonight, i'll let ya know. C.B

Hi there, I used coverxp last night and i think it rocks, the default size for cd cover templates is 121mm x 121mm as far as i can remember. i changed this to 124mm x 121 to make a more snug fit. To change the size you should use the template settings as already advised. good luck

Hi OldMan, Thanks for the ideas, sadly i have assigned a static ip address which is outside the active dhcp scope. Though i think i have found the correct answer from my other source. My scope was only 10 addresses long and since i had rras running it by default holds back 10 addresses for remote clients. This default setting can be changed in the registry or i can extend my scope so that it has enough for remote clients and my few clients. I have not had time to fully test this idea but i think it will be correct and i shall post back again to confirm many thanks C.B

Hello again, Well i am surprised at the lack of ideas, However i have another resource for an answer that i did not want to use but it looks like i will have to. I will let you know if i find the answer out! cheers Curv Boll

Hi Vavavoom, By the size of your network all you should need is the standard edition of 2k3 server. Most people however, create a "domain" when introducing 2003 server into their network. They setup the server as a domain controller which means they have a central administrative point for sharing files and managing accounts and so on. This makes life so much easier. If you want to make the server a domain controller you will have to change the xp home machines. XP home machines are every bit as good as the pro version except that they do not have the networking capabilities that are offered in the pro version. (just a good bit of marketing by ms) This in turn means that home machines cannot join a domain. XPpro can. The other option you have is to leave the server as a member server which means there will be no central management server for the network. The server will be able to assign dhcp addresses to the clients but you would have to manage computers and users via all the different machines. Hope this helps C.B

Hi Folk's, I have a problem which i am sure will be simple for some1 to answer, Currently i have 2k3 server setup as dc... That same server acts as a dhcp server as well as dns and wins server. This machine also acts as a rras server. Everything works as required except that from time to time my clients cannot get ip addresses from the server. When i look at the status of the dhcp server i find that all the addresses in the active scope are assigned to the server. The clients are not getting an ip because the dhcp server is assigning all the available ip's to itself!! Any idea's??? Thankyou in advance C.B