98 to XP networking

When starting up my 98 computer, I always see a log on
screen that asked for a domain name and password. I have
not set up a domain.

When I try to just enter a return, I get a message:
"No domain server available to verify password".

I have not set up any domain's to my knowledge and am
trying to use Microsoft Networking with the MSHOME
workgroup.

My 98 computer can see the XP computer if I use find
computer but the XP computer does not show up on network
neighborhood.

The XP computer cannot see the 98 computer eitehr in
network neighborhood or with find computer.

I've tried deleting and reinstalling all services without
success.

Any ideas?




ron with a problem

Your suggestion solved my domain problem. I no longer
get a missing domain message. I am still not able to see
the win98 computer from the XP computer. I can ping it
successfully but it doesn't show up when I search for
network computers. Likewise, I cannot see the XP
computer from the 98 computer on the network neighborhood
list but I can find it when I search for it.

The 98 computer has two TCP/IP's enabled, one for the
dial up adapter and one for the ethernet adapter. I also
notice that DNS is disabled. Is this correct?

What else should I be doing?

Thanks,

Ron


>-----Original Message-----
>In article <6b6d01c35856$f29293f0
$(E-Mail Removed)>, "ron with a
>problem" <(E-Mail Removed)> wrote:
>>When starting up my 98 computer, I always see a log on
>>screen that asked for a domain name and password. I
have
>>not set up a domain.
>>
>>When I try to just enter a return, I get a message:
>>"No domain server available to verify password".
>>
>>I have not set up any domain's to my knowledge and am
>>trying to use Microsoft Networking with the MSHOME
>>workgroup.
>>
>>My 98 computer can see the XP computer if I use find
>>computer but the XP computer does not show up on
network
>>neighborhood.
>>
>>The XP computer cannot see the 98 computer eitehr in
>>network neighborhood or with find computer.
>>
>>I've tried deleting and reinstalling all services
without
>>success.
>>
>>Any ideas?
>
>On 98, go to Control Panel | Network | Client for
Microsoft Networks |
>Properties and clear all of the Windows NT Domain boxes.
>
>Permanently disable XP's built-in Internet Connection
Firewall on
>local area network connections -- it's for use only on a
direct modem
>connection to the Internet. Disable and un-install all
other
>firewalls while troubleshooting.
>
>Use only one for File and Printer Sharing. If the
network needs more
>than one protocol, unbind File and Printer Sharing from
all but one of
>them.
>
>Make sure that NetBIOS over TCP/IP is enabled on all
computers.
>--
>Best Wishes,
>Steve Winograd, MS-MVP (Windows Networking)
>
>Please post any reply as a follow-up message in the news
group
>for everyone to see. I'm sorry, but I don't answer
questions
>addressed directly to me in E-mail or news groups.
>
>Microsoft Most Valuable Professional - Windows Networking
>http://mvp.support.microsoft.com
>
>Steve Winograd's Networking FAQ
>http://www.bcmaven.com/networking/faq.htm
>.
>

In article <004701c35b6f$36f1f570$(E-Mail Removed)>, "ronwithaproblem"
<(E-Mail Removed)> wrote:
>Your suggestion solved my domain problem. I no longer
>get a missing domain message. I am still not able to see
>the win98 computer from the XP computer. I can ping it
>successfully but it doesn't show up when I search for
>network computers. Likewise, I cannot see the XP
>computer from the 98 computer on the network neighborhood
>list but I can find it when I search for it.
>
>The 98 computer has two TCP/IP's enabled, one for the
>dial up adapter and one for the ethernet adapter. I also
>notice that DNS is disabled. Is this correct?
>
>What else should I be doing?
>
>Thanks,
>
>Ron

It's normal to have separate TCP/IP bindings for each network adapter,
and it's normal for DNS to be disabled when a network adapter gets its
TCP/IP configuration automatically from a DHCP server.

Here are some steps that should help get everything working:

