Network with Windows XP and 2000 Pro

Thanks Carey and Steve! I will try your suggestions as soon as I get home. I
have no doubt we will figure this thing out.

In the mean time, let me give you guys an overview of what I have going on
so you can get an idea of what I'm doing.

I have created a test lab at my house in order to learn more about how all
these things work. I run a small business fixing computers. I want to learn
more about networking, so I set up this lab just to figure out problems like
I'm having now. That way if I should run into a problem like this on a job, I
will know what to do.

Here is a run down of the lab:

TestLab1 computer is dual boot with Windows 98SE and Windows 200 Pro. Each
OS is named TestLab1-98 and TestLab1-2K on the network and belongs to a
workgroup named TestLab.

TestLab2 computer is not up and running yet. I am planning to install
FreeBSD and use Samba to create primary domain controller. The reason for
this is that I have a project to do in the next several months for a church
with 8 computers. They want some sort of PDC network, but don't have much
money to spend.

TestLab3 computer is dual boot with Windows XP Pro and Windows NT 4.0. Each
OS is named TestLab3-XP and TestLab3-NT on the network and belongs to the
workgroup TestLab.

TestLab4 computer is a dual boot with Windows ME and Ubuntu Linux. Each OS
is named TestLab4-ME and TestLab4-UL on the network and belong to the work
group TestLab.

TestLab2, 3 and 4 are wired to a Belkin basestation with 4 wired ports.
TestLab1 has the NetGear wireless PCI adapter that also connects the Belkin
basestation.

I have a Sony laptop that is connected to my HomeNetwork. My HomeNetwork
uses a Microsoft wirless basestation that shares cable internet access. The
laptop has a Microsoft PC Card wirless adapter. I connect a crossover cable
from the internal ethernet card in the laptop to the WAN port of the Belkin
router. I set up ICS on the laptop and it distributes the internet to my
TestLab from my HomeNetwork.

Also, sorry this is so long, here are another couple of things I did last
night. I shutdown TestLab3-XP and rebooted into TestLab3-NT. TestLab3-NT was
not able to see TestLab1-98, but was able to see TestLab1-2K when I rebooted
into that.

Likewise, TestLab4-UL was able to see TestLab3-XP, TestLab3-NT and
TestLab1-2K in any combination, but was never able to see TestLab1-98.

