Re: IIS install on XP in SBS2003 Domain

Thanks for your help but I figured out that it is not IIS it is a windows
patch that screwed things up with the NIC driver. Installed the newest driver
and it is working now.

"BillB" wrote:

Ipconfig /all shows all of the correct entries compared to any other xp
workstation in the domain. DNS WINS etc all point to the ip address of the
DC. Yes this is before autodesk is installed. THe workstatation is a fully
patched XP SP2 system that is setup using
http://SBSservername/connectcomputer and everything is fine. I then install
IIS using add/remove programs XP setup and then the system will no longer
recognize the DC. If I try using connect computer again it says the system is
already part of the domain and I get a page that there was an error setting
up network contact network administrator. I have reinstalled XP twice now and
the same thing happens everytime I install IIS. Do I need to reinstall SP2
after installing IIS. My XP SP2 is a slipstreamed disk I made from my XP SP1
cd and the SP2 download.

"kj [SBS MVP]" wrote:

BillB wrote:
Thanks Larry but I already checked all of that as well as the binding
order etc. I can still access the network if I input my username and
password when prompted i can ping the DC its just that the XP machine
will not recognize the SBS server as the domain controller once IIS
is installed.


DC's are located using DNS. Post output from ipconfig/all and check the
hosts file for any unusual entries relative to the domain.

This is before you install autodesk, correct?

"Larry Struckmeyer" wrote:

Hi Bill:

I'm pasting in what I have gleaned from this group in the past. Let
us know if any of it seems helpful or relevant. In particular, see
the part toward the end about ghosted devices.

Larry

Per Charlie Russell:
1.) disconnect from all networks by pulling the plug(s)

2.) disable the old NICs. If they're built in, disable them in Device
Manager as well.

3.) shutdown

4.) remove the NICs, if you can, or disable them in the BIOS if
they're built in.

5.) Insert the new Intel NICs.

6.) Power Up.

7.) log in. It'll probably complain, but should let you in to the 500
account. If not, do safe mode.

8.) Let Windows find the new NICs

9.) Assign fixed IP address(s) to the NIC(s)

10.) Run the CEICW.

11.) Reboot.

Should be back to normal.

From Les Conner:

I prefer to power down, install new nic(s), power up and detect.

Disable old nic(s), transfer settings to new.

Run CEICW.

This avoids the usual very lengthy restart when things can't bind to
the NICs.

Disabling the on-board nics in BIOS is optional, but does prevent
accidentally enabling them from the OS later.

I didn't mention the cleanup ;-).

It's likely that the bios disabled nics remain in device manager as
ghosted nics, and this can cause some later issues. They should be
removed by showing non-present devices and show hidden devices, and
removed.

The advantage to the loopback adapters is that services don't balk,
keeping the event log red bangs to a minimum. They are also useful
if doing a forklift to new hardware (or virtualizing a physical
server).

But for a simple nic swap, I agree - loopbacks don't offer a huge
advantage.


"BillB" <BillB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F7039756-1FF6-4EF8-86FB-8EB50D325BEA@xxxxxxxxxxxxxxxx
I hope someone can help me with this. I am trying to setup a new XP
SP2 CAD workstation in a SBS2003 Domain. Part of the autodesk setup
is a program called Vault which requires IIS to be installed on the
workstation. As soon
as I install IIS on the xp machine I can no longer log onto the
domain instead the system logs on using cached credentials and
everytime I try to access a the server or another domain computer I
am prompted for a user name
and password. I tried changing the network setup to a workgroup and
then retry joining the domain but I get an error that a domain
controller for the
domain cannot be found. I followed the help instructions to check
DNS settings but I can see nothing wrong. Nslookup lists the proper
server name
and IP address. Does anyone know how to fix this problem or is this
a limitation of SBS2003. Thanks in advance for any assistance that
can be provided.

--
/kj



.

Relevant Pages

  • Re: IIS install on XP in SBS2003 Domain
    ... the same thing happens everytime I install IIS. ... disable the old NICs. ... Disabling the on-board nics in BIOS is optional, ... SP2 CAD workstation in a SBS2003 Domain. ...
    (microsoft.public.windows.server.sbs)
  • Re: IIS install on XP in SBS2003 Domain
    ... install IIS using add/remove programs XP setup and then the system ... happens everytime I install IIS. ... disable the old NICs. ... Disabling the on-board nics in BIOS is optional, ...
    (microsoft.public.windows.server.sbs)
  • Re: IIS install on XP in SBS2003 Domain
    ... I can still access the network if I input my username and ... disable the old NICs. ... I prefer to power down, install new nic, power up and detect. ... Disabling the on-board nics in BIOS is optional, ...
    (microsoft.public.windows.server.sbs)
  • Re: IIS install on XP in SBS2003 Domain
    ... disable the old NICs. ... I prefer to power down, install new nic, power up and detect. ... Disabling the on-board nics in BIOS is optional, ... I tried changing the network setup to a workgroup and then ...
    (microsoft.public.windows.server.sbs)
  • RE: Weird update problems (XP Pro, SP2 and non)
    ... you can download from Microsoft the Microsoft installer cleanup ... Try installing again at the web site with IIS ... > disabling the client allows me to download and isntall critical updates ... > (I've found in the past that I could install optional updates, ...
    (microsoft.public.windowsupdate)