Re: Windows Lies
From: Jim Carlock (anonymous_at_127.0.0.1)
Date: 04/17/04
- Next message: Ken Blake, MVP: "Re: new installation of XP home over Windows ME"
- Previous message: Bill Chatfield: "Re: Critical Update installs OK but then appears again..."
- In reply to: Bruce Chambers: "Re: Windows Lies"
- Next in thread: Bruce Chambers: "Re: Windows Lies"
- Reply: Bruce Chambers: "Re: Windows Lies"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 17 Apr 2004 17:39:44 -0400
:-)
I can switch to another adapter. There are multiple adapters
on the machine. The domain controller is a Win2K machine.
I know there is an SID problem. And I'm pretty sure that is
what is causing the Win2K domain controller to not see the
machine, because I get a trust failure when I try to log on to
the XP machine.
The network card is working fine. There don't seem to be
any issues with sending information back and forth. It knows
its IP address, grabs its IP address and all the appropriate
information about the domain servers, ie DHCP, DNS, and
is assigned the Wins server in the TCPIP settings.
It sees the server, and the server sees it. There's just an SID
problem, that is preventing the pre-existing trust to work or
something along that line.
The drivers are XP specific with a 2001 October date on
them. I'm almost 100% sure it has nothing to do with the
drivers. :-) In fact, I'll just make myself 110% sure and
turn on the other NIC. ;-)
The other adapter is:
ASUSTeK/Broadcom 440x 10/100 Integrated Controller
And its got a different IP address, but everything is just as
it was with the initial adapter.
-- Jim Carlock http://www.microcosmotalk.com/ Post replies to the newsgroup. "Bruce Chambers" <bchambers@nospamcableone.net> wrote... Greetings -- What version of WinXP do you have? WinXP Home isn't designed to be part of a domain. Also, what kind of domain is it? There are some minor issues using WinXP Pro on a WinNT domain. For what it's worth, NetBEUI is of very little use on modern networks, particularly any large enough to have a domain server, as it's not routable. Curiously, and perhaps more to the point, considering your networking problems, I can find no mention on LinkSys' web site of that specific NIC being supported on WinXP. There's plenty of mention for Win95 and Win98 support, as well as some support for Win2K, but nothing about WinXP, except a non-functional link to a LinkSys KB article, and a claim to support WinXP on a marketing Datasheet. Were you able to get WinXP-specific drivers for it? The newest version of drivers I can see were released several months _before_ WinXP went onto the market. Bruce Chambers -- Help us help you: http://dts-l.org/goodpost.htm http://www.catb.org/~esr/faqs/smart-questions.html You can have peace. Or you can have freedom. Don't ever count on having both at once. -- RAH "Jim Carlock" <anonymous@127.0.0.1> wrote in message news:OJq2%237KJEHA.624@TK2MSFTNGP11.phx.gbl... > Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4) > > There are some definite networking issues that are present. > For one I'm hooked up to a domain that only partially > acknowledges the connection, meaning this computer is NOT > visible as a system on the network in domain, but DNS knows > it's here and DHCP knows it's here, but Wins does not know > it exists. Perhaps thats because NetBIOS / NetBui is not > configured. I can see all systems on the network but noone > can see me, unless you go into the DHCP server and see the > assignment there, or see the records in the DNS server. > > It's working fine otherwise. > > -- > Jim Carlock > http://www.microcosmotalk.com/ > Post replies to the newsgroup. > > > "Bruce Chambers" <bchambers@nospamcableone.net> wrote in message > news:1082v7rhrhckm1e@corp.supernews.com... > Greetings -- > > Yes, I am currently using WinXP's SP2-RC1, which accounts for the > different OE build number. However, I don't recall ever > experiencing > the specific problem you describe even when I was using any of the > earlier OE builds. (Not that I make a habit of disconnecting my > network cable in the middle of using the network connection. <vbg>) > > It could, as you suggest, be something unique to your > system/configuration. What particular NIC and version of its > drivers > are you using? > > > Bruce Chambers > > -- > Help us help you: > http://dts-l.org/goodpost.htm > http://www.catb.org/~esr/faqs/smart-questions.html > > > You can have peace. Or you can have freedom. Don't ever count on > having both at once. -- RAH > > > "Jim Carlock" <anonymous@127.0.0.1> wrote in message > news:eM3KJGKJEHA.2380@TK2MSFTNGP09.phx.gbl... >> Must be something specific to my machine then. Wondering... >> >> I'm looking at the news read header information. >> >> SPINNER: >> X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 >> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 >> (?) >> >> BRUCE: >> X-Newsreader: Microsoft Outlook Express 6.00.2900.2096 >> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2096 >> XP-Pro SP2-beta (?) >> >> ME: >> X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 >> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 >> XP-Pro >> >> I think Bruce indicated he is using the beta version of SP2. I >> thought my system had the current updates/files but it doesn't >> look that way. >> >> -- >> Jim Carlock >> http://www.microcosmotalk.com/ >> Post replies to the newsgroup. >> >> > > >
- Next message: Ken Blake, MVP: "Re: new installation of XP home over Windows ME"
- Previous message: Bill Chatfield: "Re: Critical Update installs OK but then appears again..."
- In reply to: Bruce Chambers: "Re: Windows Lies"
- Next in thread: Bruce Chambers: "Re: Windows Lies"
- Reply: Bruce Chambers: "Re: Windows Lies"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|