Re: IIS install on XP in SBS2003 Domain
- From: "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com>
- Date: Wed, 29 Aug 2007 12:07:12 -0400
Hmmm... this answer belongs in the thread below. Sorry.
"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message
news:OdAp%23Vl6HHA.2632@xxxxxxxxxxxxxxxxxxxxxxx
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.
.
- References:
- Re: IIS install on XP in SBS2003 Domain
- From: Larry Struckmeyer
- Re: IIS install on XP in SBS2003 Domain
- Prev by Date: Re: Push email to Vodafone v1415
- Next by Date: Re: Remote Access Wizard Error
- Previous by thread: Re: IIS install on XP in SBS2003 Domain
- Next by thread: Re: IIS install on XP in SBS2003 Domain
- Index(es):
Relevant Pages
|
Loading
