Hi Guys, Thanks for the replies.
It seems Kirk(Jantzer) was correct. For whatever reason when I put the xen tools into the template it got a link-local address. When I placed them to install with the sysprep answer file it worked as expected. Thanks! Ian On 15 July 2013 01:45, Kirk Jantzer <[email protected]> wrote: > Ian - As the other Kirk said (I don't get to say that often :-P), if it's > getting that kind of IP, it could mean the NIC drivers aren't getting > installed correctly. I've found Windows works better in CS when you run > post scripts that are kicked off via a sysprep answer file, rather than > just wrapping things up in an image. > > > On Sun, Jul 14, 2013 at 6:58 PM, Kirk Kosinski <[email protected]>wrote: > >> Hi, Ian. Is it getting an 169.254.x.x IP? If so, it means it cannot get >> an IP via DHCP. In this case, try setting the IP manually to the IP it >> should have, then try to diagnose network connectivity (ping virtual >> router, ping other VMs, etc.). >> >> Best regards, >> Kirk >> >> On 07/14/2013 03:39 PM, Ian Duffy wrote: >> > Hi, >> > >> > I'm using Cloudstack 4.1 and Xenserver 6.0.2. >> > >> > I Installed windows server 2008 R2 with xenserver tools and cloud.com >> > VM instance tools. >> > syspreped it with "Enter System out of box experience" + Generalize. >> > Shutdown the machine and created a template. >> > >> > I created an instance using the template and the instance came up but: >> > 1) It had a different IP address to the one given in Cloudstack >> > 2) No gateway was set >> > >> > Any idea why this is happening and how to fix it? >> > >> > Thanks, >> > >> > Ian >> > >> > > > > -- > Regards, > > Kirk Jantzer > c: (678) 561-5475 > http://about.met/kirkjantzer
