Prev: Changing Domain Name through Internet Address Management Wizard
Next: redirect users folders sbs2008
From: Andrew M. Saucci, Jr. on 16 Apr 2010 23:04
After installing a large number of updates on an SBS 2000 that
hadn't been updated in a while, I was told that the DOS-based line of
business application was painfully slow, which I was able to verify for
myself. The only big thing I can find wrong is that WINS is showing the IP
of the WAN adapter instead of the IP of the LAN adapter, but KB 292822 was
implemented many moons ago. I reviewed it anyway, but all the necessary
registry entries are still there. I tried clearing the WINS database, but
the incorrect enties returned. DNS looks okay.

At the same time, we installed a TeraStation with two network
adapters, which insists on registering a 169.254.x.x address for the unused
adapter in WINS instead of the IP of the one we're using. Could this be
related? How might one troubleshoot this? I see nothing relevant in the
event viewer. It's taking fifteen minutes to generate a report that should
take only a minute or two. Right now it looks as though I have to guess,
which is a painful way to resolve a problem.


From: Susan Bradley on 16 Apr 2010 23:27
Andrew M. Saucci, Jr. wrote:
> After installing a large number of updates on an SBS 2000 that
> hadn't been updated in a while, I was told that the DOS-based line of
> business application was painfully slow, which I was able to verify for
> myself. The only big thing I can find wrong is that WINS is showing the IP
> of the WAN adapter instead of the IP of the LAN adapter, but KB 292822 was
> implemented many moons ago. I reviewed it anyway, but all the necessary
> registry entries are still there. I tried clearing the WINS database, but
> the incorrect enties returned. DNS looks okay.
>
> At the same time, we installed a TeraStation with two network
> adapters, which insists on registering a 169.254.x.x address for the unused
> adapter in WINS instead of the IP of the one we're using. Could this be
> related? How might one troubleshoot this? I see nothing relevant in the
> event viewer. It's taking fifteen minutes to generate a report that should
> take only a minute or two. Right now it looks as though I have to guess,
> which is a painful way to resolve a problem.
>
>
>
I think I'd be planning on retiring it, not patching it.
You did check binding order right?
From: SuperGumby [SBS MVP] on 17 Apr 2010 08:03
the changes suggested by 292822 are valid for all DC's having multiple
interfaces.

Maybe the advanced properties of the external NIC are set to register.

"Andrew M. Saucci, Jr." <spam-only(a)2000computer.local> wrote in message
news:%235%23p6qd3KHA.1452(a)TK2MSFTNGP06.phx.gbl...
> After installing a large number of updates on an SBS 2000 that
> hadn't been updated in a while, I was told that the DOS-based line of
> business application was painfully slow, which I was able to verify for
> myself. The only big thing I can find wrong is that WINS is showing the IP
> of the WAN adapter instead of the IP of the LAN adapter, but KB 292822 was
> implemented many moons ago. I reviewed it anyway, but all the necessary
> registry entries are still there. I tried clearing the WINS database, but
> the incorrect enties returned. DNS looks okay.
>
> At the same time, we installed a TeraStation with two network
> adapters, which insists on registering a 169.254.x.x address for the
> unused adapter in WINS instead of the IP of the one we're using. Could
> this be related? How might one troubleshoot this? I see nothing relevant
> in the event viewer. It's taking fifteen minutes to generate a report that
> should take only a minute or two. Right now it looks as though I have to
> guess, which is a painful way to resolve a problem.
>


From: Andrew M. Saucci, Jr. on 17 Apr 2010 12:50
I just looked at that-- WINS is blank on the WAN adapter. Good
thought, though.

"SuperGumby [SBS MVP]" <not(a)your.nellie> wrote in message
news:uQ5LGZi3KHA.4016(a)TK2MSFTNGP05.phx.gbl...
> the changes suggested by 292822 are valid for all DC's having multiple
> interfaces.
>
> Maybe the advanced properties of the external NIC are set to register.
>
> "Andrew M. Saucci, Jr." <spam-only(a)2000computer.local> wrote in message
> news:%235%23p6qd3KHA.1452(a)TK2MSFTNGP06.phx.gbl...
>> After installing a large number of updates on an SBS 2000 that
>> hadn't been updated in a while, I was told that the DOS-based line of
>> business application was painfully slow, which I was able to verify for
>> myself. The only big thing I can find wrong is that WINS is showing the
>> IP of the WAN adapter instead of the IP of the LAN adapter, but KB 292822
>> was implemented many moons ago. I reviewed it anyway, but all the
>> necessary registry entries are still there. I tried clearing the WINS
>> database, but the incorrect enties returned. DNS looks okay.
>>
>> At the same time, we installed a TeraStation with two network
>> adapters, which insists on registering a 169.254.x.x address for the
>> unused adapter in WINS instead of the IP of the one we're using. Could
>> this be related? How might one troubleshoot this? I see nothing relevant
>> in the event viewer. It's taking fifteen minutes to generate a report
>> that should take only a minute or two. Right now it looks as though I
>> have to guess, which is a painful way to resolve a problem.
>>
>
>


From: Andrew M. Saucci, Jr. on 17 Apr 2010 12:53
This client is not likely to go for a new server unless the old one
becomes totally inoperative. It was running fine until two weeks ago. I may
have to call Microsoft and try to get free help as an issue related to
security updates, but who knows where to begin?

"Susan Bradley" <sbradcpa(a)pacbell.net> wrote in message
news:ON7Rn3d3KHA.4964(a)TK2MSFTNGP05.phx.gbl...
> Andrew M. Saucci, Jr. wrote:
>> After installing a large number of updates on an SBS 2000 that
>> hadn't been updated in a while, I was told that the DOS-based line of
>> business application was painfully slow, which I was able to verify for
>> myself. The only big thing I can find wrong is that WINS is showing the
>> IP of the WAN adapter instead of the IP of the LAN adapter, but KB 292822
>> was implemented many moons ago. I reviewed it anyway, but all the
>> necessary registry entries are still there. I tried clearing the WINS
>> database, but the incorrect enties returned. DNS looks okay.
>>
>> At the same time, we installed a TeraStation with two network
>> adapters, which insists on registering a 169.254.x.x address for the
>> unused adapter in WINS instead of the IP of the one we're using. Could
>> this be related? How might one troubleshoot this? I see nothing relevant
>> in the event viewer. It's taking fifteen minutes to generate a report
>> that should take only a minute or two. Right now it looks as though I
>> have to guess, which is a painful way to resolve a problem.
>>
>>
> I think I'd be planning on retiring it, not patching it.
> You did check binding order right?


 |  Next  |  Last
Pages: 1 2
Prev: Changing Domain Name through Internet Address Management Wizard
Next: redirect users folders sbs2008