W98 networki enigma

On Mon, 11 Jun 2007 10:03:38 -0700, "Mike Easter"
wrote:

The route print for # 3 [no internet] is:

It all looks to be in order and there is no apparent reason why it
isn't working.

I can't suggest anything apart from maybe try it with a static ip
address, enable dns in the tcp/ip properties and enter your isp's
nameserver addresses in those settings.


Jim.

James Egan wrote:
"Mike Easter"

The route print for # 3 [no internet] is:

It all looks to be in order and there is no apparent reason why it
isn't working.

I don't know how to analyze the route table information, but the two #1
& #3 aren't 'symmetrical' in terms of a differences besides the
different NAT addresses.

If you consider the two to each be a table of 7 rows and 5 columns,
there is a difference between #1 & #3 at row 7 column 4. I have no idea
what that means.

I can't suggest anything apart from maybe try it with a static ip
address, enable dns in the tcp/ip properties and enter your isp's
nameserver addresses in those settings.

Yes, I think I'm going to tinker with those ideas.


--
Mike Easter

James Egan wrote:
"Mike Easter"

The route print for # 3 [no internet] is:

It all looks to be in order and there is no apparent reason why it
isn't working.

I don't know how to analyze the route table information, but the two #1
& #3 aren't 'symmetrical' in terms of a differences besides the
different NAT addresses.

If you consider the two to each be a table of 7 rows and 5 columns,
there is a difference between #1 & #3 at row 7 column 4. I have no idea
what that means.

I can't suggest anything apart from maybe try it with a static ip
address, enable dns in the tcp/ip properties and enter your isp's
nameserver addresses in those settings.

Yes, I think I'm going to tinker with those ideas.


--
Mike Easter

On Mon, 11 Jun 2007 15:50:36 -0700, "Mike Easter"
wrote:

James Egan wrote:
"Mike Easter"

The route print for # 3 [no internet] is:

It all looks to be in order and there is no apparent reason why it
isn't working.

I don't know how to analyze the route table information, but the two #1
& #3 aren't 'symmetrical' in terms of a differences besides the
different NAT addresses.

If you consider the two to each be a table of 7 rows and 5 columns,
there is a difference between #1 & #3 at row 7 column 4. I have no idea
what that means.


I did notice that but it was the machine which is working correctly
that is giving the unexpected route. 255.255.255.255 is a broadcast
route and machine #3 lists the line correctly. I don't know what
causes machine #1 to output that line.


Jim.

On Mon, 11 Jun 2007 15:50:36 -0700, "Mike Easter"
wrote:

James Egan wrote:
"Mike Easter"

The route print for # 3 [no internet] is:

It all looks to be in order and there is no apparent reason why it
isn't working.

I don't know how to analyze the route table information, but the two #1
& #3 aren't 'symmetrical' in terms of a differences besides the
different NAT addresses.

If you consider the two to each be a table of 7 rows and 5 columns,
there is a difference between #1 & #3 at row 7 column 4. I have no idea
what that means.


I did notice that but it was the machine which is working correctly
that is giving the unexpected route. 255.255.255.255 is a broadcast
route and machine #3 lists the line correctly. I don't know what
causes machine #1 to output that line.


Jim.

Mike Easter wrote:
Win98 can't access the internet, neighborhood OK.

OK, I'm back with fundamentally the same problem which I'm completely
convinced is a Win98 configuration or install related problem -- the
hardware and topology are different, but many fundamentals are the same.
I'm doing this on a different #3 computer with different wireless PCI
card.

In the simplest troubleshooting model, we have a two computer network
via an AirLink AR325W router, to which W98se computer #1 is ethernet
hardwired and W98se computer #3 is running a wireless PCI card which has
been changed to an AirLink101 AWLH4130 which runs an Atheros chipset
known as ar5212.

#3 was initially configured wired ethernet integrated mobo LAN, then
'converted' by adding the wireless PCI card. This requires disabling
the wired hardware in the system to do any good at all.

With some interesting work on the linux installs which can also boot on
#3, I now have both Linspire and Ubuntu able to access the internet
using either their wired connectivity or their wireless connectivity.
The goal of this machine is to be rolled into another room where it will
need wireless connectivity only. Currently I'm doing my troubleshooting
with it nearby.

The baffling features of the wireless dysfunction on the W98 #3 boot are
that Win can see quite a bit, but not the internet. Win can see the #1
shares and the printer connected to #1 in the network neighborhood. It
can also see the router's configuration page at 192.168.1.1 - however,
it can't see http one step beyond that to the cable modem's
configuration page at 192.168.100.1 - and it can't see the internet by
name or IP address.

It seems as if the #3 Win isn't getting past the router except for the
shares - maybe as if netbeui was working past the router, but tcp/ip
wasn't - but that tcp/ip worked right up to the router.