1. Permanently disable XP's built-in Internet Connection Firewall on
local area network connections -- it's for use only on a direct modem
connection to the Internet. Disable and un-install all other
firewalls while troubleshooting. Details here:

Windows XP Internet Connection Firewall
http://www.practicallynetworked.com/...c_firewall.htm

2. Use only one protocol for File and Printer Sharing. If the network
needs more than one protocol, unbind File and Printer Sharing from all
but one of them. Details here:

Windows XP Network Protocols
http://www.practicallynetworked.com/..._protocols.htm

3. Make sure that NetBIOS over TCP/IP is enabled on all computers.
Details here:

Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/...hoot/netbt.htm
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

I have another suggestion.
I don't know why Steve hasn't mentioned this.
From what I understand, file sharing from 9x to NT-based *requires*
NetBEUI to be installed.
Network (config panel) -> Add -> Protocol -> Microsoft -> NetBEUI
See if that works.


ronwithaproblem wrote:

> Your suggestion solved my domain problem. I no longer
> get a missing domain message. I am still not able to see
> the win98 computer from the XP computer. I can ping it
> successfully but it doesn't show up when I search for
> network computers. Likewise, I cannot see the XP
> computer from the 98 computer on the network neighborhood
> list but I can find it when I search for it.
>
> The 98 computer has two TCP/IP's enabled, one for the
> dial up adapter and one for the ethernet adapter. I also
> notice that DNS is disabled. Is this correct?
>
> What else should I be doing?
>
> Thanks,
>
> Ron
>
>
>
>>-----Original Message-----
>>In article <6b6d01c35856$f29293f0
>
> $(E-Mail Removed)>, "ron with a
>
>>problem" <(E-Mail Removed)> wrote:
>>
>>>When starting up my 98 computer, I always see a log on
>>>screen that asked for a domain name and password. I
>
> have
>
>>>not set up a domain.
>>>
>>>When I try to just enter a return, I get a message:
>>>"No domain server available to verify password".
>>>
>>>I have not set up any domain's to my knowledge and am
>>>trying to use Microsoft Networking with the MSHOME
>>>workgroup.
>>>
>>>My 98 computer can see the XP computer if I use find
>>>computer but the XP computer does not show up on
>
> network
>
>>>neighborhood.
>>>
>>>The XP computer cannot see the 98 computer eitehr in
>>>network neighborhood or with find computer.
>>>
>>>I've tried deleting and reinstalling all services
>
> without
>
>>>success.
>>>
>>>Any ideas?
>>
>>On 98, go to Control Panel | Network | Client for
>
> Microsoft Networks |
>
>>Properties and clear all of the Windows NT Domain boxes.
>>
>>Permanently disable XP's built-in Internet Connection
>
> Firewall on
>
>>local area network connections -- it's for use only on a
>
> direct modem
>
>>connection to the Internet. Disable and un-install all
>
> other
>
>>firewalls while troubleshooting.
>>
>>Use only one for File and Printer Sharing. If the
>
> network needs more
>
>>than one protocol, unbind File and Printer Sharing from
>
> all but one of
>
>>them.
>>
>>Make sure that NetBIOS over TCP/IP is enabled on all
>
> computers.
>
>>--
>>Best Wishes,
>>Steve Winograd, MS-MVP (Windows Networking)
>>
>>Please post any reply as a follow-up message in the news
>
> group
>
>>for everyone to see. I'm sorry, but I don't answer
>
> questions
>
>>addressed directly to me in E-mail or news groups.
>>
>>Microsoft Most Valuable Professional - Windows Networking
>>http://mvp.support.microsoft.com
>>
>>Steve Winograd's Networking FAQ
>>http://www.bcmaven.com/networking/faq.htm
>>.
>>

In article
<2zEZa.114494$(E-Mail Removed). rogers.com>,
OneMouseTooMany <(E-Mail Removed)> wrote:
>I have another suggestion.
>I don't know why Steve hasn't mentioned this.
> From what I understand, file sharing from 9x to NT-based *requires*
>NetBEUI to be installed.
>Network (config panel) -> Add -> Protocol -> Microsoft -> NetBEUI
>See if that works.

