COERCITAS

Hello all, I tried to use the BDD 2007 tool to deploy Windows XP but I encounter some problems. I am not dealing with the drivers issue, I can boot from the WDS server on the network without any problem. My issue happens later, when the HTA page should spawn...this page isn't populated at all, everything is blank. I tried this with ESX 3.0 and VMWare Server 1.0.3 and the problem is the same. When I use the same server to deploy the image on a laptop (thus NOT a VMWare client), everything work perfectly... Am I missing something ? Regards.

You should consider updating to XP or 2003, 2000 won't be supported that long and you have to admit XP / 2003 are far better OSes.

The only advice I could give you with those informations would be to follow OSI Model checks...I mean start to check hardware / cable and then, climb up every step until you find the problem. For what I can tell, it could be a cable problem, an interface problem, a switch / hub problem, etc...if it isn't, it can be a speed / duplex problem (autonegociation isn't always your best friend ).

Not to mention Cisco's PIX is only a filtering firewall, there is no higher layer filter built in. For the cost, I would recommend Checkpoint or ISA Server 2004 but it is something that may be discussed (PIX have its advantages, ISA or Checkpoint have theirs). Another solution could be BSD (best one if you ask me is OpenBSD but FreeBSD isn't that bad, never tried NetBSD) or (argh !) Linux, cheaper (well, free actually) but no support. If cost isn't your main concern and if you only use Microsoft products, go with ISA Server 2004, it is a very very very good Proxy / Firewall (ppl stating the opposite never even tried it, I used to be a Checkpoint / Borderware fan, I am now an ISA fan).

Absolutely (hello btw ), but you still can assign several IP addresses to the same interface PS : the reason is that regular HTTP header is containing site's name if needed, so you can have more than one HTTP ONLY site on the same IP address (thus, only the site's name will separate them) BUT HTTPS is "only" dealing with IP address, thus you can't have 2 different HTTPS sites on the same IP address (non sense). This is easily bypassed just by adding another IP address to the interface and then, assign said site to its own IP address (you can't stay with the default ANY setting in that case).