In addition, a wireless monitor app installed on #3 shows signal
strength nicely, and shows that #3 is able to get an IP address, which
is also reflected in the router's client list by computer name, IP, and
MAC.

I don't know where #3 is getting its name when it determines it itself.
If I msdos ping localhost, the name which is returned is my name
attached to a 3 level domainname which I am familiar with, but neither
of those names is the computer's name as entered in the network
configuration. My name shows in the system as the registered to. My
name also shows as the logon. I don't know if this name confusion is
important or not, but it is different from the way the #1 computer
performs, which works correctly. The router calls #3 the name which I
gave it in the network configuration section, not my name. In network
neighborhood #3 shows up as the name in the network configuration, not
my name attached to a domainname.

#3 Msdos can ping #1 by its name, but it seems like resolving that is a
little pokey. #3 msdos can ping its own name, which also seems pokey to
resolve.

When I use winpopup to send messages, #1 alerts me that someone is on
the network with my name, but I send the messages with the computers'
names, which works fine both ways, 13 & 31.

#1 msdos can ping #3 by its name, with much faster resolution and
performance.

#3 route print is:

Active Routes:

Network Address Netmask Gateway Address Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.102
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.102 192.168.1.102
1
192.168.1.102 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.1.255 255.255.255.255 192.168.1.102 192.168.1.102
1
224.0.0.0 224.0.0.0 192.168.1.102 192.168.1.102
1
255.255.255.255 255.255.255.255 192.168.1.102 192.168.1.102
1

#1 route print is:

Active Routes:

Network Address Netmask Gateway Address Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.145
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.145 192.168.1.145
1
192.168.1.145 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.1.255 255.255.255.255 192.168.1.145 192.168.1.145
1
224.0.0.0 224.0.0.0 192.168.1.145 192.168.1.145
1
255.255.255.255 255.255.255.255 192.168.1.145 0.0.0.0
1

.... which as before are the same except for the last line's interface.



--
Mike Easter

Mike Easter wrote:
Win98 can't access the internet, neighborhood OK.

OK, I'm back with fundamentally the same problem which I'm completely
convinced is a Win98 configuration or install related problem -- the
hardware and topology are different, but many fundamentals are the same.
I'm doing this on a different #3 computer with different wireless PCI
card.

In the simplest troubleshooting model, we have a two computer network
via an AirLink AR325W router, to which W98se computer #1 is ethernet
hardwired and W98se computer #3 is running a wireless PCI card which has
been changed to an AirLink101 AWLH4130 which runs an Atheros chipset
known as ar5212.

#3 was initially configured wired ethernet integrated mobo LAN, then
'converted' by adding the wireless PCI card. This requires disabling
the wired hardware in the system to do any good at all.

With some interesting work on the linux installs which can also boot on
#3, I now have both Linspire and Ubuntu able to access the internet
using either their wired connectivity or their wireless connectivity.
The goal of this machine is to be rolled into another room where it will
need wireless connectivity only. Currently I'm doing my troubleshooting
with it nearby.

The baffling features of the wireless dysfunction on the W98 #3 boot are
that Win can see quite a bit, but not the internet. Win can see the #1
shares and the printer connected to #1 in the network neighborhood. It
can also see the router's configuration page at 192.168.1.1 - however,
it can't see http one step beyond that to the cable modem's
configuration page at 192.168.100.1 - and it can't see the internet by
name or IP address.

It seems as if the #3 Win isn't getting past the router except for the
shares - maybe as if netbeui was working past the router, but tcp/ip
wasn't - but that tcp/ip worked right up to the router.

In addition, a wireless monitor app installed on #3 shows signal
strength nicely, and shows that #3 is able to get an IP address, which
is also reflected in the router's client list by computer name, IP, and
MAC.

I don't know where #3 is getting its name when it determines it itself.
If I msdos ping localhost, the name which is returned is my name
attached to a 3 level domainname which I am familiar with, but neither
of those names is the computer's name as entered in the network
configuration. My name shows in the system as the registered to. My
name also shows as the logon. I don't know if this name confusion is
important or not, but it is different from the way the #1 computer
performs, which works correctly. The router calls #3 the name which I
gave it in the network configuration section, not my name. In network
neighborhood #3 shows up as the name in the network configuration, not
my name attached to a domainname.

#3 Msdos can ping #1 by its name, but it seems like resolving that is a
little pokey. #3 msdos can ping its own name, which also seems pokey to
resolve.

When I use winpopup to send messages, #1 alerts me that someone is on
the network with my name, but I send the messages with the computers'
names, which works fine both ways, 13 & 31.

#1 msdos can ping #3 by its name, with much faster resolution and
performance.

#3 route print is:

Active Routes:

