ixion

Ok I've found the solution to this if anyone was interested In some cases you cant have two network adapters in a RIS server if the NIC's are part of two seperate networks. Disabling additional NIC's solved the problem

yeah so the problem is obvious in that when you logout it closes any existing dial-up connections. Perhaps you should install routing and remote access (built into windows server) and configure your PPOE connections from within there, this will pass your dial-up configuration to services

the immediate solution is to disconnect from the session rather than logging out is ppoe a dial-up connection? (uses dial-up networking?)

group/local policy I believe - look through the options available to you in the policy settings

Ok, I thought I would I install the first RIS server at work today I booted up a member server (Windows 2003 SP1) which I use for various administratiive tasks and installed RIS, rebooted and added an XP image. I then ran the RIS Testing tool which said everything was ok and it ensured the services were started and that DHCP was authorised. I then hopped onto the DHCP server (Windows 2000 SP4) right clicked on the relevant bit and went into "manage authorised server" the new RIS server wasn't in there so I went ahead and added it manually by hostname which resolved to the correct IP address. I then went back to the RIS server and restarted the remote install services Thinking I had covered everything I tried to boot a PXE compliant machine and it just stopped at the DHCP....... bit and then told me that it didnt receive a bootp file name and carried on booting into Windows XP. The machine can obtain an IP address from DHCP from within XP fine. Its a Dell Optiplex machine with an integrated PXE compliant NIC I have since tried going into DHCP right clicking on the scope and enabling DHCP to respond to both DHCP and BOOTP clients with the same result the message I am getting is "the proxyDHCP server did not reply to the request on port 4011" I can see that the PXE client has received an IP address as it displays this to me, it also tells me which server it received the IP address from and it is receiving the IP address from the correct DHCP server (as above) - it just doesnt seem to be getting any BOOTP information Any ideas?

I posted a new problem here, will start a new thread instead

I fully understand your rushing through my post - I did mention that I know the server has to be authorised, but one of my questions which related to this was, does DHCP have to be installed on the RIS server in order to authorise it?

check your share permissions aswell as file permissions - the most restrictive applies

Hi, I am having a few issues with RIS and finding it really difficult to find any kind of clarification on the web about some of the issues or queries I am having with RIS If I setup a new domain with a new DHCP server and new DNS servers etc, install RIS on the DHCP server and add an image it seems to work straight away. Every single time I move DHCP to another server RIS just stops working, my PXE clients just stop at "DHCP..." and report that no TFTP filename was recieved I have tried installing RIS on the new DHCP server, re-adding images, running the RIS setup checker thing, restarting services and everything else I can think of and I just cant get RIS to work. I decommision the domain controllers, format the machines and setup a new domain, install RIS and DHCP etc on the same box and it works again. When it comes time to move the DHCP server or RIS to another box it simply just stop working again. I have gone through this same procedure a number of times now and each time I need to make a change to my network (ie move DHCP/DC/RIS) and I end up re-doing my entire domain again. My last effort seems to have been my most succesfull. I manage to move DHCP from the DC/RIS server to another box and RIS stopped working. No matter what I tried I could not get RIS to work again until I moved RIS to the new DHCP server. I have tried this several times without success but this time it did work. Now my questions are, does anyone know exactly how DHCP is supposed to be configured, whether the RIS server itsefl needs DHCP server installed etc etc because Im tired of going round in circles with RIS now and I want to know exactly what its requirements are and how it should be setup. Reading FAQ's on the internet and MS site I can see the same list of troublshooting techniques popping up: one entry is always "make sure the RIS server is authorised in DHCP" and another is "IF DHCP and RIS are on the same server make sure the following resgistry setting is changed....." Judging by the second entry DHCP and RIS do not HAVE to be on the same server otherwise it would not say IF. How then are you supposed to authorise a server in DHCP if it does not have DHCP server installed? Other things I tried before I got it working were: Adding another image to RIS and choosing "use the new client install screens" Restarting RIS services Re-installing DHCP on the original RIS server and then authorising it even though there was no active scope Configuring "server options" in DHCP (not scope options, server options) Unchecking "respond to clients" and rechecking it - then restating services Unchecking respond to DHCP and BOOTP in the DHCP MMC As I said I finally managed to get RIS working succesfully after a migration for the first time but I have no idea why or which of the above managed to fix the problem. I find the documentation on RIS weak and unhelpfull as it fails to cover DHCP requirements properly. Does anyone know RIS well? Can anyone help me figure out what the requirements actually are, how to troubleshoot it correctly etc etc Any questions, comments, suggestions welcome! Thanks