I have not tried TestLab4-ME yet, but am curious to see what happens since
it is most like Windows 98. The only consistant thing I have found so far is
the Windows 98 is not communicating. But, the fact that I can manually
connect to 98 from the XP (//TestLab1-98/c) confuses things for me. To make
it worse, whe I go to the router configuration and look at the DHCP client
list, TestLab1-98 is there. 98 must be on the network, but cannot see or be
seen and cannot access the internet or the router configuration.

Thanks!

"Keith" wrote:

Ok, here is the latest. I am currently posting from the Windows XP machine.
Therfore, obviously, I can get on the network which shares internet access.

First I checked all the suggestions from Steve. Everything was as it should
be, but still no Win 98 computer in Network Places. I went to "Add Network
PLace" and typed in \\testlab1-98 (the computer's name) and it found it! I'm
not sure why it didn't find it automatically, but I can now access the 98
computer from the XP computer.

Second, I went to the 98 computer and checked the Network Neighborhood. I
opened the Entire Network and there was no XP computer. I went to Run and
tried to connect manually, but it wouldn't work that way either.

I then did steps 4 and 5 at Carey's website
(www.careyholzman.com/netfixes.htm). All the registry entries and everything
were as they should be, so I didn't change much. After doing those things,
still no XP computer. So, I tried to see if I could access the internet and
that didn't work.

I rebooted into Windows 2000 and was able to see the XP computer and get on
the internet. So, I figured it was a Windows 98 problem or maybe the wirless
adapter drivers weren't set up correctly in Windows 98.

I checked the device manager and the network adapter was working fine and
recieving a signal. I looked at the NetGear website and searched for the
model number, WG311v2, and didn't find any issued with Windows 98.

The other fishy thing is that I cannot access my router configuration screen
when I type 192.168.2.1 in Iternet Explorer. I can in every other OS, just
not when I'm in 98. I'm trying hard to figure it out myself, but I don't know
what to do next.

Thanks!

"Keith" wrote:

I have read through several posts and some are similar to my question, but
not exactly.

I have 2 computers one with Windows XP and the other is a dual boot with
Windows 2000 Pro and 98 SE. I set up a wirless PCI card in the dual boot
computer and the XP machine is hard wired to the router.

I first booted into Windows 2000 and setup the card. Once done, I went to
network neighborhood and I could see the XP machine. I went to the XP machine
and I could see the 2000 Pro system. So, that was a good thing!

After, I rebooted into 98SE. I set up the card the same way and connected to
the network sucessfully. I went to Network Neighborhood, but could not see
the XP machine. I went to the XP machine and could not see the 98SE. So, that
was not a good thing!

Is there something in 98 that I must set that is not necessary to do in
2000? Is it because 98 cannot see NTFS file systems, and that is why 98
cannot see XP? But, if that were the case XP should still be able to see 98.

Thanks!

Ok, I have discovered something interesting! I have done all things
suggested. Everything was the way it was supposed to be except one thing.
When I typed ipconfig /all in Windows XP the NodeType was unknown. I added
the parameter as specified by Steve. I added NodeType as a DWORD with an
attribute of 1 for broadcast. After I rebooted, I went back to ipconfig and
NodeType was broadcast. But, still no dice.

I went into Device Manager and disabled the NetGear wireless PCI adapter. So
now I was only working with the on-board 3Com Ethernet. I made the RJ-45
connection from the router to the computer and checked Network Neighborhood.
Instantly I was able to see the XP computer. I went to the XP computer and
was instantly able to see the 98 computer.

After, I re-enabled the wirless card and unplugged the RJ-45 connection.
Then, went to Network Neighborhood and saw nothing AGAIN!

I have a few ideas I want to try, but first, I must watch The Apprentice. lol

If any of you guys happen to read this in the mean time, please add any of
your own ideas on the matter.

Thanks!



"Keith" wrote:

I have read through several posts and some are similar to my question, but
not exactly.

I have 2 computers one with Windows XP and the other is a dual boot with
Windows 2000 Pro and 98 SE. I set up a wirless PCI card in the dual boot
computer and the XP machine is hard wired to the router.

I first booted into Windows 2000 and setup the card. Once done, I went to
network neighborhood and I could see the XP machine. I went to the XP machine
and I could see the 2000 Pro system. So, that was a good thing!

After, I rebooted into 98SE. I set up the card the same way and connected to
the network sucessfully. I went to Network Neighborhood, but could not see
the XP machine. I went to the XP machine and could not see the 98SE. So, that
was not a good thing!

Is there something in 98 that I must set that is not necessary to do in
2000? Is it because 98 cannot see NTFS file systems, and that is why 98
cannot see XP? But, if that were the case XP should still be able to see 98.

Thanks!

Ok, I have discovered something interesting! I have done all things
suggested. Everything was the way it was supposed to be except one thing.
When I typed ipconfig /all in Windows XP the NodeType was unknown. I added
the parameter as specified by Steve. I added NodeType as a DWORD with an
attribute of 1 for broadcast. After I rebooted, I went back to ipconfig and
NodeType was broadcast. But, still no dice.

I went into Device Manager and disabled the NetGear wireless PCI adapter. So
now I was only working with the on-board 3Com Ethernet. I made the RJ-45
connection from the router to the computer and checked Network Neighborhood.
Instantly I was able to see the XP computer. I went to the XP computer and
was instantly able to see the 98 computer.

After, I re-enabled the wirless card and unplugged the RJ-45 connection.
Then, went to Network Neighborhood and saw nothing AGAIN!

I have a few ideas I want to try, but first, I must watch The Apprentice. lol

If any of you guys happen to read this in the mean time, please add any of
your own ideas on the matter.

Thanks!



"Keith" wrote:

I have read through several posts and some are similar to my question, but
not exactly.

I have 2 computers one with Windows XP and the other is a dual boot with
Windows 2000 Pro and 98 SE. I set up a wirless PCI card in the dual boot
computer and the XP machine is hard wired to the router.

I first booted into Windows 2000 and setup the card. Once done, I went to
network neighborhood and I could see the XP machine. I went to the XP machine
and I could see the 2000 Pro system. So, that was a good thing!

After, I rebooted into 98SE. I set up the card the same way and connected to
the network sucessfully. I went to Network Neighborhood, but could not see
the XP machine. I went to the XP machine and could not see the 98SE. So, that
was not a good thing!

Is there something in 98 that I must set that is not necessary to do in
2000? Is it because 98 cannot see NTFS file systems, and that is why 98
cannot see XP? But, if that were the case XP should still be able to see 98.

Thanks!

Ok, so I had a few minuites until The Apprentice starts. I just couldn't take
it and I had to go try at least one thing.

I went to the 98 computer and went to Device Manager. This time I did just
the opposite of last time. I disabled the on-board 3Com Ethernet, eventhough
it wasn't even connected. I was thinking heir might be some conflict between
the two network adapters.

So, now all I have is the NetGear wirless adapter enabled. VOILA!!!!!!!!!!!!
98 sees Xp and XP sees 98. Woooo hoooooo I am posting this reply from the
Windows 98 computer which now had internet access.

I guess in Windows 98 there is some conflict between the two adapters that
does not exist when I boot into Windows 2000.

Thanks guys your help has been priceless!

"Keith" wrote:

Ok, I have discovered something interesting! I have done all things
suggested. Everything was the way it was supposed to be except one thing.
When I typed ipconfig /all in Windows XP the NodeType was unknown. I added
the parameter as specified by Steve. I added NodeType as a DWORD with an
attribute of 1 for broadcast. After I rebooted, I went back to ipconfig and
NodeType was broadcast. But, still no dice.

I went into Device Manager and disabled the NetGear wireless PCI adapter. So
now I was only working with the on-board 3Com Ethernet. I made the RJ-45
connection from the router to the computer and checked Network Neighborhood.
Instantly I was able to see the XP computer. I went to the XP computer and
was instantly able to see the 98 computer.

After, I re-enabled the wirless card and unplugged the RJ-45 connection.
Then, went to Network Neighborhood and saw nothing AGAIN!

I have a few ideas I want to try, but first, I must watch The Apprentice. lol

If any of you guys happen to read this in the mean time, please add any of
your own ideas on the matter.

Thanks!



"Keith" wrote:

I have read through several posts and some are similar to my question, but
not exactly.

I have 2 computers one with Windows XP and the other is a dual boot with
Windows 2000 Pro and 98 SE. I set up a wirless PCI card in the dual boot
computer and the XP machine is hard wired to the router.

I first booted into Windows 2000 and setup the card. Once done, I went to
network neighborhood and I could see the XP machine. I went to the XP machine
and I could see the 2000 Pro system. So, that was a good thing!

After, I rebooted into 98SE. I set up the card the same way and connected to
the network sucessfully. I went to Network Neighborhood, but could not see
the XP machine. I went to the XP machine and could not see the 98SE. So, that
was not a good thing!

Is there something in 98 that I must set that is not necessary to do in
2000? Is it because 98 cannot see NTFS file systems, and that is why 98
cannot see XP? But, if that were the case XP should still be able to see 98.

Thanks!

Ok, so I had a few minuites until The Apprentice starts. I just couldn't take
it and I had to go try at least one thing.

I went to the 98 computer and went to Device Manager. This time I did just
the opposite of last time. I disabled the on-board 3Com Ethernet, eventhough
it wasn't even connected. I was thinking heir might be some conflict between
the two network adapters.

So, now all I have is the NetGear wirless adapter enabled. VOILA!!!!!!!!!!!!
98 sees Xp and XP sees 98. Woooo hoooooo I am posting this reply from the
Windows 98 computer which now had internet access.

I guess in Windows 98 there is some conflict between the two adapters that
does not exist when I boot into Windows 2000.

Thanks guys your help has been priceless!

"Keith" wrote:

Ok, I have discovered something interesting! I have done all things
suggested. Everything was the way it was supposed to be except one thing.
When I typed ipconfig /all in Windows XP the NodeType was unknown. I added
the parameter as specified by Steve. I added NodeType as a DWORD with an
attribute of 1 for broadcast. After I rebooted, I went back to ipconfig and
NodeType was broadcast. But, still no dice.

I went into Device Manager and disabled the NetGear wireless PCI adapter. So
now I was only working with the on-board 3Com Ethernet. I made the RJ-45
connection from the router to the computer and checked Network Neighborhood.
Instantly I was able to see the XP computer. I went to the XP computer and
was instantly able to see the 98 computer.

After, I re-enabled the wirless card and unplugged the RJ-45 connection.
Then, went to Network Neighborhood and saw nothing AGAIN!

I have a few ideas I want to try, but first, I must watch The Apprentice. lol

If any of you guys happen to read this in the mean time, please add any of
your own ideas on the matter.

Thanks!



"Keith" wrote:

I have read through several posts and some are similar to my question, but
not exactly.

I have 2 computers one with Windows XP and the other is a dual boot with
Windows 2000 Pro and 98 SE. I set up a wirless PCI card in the dual boot
computer and the XP machine is hard wired to the router.

I first booted into Windows 2000 and setup the card. Once done, I went to
network neighborhood and I could see the XP machine. I went to the XP machine
and I could see the 2000 Pro system. So, that was a good thing!

After, I rebooted into 98SE. I set up the card the same way and connected to
the network sucessfully. I went to Network Neighborhood, but could not see
the XP machine. I went to the XP machine and could not see the 98SE. So, that
was not a good thing!

Is there something in 98 that I must set that is not necessary to do in
2000? Is it because 98 cannot see NTFS file systems, and that is why 98
cannot see XP? But, if that were the case XP should still be able to see 98.

Thanks!

Thanks for the update! Glad to hear you got it sorted out!

Carey

"Keith" wrote in message
...
Ok, so I had a few minuites until The Apprentice starts. I just couldn't
take
it and I had to go try at least one thing.

I went to the 98 computer and went to Device Manager. This time I did just
the opposite of last time. I disabled the on-board 3Com Ethernet,
eventhough
it wasn't even connected. I was thinking heir might be some conflict
between
the two network adapters.

So, now all I have is the NetGear wirless adapter enabled.
VOILA!!!!!!!!!!!!
98 sees Xp and XP sees 98. Woooo hoooooo I am posting this reply from the
Windows 98 computer which now had internet access.

I guess in Windows 98 there is some conflict between the two adapters that
does not exist when I boot into Windows 2000.

Thanks guys your help has been priceless!

"Keith" wrote:

Ok, I have discovered something interesting! I have done all things
suggested. Everything was the way it was supposed to be except one thing.
When I typed ipconfig /all in Windows XP the NodeType was unknown. I
added
the parameter as specified by Steve. I added NodeType as a DWORD with an
attribute of 1 for broadcast. After I rebooted, I went back to ipconfig
and
NodeType was broadcast. But, still no dice.

I went into Device Manager and disabled the NetGear wireless PCI adapter.
So
now I was only working with the on-board 3Com Ethernet. I made the RJ-45
connection from the router to the computer and checked Network
Neighborhood.
Instantly I was able to see the XP computer. I went to the XP computer
and
was instantly able to see the 98 computer.

After, I re-enabled the wirless card and unplugged the RJ-45 connection.
Then, went to Network Neighborhood and saw nothing AGAIN!

I have a few ideas I want to try, but first, I must watch The Apprentice.
lol

If any of you guys happen to read this in the mean time, please add any
of
your own ideas on the matter.

Thanks!



"Keith" wrote:

I have read through several posts and some are similar to my question,
but
not exactly.

I have 2 computers one with Windows XP and the other is a dual boot
with
Windows 2000 Pro and 98 SE. I set up a wirless PCI card in the dual
boot
computer and the XP machine is hard wired to the router.

I first booted into Windows 2000 and setup the card. Once done, I went
to
network neighborhood and I could see the XP machine. I went to the XP
machine
and I could see the 2000 Pro system. So, that was a good thing!

After, I rebooted into 98SE. I set up the card the same way and
connected to
the network sucessfully. I went to Network Neighborhood, but could not
see
the XP machine. I went to the XP machine and could not see the 98SE.
So, that
was not a good thing!

Is there something in 98 that I must set that is not necessary to do in
2000? Is it because 98 cannot see NTFS file systems, and that is why 98
cannot see XP? But, if that were the case XP should still be able to
see 98.

Thanks!

Thanks for the update! Glad to hear you got it sorted out!

Carey

"Keith" wrote in message
...
Ok, so I had a few minuites until The Apprentice starts. I just couldn't
take
it and I had to go try at least one thing.

I went to the 98 computer and went to Device Manager. This time I did just
the opposite of last time. I disabled the on-board 3Com Ethernet,
eventhough
it wasn't even connected. I was thinking heir might be some conflict
between
the two network adapters.

So, now all I have is the NetGear wirless adapter enabled.
VOILA!!!!!!!!!!!!
98 sees Xp and XP sees 98. Woooo hoooooo I am posting this reply from the
Windows 98 computer which now had internet access.

I guess in Windows 98 there is some conflict between the two adapters that
does not exist when I boot into Windows 2000.

Thanks guys your help has been priceless!

"Keith" wrote:

Ok, I have discovered something interesting! I have done all things
suggested. Everything was the way it was supposed to be except one thing.
When I typed ipconfig /all in Windows XP the NodeType was unknown. I
added
the parameter as specified by Steve. I added NodeType as a DWORD with an
attribute of 1 for broadcast. After I rebooted, I went back to ipconfig
and
NodeType was broadcast. But, still no dice.

I went into Device Manager and disabled the NetGear wireless PCI adapter.
So
now I was only working with the on-board 3Com Ethernet. I made the RJ-45
connection from the router to the computer and checked Network
Neighborhood.
Instantly I was able to see the XP computer. I went to the XP computer
and
was instantly able to see the 98 computer.

After, I re-enabled the wirless card and unplugged the RJ-45 connection.
Then, went to Network Neighborhood and saw nothing AGAIN!

I have a few ideas I want to try, but first, I must watch The Apprentice.
lol

If any of you guys happen to read this in the mean time, please add any
of
your own ideas on the matter.

Thanks!



"Keith" wrote:

I have read through several posts and some are similar to my question,
but
not exactly.

I have 2 computers one with Windows XP and the other is a dual boot
with
Windows 2000 Pro and 98 SE. I set up a wirless PCI card in the dual
boot
computer and the XP machine is hard wired to the router.

I first booted into Windows 2000 and setup the card. Once done, I went
to
network neighborhood and I could see the XP machine. I went to the XP
machine
and I could see the 2000 Pro system. So, that was a good thing!

After, I rebooted into 98SE. I set up the card the same way and
connected to
the network sucessfully. I went to Network Neighborhood, but could not
see
the XP machine. I went to the XP machine and could not see the 98SE.
So, that
was not a good thing!

Is there something in 98 that I must set that is not necessary to do in
2000? Is it because 98 cannot see NTFS file systems, and that is why 98
cannot see XP? But, if that were the case XP should still be able to
see 98.

Thanks!

In article ,
"Keith" wrote:
Ok, I have discovered something interesting! I have done all things
suggested. Everything was the way it was supposed to be except one thing.
When I typed ipconfig /all in Windows XP the NodeType was unknown. I added
the parameter as specified by Steve. I added NodeType as a DWORD with an
attribute of 1 for broadcast. After I rebooted, I went back to ipconfig and
NodeType was broadcast. But, still no dice.

As I mentioned, only a node type of "Point-to-Point" indicates a
problem and requires changing the NodeType registry value. A node
type of "Unknown" is OK, and I wouldn't expect that changing "Unknown"
to "Broadcast" would help.

I went into Device Manager and disabled the NetGear wireless PCI adapter. So
now I was only working with the on-board 3Com Ethernet. I made the RJ-45
connection from the router to the computer and checked Network Neighborhood.
Instantly I was able to see the XP computer. I went to the XP computer and
was instantly able to see the 98 computer.

After, I re-enabled the wirless card and unplugged the RJ-45 connection.
Then, went to Network Neighborhood and saw nothing AGAIN!

It looks to me like the wireless card is defective or is improperly
configured for connecting to your wireless network. Does it associate
with the access point? Does it get an IP address in the right subnet?

I have a few ideas I want to try, but first, I must watch The Apprentice. lol

If any of you guys happen to read this in the mean time, please add any of
your own ideas on the matter.

Thanks!
--
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 ,
"Keith" wrote:
Ok, I have discovered something interesting! I have done all things
suggested. Everything was the way it was supposed to be except one thing.
When I typed ipconfig /all in Windows XP the NodeType was unknown. I added
the parameter as specified by Steve. I added NodeType as a DWORD with an
attribute of 1 for broadcast. After I rebooted, I went back to ipconfig and
NodeType was broadcast. But, still no dice.

As I mentioned, only a node type of "Point-to-Point" indicates a
problem and requires changing the NodeType registry value. A node
type of "Unknown" is OK, and I wouldn't expect that changing "Unknown"
to "Broadcast" would help.

I went into Device Manager and disabled the NetGear wireless PCI adapter. So
now I was only working with the on-board 3Com Ethernet. I made the RJ-45
connection from the router to the computer and checked Network Neighborhood.
Instantly I was able to see the XP computer. I went to the XP computer and
was instantly able to see the 98 computer.

After, I re-enabled the wirless card and unplugged the RJ-45 connection.
Then, went to Network Neighborhood and saw nothing AGAIN!

It looks to me like the wireless card is defective or is improperly
configured for connecting to your wireless network. Does it associate
with the access point? Does it get an IP address in the right subnet?

I have a few ideas I want to try, but first, I must watch The Apprentice. lol

If any of you guys happen to read this in the mean time, please add any of
your own ideas on the matter.

Thanks!
--
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

Thanks Steve your help has been GREATLY appreciated! I don't think it was a
defective card because it scanned and found both my Home wireless network and
my test wireless network. When I told it to connect to the test network, it
did so successfully. Also, as I mentioned, it worked fine when I was in
Windows 2000.

If you see my last post prior to this one, you will see the solution. The
only thing I can figure is a problem in Windows 98 when two network adapters
are installed and enabled. When disabeling one in the Device Manger the other
worked perfectly. When both enabled, problems.

I assume this is something specific to Windows 98 because when I boot into
Windows 2000 with both network adapters enabled, I don't have any problems.

Thanks again!

"Steve Winograd [MVP]" wrote:

In article ,
"Keith" wrote:
Ok, I have discovered something interesting! I have done all things
suggested. Everything was the way it was supposed to be except one thing.
When I typed ipconfig /all in Windows XP the NodeType was unknown. I added
the parameter as specified by Steve. I added NodeType as a DWORD with an
attribute of 1 for broadcast. After I rebooted, I went back to ipconfig and
NodeType was broadcast. But, still no dice.

As I mentioned, only a node type of "Point-to-Point" indicates a
problem and requires changing the NodeType registry value. A node
type of "Unknown" is OK, and I wouldn't expect that changing "Unknown"
to "Broadcast" would help.

I went into Device Manager and disabled the NetGear wireless PCI adapter. So
now I was only working with the on-board 3Com Ethernet. I made the RJ-45
connection from the router to the computer and checked Network Neighborhood.
Instantly I was able to see the XP computer. I went to the XP computer and
was instantly able to see the 98 computer.

After, I re-enabled the wirless card and unplugged the RJ-45 connection.
Then, went to Network Neighborhood and saw nothing AGAIN!

It looks to me like the wireless card is defective or is improperly
configured for connecting to your wireless network. Does it associate
with the access point? Does it get an IP address in the right subnet?

I have a few ideas I want to try, but first, I must watch The Apprentice. lol

If any of you guys happen to read this in the mean time, please add any of
your own ideas on the matter.

Thanks!
--
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