Network Address Netmask Gateway Address Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.102
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.102 192.168.1.102
1
192.168.1.102 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.1.255 255.255.255.255 192.168.1.102 192.168.1.102
1
224.0.0.0 224.0.0.0 192.168.1.102 192.168.1.102
1
255.255.255.255 255.255.255.255 192.168.1.102 192.168.1.102
1

#1 route print is:

Active Routes:

Network Address Netmask Gateway Address Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.145
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.145 192.168.1.145
1
192.168.1.145 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.1.255 255.255.255.255 192.168.1.145 192.168.1.145
1
224.0.0.0 224.0.0.0 192.168.1.145 192.168.1.145
1
255.255.255.255 255.255.255.255 192.168.1.145 0.0.0.0
1

.... which as before are the same except for the last line's interface.



--
Mike Easter

Mike Easter wrote:
Mike Easter wrote:
Win98 can't access the internet, neighborhood OK.

Updates:

I've removed netbeui as protocol on the affected computer.

I can ping/echo the cablemodem by IP address 192.168.100.1 and I can
ping internet sites [which echo pings] by IP address with the affected
#3.

I don't understand why I can't access the webserver tool on the
cablemodem by IP address http://192.168.100.1 if I can ping it and get a
ping echo -- and I don't understand why I can ping/echo the ipchicken
site by IP, but I can't get http://209.68.27.16

So, now that seems as if the ping goes thru' the wireless & wireless
router & cable modem & internet & echoes back and is handled properly by
the router and wirelessness - but packets don't. Or something.


I misspoke here below:

When I use winpopup to send messages, #1 alerts me that someone is on
the network with my name, but I send the messages with the computers'
names, which works fine both ways, 13 & 31.

I get that alert from #3, the affected, not #1 the unaffected.

Also, when winpopup gets a message from #3, it thinks its name is my
name, not the computer's name. But I can send to the computer's name
OK.



--
Mike Easter

Mike Easter wrote:
Mike Easter wrote:
Win98 can't access the internet, neighborhood OK.

Updates:

I've removed netbeui as protocol on the affected computer.

I can ping/echo the cablemodem by IP address 192.168.100.1 and I can
ping internet sites [which echo pings] by IP address with the affected
#3.

I don't understand why I can't access the webserver tool on the
cablemodem by IP address http://192.168.100.1 if I can ping it and get a
ping echo -- and I don't understand why I can ping/echo the ipchicken
site by IP, but I can't get http://209.68.27.16

So, now that seems as if the ping goes thru' the wireless & wireless
router & cable modem & internet & echoes back and is handled properly by
the router and wirelessness - but packets don't. Or something.


I misspoke here below:

When I use winpopup to send messages, #1 alerts me that someone is on
the network with my name, but I send the messages with the computers'
names, which works fine both ways, 13 & 31.

I get that alert from #3, the affected, not #1 the unaffected.

Also, when winpopup gets a message from #3, it thinks its name is my
name, not the computer's name. But I can send to the computer's name
OK.



--
Mike Easter

Mike Easter wrote:

I don't understand why I can't access the webserver tool on the
cablemodem by IP address http://192.168.100.1 if I can ping it and
get a ping echo -- and I don't understand why I can ping/echo the
ipchicken site by IP, but I can't get http://209.68.27.16


I fixed it! I fixed it!

I figgered something was wrong with the tcp/ip stack if I could ping but
I couldn't do anything else, so I started looking for repair utilities.
I had already tried removing all of the tcp/ip protocols from the
network config and then reinstalling them, but that didn't do any good.
Some suggested registry repairs.

After searching and searching I found a site^1 which description sounded
like my problem:

sNip
This program is designed to fix a situation where all of the following
are true:
the computer can get a valid IP address
the computer can ping DNS numbers
the computer can be pinged from other computers
all other network services do not work (Telnet, ftp and Web browsers)
/sNip

That all sounded pretty good to me and it sounded like a good way to
repair the registry which had been mentioned somewhere else, so I
performed that operation with the site's win2fix.exe.

But it didn't work. That was very disappointing, because it sounded
like the symptoms were right on the money. As I re-read the school's
website which app was no longer supported because the developer had
graduated or left, the site said that they believed that the app there
may no longer be the best solution and referred me to a different site^2
with a similarly functioning tool.

So, I doggedly went over there and got that one, winsockfix.exe. Altho'
it was designed to fix problems caused by spyware, which I had never had
any trouble with, I still tho't it was a good idea. I made some backups
this time and ran the app which finished in an instant, almost
disappointingly fast.

Then after the reboot... lo! and behold!

Everything was working. Ta da!!

Thanks for everyone's help.


^1 http://www.bu.edu/pcsc/internetaccess/winsock2fix.html
^2 http://www.tacktech.com/display.cfm?ttid=257

--
Mike Easter