nope, sure you using the same raid/sata drivers in the two installation media's?

Hi, I was wondering if its possible to deploy via RIS a windows PE image like Sysinternals/Wininternals ERD disk (emergency repair disk) which will boot from RIS? If anyone doesnt know what the ERD is, its basically a windows PE boot CD which takes you into a PE OS and has various tools for troubleshooting fudged operating systems etc Also, is it possible for me to build my own PE "install" with various tools and have this bootable from RIS? If answers the above are yes, could you please tell me where I should start Im finding RIS and PE documentation a bit loosly thrown together and difficult to understand. Once I know which steps I should be taking I can then go find the relevant documentation - I just dont know where to start

not sure if this is possible and I cant remember where you do it, but using the same methods that you would to add scsi/sata raid controller drivers (text mode setup files) can you not add the chipset drivers in at that level, exposing the NIC? Actually, it probably looks for the NIC before it looks for SCSI/RAID controller drivers tbh

try a low level format which will mark the bad sectors as bad and when you try install it wont use those sectors be warned however because bad sectors spread, if the above fixes your problem or anything else you do leads you to beleive that the HDD has bad sectors get rid of the disk and dont risk future data loss

start the service called help and support

bump

the console has a coax input, lavelled coax. the console also does dolby digital decoding etc so I am confident that it supports whatever it needs to. I have used coax on this console before, using a SB Live

Hi, I have an ASUS V6V laptop which according to the specs has a SPDIF output. Looking at the sound settings on the control application that installs itself (Realtek sound manager or something) I can see an option where I can set my sound to No Output, Digital Only or Analogue and Digital output. Regardless of what setting I set this to I can still get sound if I plug in a pair of headphones. I have a creative speaker setup in my room at home which supports dolby digital and various inputs including coax, optical and analogue. I went into a shop yesterday and asked what kind of cable I need to get my laptop working and the guy there seemed to think that because the Asus website says “SPDIF” for my sound card that I should be using a mini-jack to coax cable and plug this into my coax input on my creative speaker console thingy. I cant for the life of me get any sound when I flick my creative console over to coax in regardless of which of the following analogue/spdif outputs I select in the control panel. Does anyone have any ideas on what I should be doing or how I should be setting this up so I can get digital output from my laptop? Thanks

is this a stand alone machine? what OS? If you install from an unattended answer file its better to define this setting there

If you do as chilifrei suggests on point number 3 and create a replica scope on the backup DHCP server enable IP address conflict detection (from memory right click the DHCP server name in DHCP MMC - last tab) because you are going to have clients on your network with addresses which have already been leased and your second DHCP server isn't going to know anything about them to add to this, go into sites and services and right click on the NTDS settings for this backup server once its been promoted and make it a global catalogue. If you loose your first server alltogether then this second server, being a GC will have a copy of everything you will need to rebuild your domain

I dont get why they have to have the same computer name anyway, just build a spare server with the restored database, call it something different and if the original box fails create a static entry in DNS which redirects requests to the backup server. If the applications you are using are reliant on computer names then its only going to take you a few minutes to delete the original account from AD and change the backup servers name to the original name.

169.254 is an APIPA address, if a network connection detects physical connectivity and is configured to use DHCP and it cannot obtain an IP address then it will assign itself an APIPA address randomly. It sounds as if you have DHCP installed on this server, DC, and that it has a scope configured in the 192.x range and that it is bound to the adapter which has assigned intself an APIPA address

chances are your ISP is blocking port 25 not your router if you think your port forwarding is setup correctly. Have a chat with your ISP they will probaby have to do an SMTP relay check before opening up that port for you To answer your other question. No you cant do what you want to do (unless you use ISA firewall) however there are options. 1) forward port 443 to the exchange server and use https:// 2) use your webserver as an OWA server which in turn talks to the exchange server (requires exchange installed on the webserver) in essence this will make your webserver a front-end exchange server 3) if you have multiple IP addresses create a sub domain mail.blah.com and assign that sub domain an alternate IP address 4) use something like ISA server as a firewall which can publish websites running on different servers. For example you can publish server1 as http://blah.com/server1 and server2 as http://blah.com/server2. You need an application level firewall to do this, ISA is the only one I know about which can do this. This does not "forward" ports, it publishes the website - there is a difference 5) if you are running IIS on your webserver you might be able to forward web requests on certain header to another website but Im not sure

Could someone please give me the links you used to get info on booting winpe from RIS please, I want to try this out. Do you think it would be possible to boot Wininternals Emergency Recovery Disk from RIS at all?

Hi, I am having a few issues with RIS and finding it really difficult to find any kind of clarification on the web about some of the issues or queries I am having with RIS If I setup a new domain with a new DHCP server and new DNS servers etc, install RIS on the DHCP server and add an image it seems to work straight away. Every single time I move DHCP to another server RIS just stops working, my PXE clients just stop at "DHCP..." and report that no TFTP filename was recieved I have tried installing RIS on the new DHCP server, re-adding images, running the RIS setup checker thing, restarting services and everything else I can think of and I just cant get RIS to work. I decommision the domain controllers, format the machines and setup a new domain, install RIS and DHCP etc on the same box and it works again. When it comes time to move the DHCP server or RIS to another box it simply just stop working again. I have gone through this same procedure a number of times now and each time I need to make a change to my network (ie move DHCP/DC/RIS) and I end up re-doing my entire domain again. My last effort seems to have been my most succesfull. I manage to move DHCP from the DC/RIS server to another box and RIS stopped working. No matter what I tried I could not get RIS to work again until I moved RIS to the new DHCP server. I have tried this several times without success but this time it did work. Now my questions are, does anyone know exactly how DHCP is supposed to be configured, whether the RIS server itsefl needs DHCP server installed etc etc because Im tired of going round in circles with RIS now and I want to know exactly what its requirements are and how it should be setup. Reading FAQ's on the internet and MS site I can see the same list of troublshooting techniques popping up: one entry is always "make sure the RIS server is authorised in DHCP" and another is "IF DHCP and RIS are on the same server make sure the following resgistry setting is changed....." Judging by the second entry DHCP and RIS do not HAVE to be on the same server otherwise it would not say IF. How then are you supposed to authorise a server in DHCP if it does not have DHCP server installed? Other things I tried before I got it working were: Adding another image to RIS and choosing "use the new client install screens" Restarting RIS services Re-installing DHCP on the original RIS server and then authorising it even though there was no active scope Configuring "server options" in DHCP (not scope options, server options) Unchecking "respond to clients" and rechecking it - then restating services Unchecking respond to DHCP and BOOTP in the DHCP MMC As I said I finally managed to get RIS working succesfully after a migration for the first time but I have no idea why or which of the above managed to fix the problem. I find the documentation on RIS weak and unhelpfull as it fails to cover DHCP requirements properly. Does anyone know RIS well? Can anyone help me figure out what the requirements actually are, how to troubleshoot it correctly etc etc Any questions, comments, suggestions welcome! Thanks

the only reason people recommend making changes to the default domain policy is because it reduces network traffic during site replication. If you are a single site then make your group policy changes as granular as you wish with many many seperate GPO's for all the different setting so you can keep track of things properly. If you are a domain with multiple sites with very slow WAN links than make the bulk of your changes on your default domain policy and only create new GPO's if you need them