Nothing in Windows networking requires, or has ever required, NetBEUI
to be installed. All versions of Windows can network with each other
using TCP/IP as the only network protocol.

Are you thinking of NetBIOS? Windows 9x/NT networking requires
NetBIOS, which isn't a protocol. It's an applications programming
interface that runs over any of the protocols: TCP/IP, NetBEUI, or
IPX/SPX.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

In article <eCakke#(E-Mail Removed)>, "Bob Byrne"
<(E-Mail Removed)> wrote:
>Steve Winograd [MVP] <(E-Mail Removed)> wrote:
>> Nothing in Windows networking requires, or has ever required, NetBEUI
>> to be installed. All versions of Windows can network with each other
>> using TCP/IP as the only network protocol.
>
>I couldn't get my XP host to connect to my Win98SE client without
>installing NetBEUI. To make sure I removed NetBEUI from the client
>to leave only TCP/IP and lost my connection. Reinstalled NetBEUI and
>it returned. Perhaps it's not NetBEUI itself but a by-product of it's
>installation that does it.

It's OK to use NetBEUI, Bob, but it's not necessary. If a network
only works after installing NetBEUI, something's wrong with its TCP/IP
configuration, and installing NetBEUI hides the problem.

I do network consulting, and I always remove NetBEUI when I find it on
a client's network. I've worked on lots of Windows networks, and
every one of them works with just TCP/IP.

Here are the some likely fixes for TCP/IP problems:

1. Permanently disable XP's built-in Internet Connection Firewall on
local area network connections -- it's for use only on a direct modem
connection to the Internet. Disable and un-install all other firewall
programs while troubleshooting. Details here:

Windows XP Internet Connection Firewall
http://www.practicallynetworked.com/...c_firewall.htm

2. Make sure that NetBIOS over TCP/IP is enabled on all computers, as
shown here:

Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/...hoot/netbt.htm
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

I may have confused NetBIOS and NetBEUI in whatever I read (happens to
me sometimes), but I don't think I have.
I've noticed the same behaviour as mentioned by Bob

Steve Winograd [MVP] wrote:
>
> Nothing in Windows networking requires, or has ever required, NetBEUI
> to be installed. All versions of Windows can network with each other
> using TCP/IP as the only network protocol.
>
> Are you thinking of NetBIOS? Windows 9x/NT networking requires
> NetBIOS, which isn't a protocol. It's an applications programming
> interface that runs over any of the protocols: TCP/IP, NetBEUI, or
> IPX/SPX.

Steve Winograd [MVP] <(E-Mail Removed)> wrote:
> It's OK to use NetBEUI, Bob, but it's not necessary. If a network
> only works after installing NetBEUI, something's wrong with its TCP/IP
> configuration, and installing NetBEUI hides the problem.
> .....

Well knock me over with a feather, I deleted NetBEUI and it works.
I remember seeing a setting when troubleshooting TCP/IP in Win98 that was
"Make TCP/IP the default". I think this may have been a contributing factor
if not checked.

--
Bob

In article <(E-Mail Removed)>, "Bob Byrne"
<(E-Mail Removed)> wrote:
>Steve Winograd [MVP] <(E-Mail Removed)> wrote:
>> It's OK to use NetBEUI, Bob, but it's not necessary. If a network
>> only works after installing NetBEUI, something's wrong with its TCP/IP
>> configuration, and installing NetBEUI hides the problem.
>
>Well knock me over with a feather, I deleted NetBEUI and it works.
>I remember seeing a setting when troubleshooting TCP/IP in Win98 that was
>"Make TCP/IP the default". I think this may have been a contributing factor
>if not checked.

Bingo! I'd forgotten about that setting, which is "Set this protocol
to be the default protocol" and appears on the Advanced tab of the
TCP/IP properties. Thanks for pointing it out.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm