98SE refuses XP home connection

Familiar Story? XP Home boy meets 98SE. 98SE likes XP_Home a lot, lets him
shares her files, gives him her number so he pings her constantly and even
shares her files. But the XP swine gives her the cold shoulder - doesn't
reply to her pings and blocks her out. What's a nice girl to do???

Although this seems a fairly frequent problem I have spent many hours
reviewing previous postings! challenge - spot what I missed!.

Firstly HP home box:
# Logon and password same as on 98
# Guest account enables with no password
# firewall if OFF (not intended as a permanent solution)
# YES - Client for MS networks - Name Service provider is W Locator
#Yes- file and printer sharing for MS networks
#YES - TCP/IP
The XP box CAN see the 98 shares and can happily read and write to them.
The XP box CAN ping the 98 box.
The network wizard has been run.

Old Faithfull 98:
# Yes it starts with a logon - same name and password as XP box
# Network wizard disk was run. - so workgroup name is the same as XP box.
# Network neighbourhood starts blank - not even local name shows -
eventually wait long enough and you might be lucky enough to get an 'unable
to browse network - network is unaccessible]
# XP box ping just times out
# start/run \\XPname eventually times out with 'network name cannot be found'
#Network properties include:
- client for MS networks
- TCP/IP (enable netbios over TCPIP selected and greyed out)
IP address selected automatically
Bindings - client for ms networks & file and printer sharing
# YES - file and printer sharing - give access to my files ...
primary network logon - Client for MS netwqorks
Identifiation - workgroup MSHOME (sanme as XP)
Acces Control - share-level

Internet gateway is in the systray - right click gives real time status of
the XP box connection - so they ARE talking!!!
- An web page however will time out on IE.

Pleeeese help.

Chris.

You are welcome to email me if you would like to work on this problem
one-on-one.

(E-Mail Removed)


"ChrisWhyNotDitchXP" <(E-Mail Removed)> wrote in
message news:498AC2D2-9F0C-4CAE-9A3E-(E-Mail Removed)...
> Familiar Story? XP Home boy meets 98SE. 98SE likes XP_Home a lot, lets
> him
> shares her files, gives him her number so he pings her constantly and even
> shares her files. But the XP swine gives her the cold shoulder - doesn't
> reply to her pings and blocks her out. What's a nice girl to do???
>
> Although this seems a fairly frequent problem I have spent many hours
> reviewing previous postings! challenge - spot what I missed!.
>
> Firstly HP home box:
> # Logon and password same as on 98
> # Guest account enables with no password
> # firewall if OFF (not intended as a permanent solution)
> # YES - Client for MS networks - Name Service provider is W Locator
> #Yes- file and printer sharing for MS networks
> #YES - TCP/IP
> The XP box CAN see the 98 shares and can happily read and write to them.
> The XP box CAN ping the 98 box.
> The network wizard has been run.
>
> Old Faithfull 98:
> # Yes it starts with a logon - same name and password as XP box
> # Network wizard disk was run. - so workgroup name is the same as XP
> box.
> # Network neighbourhood starts blank - not even local name shows -
> eventually wait long enough and you might be lucky enough to get an
> 'unable
> to browse network - network is unaccessible]
> # XP box ping just times out
> # start/run \\XPname eventually times out with 'network name cannot be
> found'
> #Network properties include:
> - client for MS networks
> - TCP/IP (enable netbios over TCPIP selected and greyed out)
> IP address selected automatically
> Bindings - client for ms networks & file and printer sharing
> # YES - file and printer sharing - give access to my files ...
> primary network logon - Client for MS netwqorks
> Identifiation - workgroup MSHOME (sanme as XP)
> Acces Control - share-level
>
> Internet gateway is in the systray - right click gives real time status of
> the XP box connection - so they ARE talking!!!
> - An web page however will time out on IE.
>
> Pleeeese help.
>
> Chris.

In article <498AC2D2-9F0C-4CAE-9A3E-(E-Mail Removed)>,
ChrisWhyNotDitchXP <(E-Mail Removed)>
wrote:
>Familiar Story? XP Home boy meets 98SE. 98SE likes XP_Home a lot, lets him
>shares her files, gives him her number so he pings her constantly and even
>shares her files. But the XP swine gives her the cold shoulder - doesn't
>reply to her pings and blocks her out. What's a nice girl to do???
>
>Although this seems a fairly frequent problem I have spent many hours
>reviewing previous postings! challenge - spot what I missed!.
>
>Firstly HP home box:
># Logon and password same as on 98
># Guest account enables with no password
># firewall if OFF (not intended as a permanent solution)
># YES - Client for MS networks - Name Service provider is W Locator
>#Yes- file and printer sharing for MS networks
>#YES - TCP/IP
>The XP box CAN see the 98 shares and can happily read and write to them.
>The XP box CAN ping the 98 box.
>The network wizard has been run.
>
>Old Faithfull 98:
># Yes it starts with a logon - same name and password as XP box
># Network wizard disk was run. - so workgroup name is the same as XP box.
># Network neighbourhood starts blank - not even local name shows -
>eventually wait long enough and you might be lucky enough to get an 'unable
>to browse network - network is unaccessible]
># XP box ping just times out
># start/run \\XPname eventually times out with 'network name cannot be found'
>#Network properties include:
>- client for MS networks
>- TCP/IP (enable netbios over TCPIP selected and greyed out)
> IP address selected automatically
> Bindings - client for ms networks & file and printer sharing
># YES - file and printer sharing - give access to my files ...
>primary network logon - Client for MS netwqorks
>Identifiation - workgroup MSHOME (sanme as XP)
>Acces Control - share-level
>
>Internet gateway is in the systray - right click gives real time status of
>the XP box connection - so they ARE talking!!!
>- An web page however will time out on IE.
>
>Pleeeese help.
>
>Chris.

Pinging a computer by IP address uses only the TCP/IP protocol. If
Win98SE can't ping XP's IP address, the most likely problems are that:

1. The computers have IP addresses in different subnets. Since 98SE
shows XP as the Internet gateway, this probably isn't the case.

2. A firewall on the XP computer is blocking access. It could be XP's
built-in firewall (Internet Connection Firewall on original and SP1,
Windows Firewall on SP2) or a third-part firewall program (Norton,
McAfee, ZoneAlarm, PCCillin, Sygate, EZ Armor, etc). Note that some
antivirus programs have an associated firewall component that might
not be obvious. It's possible that a firewall program was installed
on XP and was then partially or improperly un-installed so that it's
causing access problems.

Solve the ping-by-IP-Address problem before worrying about
file/printer sharing.

These settings have nothing to do with pinging by IP address, but
they're relevant to file/printer sharing between 98SE and XP Home:
Client for Microsoft Networks, File and Printer Sharing, NetBIOS over
TCP/IP, bindings, access control.

These settings have no effect on file/printer sharing between 98SE and
XP Home: workgroup name, primary network logon, matching logon name
and password on both computers.

Use only one protocol on the network. Since TCP/IP can do both
Internet access and file/printer sharing, remove IPX/SPX and NetBEUI
from both computers if they're present.

If XP Home is acting as an Internet Connection Sharing host for 98SE,
run these tests:

1. On XP Home, right click the local area network connection and click
Status | Support | Details. It should show:

IP Address: 192.168.0.1
Subnet Mask: 255.255.255.0
Default Gateway: none
DNS Server = none

2. On 98SE, right click the local area network connection and click
Status | Support | Details. It should show:

IP Address: 192.168.0.x (1<x<255)
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
DNS Server = 192.168.0.1

3. If #1 and #2 are right, open a command prompt window on 98SE and
enter these lines. Each one should get four replies:

ping 192.168.0.1
ping 216.239.39.99
ping google.com

4. If #1-#3 are right, enter these addresses in Internet Explorer.
They should both take you to the Google web page:

http://216.239.39.99
http://google.com
--
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

Steve,

Many Thanks for your help. I was hoping the ping would be a giveaway - and
so it proved. The DELL comes bundled with McAfee which I thought was an
antivirus program - but nowadays comes with a vicious firewall to reject all
potential suitors and keep XP for itself. Adding the 98 box IP address to
McAfee 'trusted' computers solved the problem only after the 98 had re-booted
- and file sharing is now possible. Whoopeeeee! McAfee even had a log of
the long ( and sorry) history of all attempts to connect - shame it didn't
pop-up a clue (maybe XP firewall blocked the MacAfee firewall pop-up? ... ;-)
).

I can't help feeling the XP network troubleshooting guide and also
miscrosoft on-line support are missing a trick here. Off the shelf DELL
computers are quite common round these parts and McAfee must be pretty
widespread - if blocking ALL network traffic is the default setting there
must be more than one confused punter out there ... Several days ago I went
laboriously through the the Microsoft Windows XP Technical Article "
Troubleshooting File and Printer Sharing in Microsoft Windows XP". Within
the section 'common problems with File and printer sharing' it suggests that
if run:\\ipaddress doesn't work then Windows firewall might be to blame but
doesn't suggest there might be another firewall around.

So should I be thinking of changing my logon-name? ... well give me a couple
more weeks to think about it ...

Chris.

"Steve Winograd [MVP]" wrote:

> In article <498AC2D2-9F0C-4CAE-9A3E-(E-Mail Removed)>,
> ChrisWhyNotDitchXP <(E-Mail Removed)>
> wrote:
> >Familiar Story? XP Home boy meets 98SE. 98SE likes XP_Home a lot, lets him
> >shares her files, gives him her number so he pings her constantly and even
> >shares her files. But the XP swine gives her the cold shoulder - doesn't
> >reply to her pings and blocks her out. What's a nice girl to do???
> >
> >Although this seems a fairly frequent problem I have spent many hours
> >reviewing previous postings! challenge - spot what I missed!.
> >
> >Firstly HP home box:
> ># Logon and password same as on 98
> ># Guest account enables with no password
> ># firewall if OFF (not intended as a permanent solution)
> ># YES - Client for MS networks - Name Service provider is W Locator
> >#Yes- file and printer sharing for MS networks
> >#YES - TCP/IP
> >The XP box CAN see the 98 shares and can happily read and write to them.
> >The XP box CAN ping the 98 box.
> >The network wizard has been run.
> >
> >Old Faithfull 98:
> ># Yes it starts with a logon - same name and password as XP box
> ># Network wizard disk was run. - so workgroup name is the same as XP box.
> ># Network neighbourhood starts blank - not even local name shows -
> >eventually wait long enough and you might be lucky enough to get an 'unable
> >to browse network - network is unaccessible]
> ># XP box ping just times out
> ># start/run \\XPname eventually times out with 'network name cannot be found'
> >#Network properties include:
> >- client for MS networks
> >- TCP/IP (enable netbios over TCPIP selected and greyed out)
> > IP address selected automatically
> > Bindings - client for ms networks & file and printer sharing
> ># YES - file and printer sharing - give access to my files ...
> >primary network logon - Client for MS netwqorks
> >Identifiation - workgroup MSHOME (sanme as XP)
> >Acces Control - share-level
> >
> >Internet gateway is in the systray - right click gives real time status of
> >the XP box connection - so they ARE talking!!!
> >- An web page however will time out on IE.
> >
> >Pleeeese help.
> >
> >Chris.
>
> Pinging a computer by IP address uses only the TCP/IP protocol. If
> Win98SE can't ping XP's IP address, the most likely problems are that:
>
> 1. The computers have IP addresses in different subnets. Since 98SE
> shows XP as the Internet gateway, this probably isn't the case.
>
> 2. A firewall on the XP computer is blocking access. It could be XP's
> built-in firewall (Internet Connection Firewall on original and SP1,
> Windows Firewall on SP2) or a third-part firewall program (Norton,
> McAfee, ZoneAlarm, PCCillin, Sygate, EZ Armor, etc). Note that some
> antivirus programs have an associated firewall component that might
> not be obvious. It's possible that a firewall program was installed
> on XP and was then partially or improperly un-installed so that it's
> causing access problems.
>
> Solve the ping-by-IP-Address problem before worrying about
> file/printer sharing.
>
> These settings have nothing to do with pinging by IP address, but
> they're relevant to file/printer sharing between 98SE and XP Home:
> Client for Microsoft Networks, File and Printer Sharing, NetBIOS over
> TCP/IP, bindings, access control.
>
> These settings have no effect on file/printer sharing between 98SE and
> XP Home: workgroup name, primary network logon, matching logon name
> and password on both computers.
>
> Use only one protocol on the network. Since TCP/IP can do both
> Internet access and file/printer sharing, remove IPX/SPX and NetBEUI
> from both computers if they're present.
>
> If XP Home is acting as an Internet Connection Sharing host for 98SE,
> run these tests:
>
> 1. On XP Home, right click the local area network connection and click
> Status | Support | Details. It should show:
>
> IP Address: 192.168.0.1
> Subnet Mask: 255.255.255.0
> Default Gateway: none
> DNS Server = none
>
> 2. On 98SE, right click the local area network connection and click
> Status | Support | Details. It should show:
>
> IP Address: 192.168.0.x (1<x<255)
> Subnet Mask: 255.255.255.0
> Default Gateway: 192.168.0.1
> DNS Server = 192.168.0.1
>
> 3. If #1 and #2 are right, open a command prompt window on 98SE and
> enter these lines. Each one should get four replies:
>
> ping 192.168.0.1
> ping 216.239.39.99
> ping google.com
>
> 4. If #1-#3 are right, enter these addresses in Internet Explorer.
> They should both take you to the Google web page:
>
> http://216.239.39.99
> http://google.com
> --
> 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
>

Not sure why you would prefer one-on-one. Surely the main benefit of the
usergroup ethos is to share information openly for the benefit of all the
users .... ???

Chris.

"Carey Holzman" wrote:

> You are welcome to email me if you would like to work on this problem
> one-on-one.
>
> (E-Mail Removed)
>
>
> "ChrisWhyNotDitchXP" <(E-Mail Removed)> wrote in
> message news:498AC2D2-9F0C-4CAE-9A3E-(E-Mail Removed)...
> > Familiar Story? XP Home boy meets 98SE. 98SE likes XP_Home a lot, lets
> > him
> > shares her files, gives him her number so he pings her constantly and even
> > shares her files. But the XP swine gives her the cold shoulder - doesn't
> > reply to her pings and blocks her out. What's a nice girl to do???
> >
> > Although this seems a fairly frequent problem I have spent many hours
> > reviewing previous postings! challenge - spot what I missed!.
> >
> > Firstly HP home box:
> > # Logon and password same as on 98
> > # Guest account enables with no password
> > # firewall if OFF (not intended as a permanent solution)
> > # YES - Client for MS networks - Name Service provider is W Locator
> > #Yes- file and printer sharing for MS networks
> > #YES - TCP/IP
> > The XP box CAN see the 98 shares and can happily read and write to them.
> > The XP box CAN ping the 98 box.
> > The network wizard has been run.
> >
> > Old Faithfull 98:
> > # Yes it starts with a logon - same name and password as XP box
> > # Network wizard disk was run. - so workgroup name is the same as XP
> > box.
> > # Network neighbourhood starts blank - not even local name shows -
> > eventually wait long enough and you might be lucky enough to get an
> > 'unable
> > to browse network - network is unaccessible]
> > # XP box ping just times out
> > # start/run \\XPname eventually times out with 'network name cannot be
> > found'
> > #Network properties include:
> > - client for MS networks
> > - TCP/IP (enable netbios over TCPIP selected and greyed out)
> > IP address selected automatically
> > Bindings - client for ms networks & file and printer sharing
> > # YES - file and printer sharing - give access to my files ...
> > primary network logon - Client for MS netwqorks
> > Identifiation - workgroup MSHOME (sanme as XP)
> > Acces Control - share-level
> >
> > Internet gateway is in the systray - right click gives real time status of
> > the XP box connection - so they ARE talking!!!
> > - An web page however will time out on IE.
> >
> > Pleeeese help.
> >
> > Chris.
>
>
>

In article <27A1CD49-60B0-42AC-B7D7-(E-Mail Removed)>,
ChrisWhyNotDitchXP <(E-Mail Removed)>
wrote:
>> >Familiar Story? XP Home boy meets 98SE. 98SE likes XP_Home a lot, lets him
>> >shares her files, gives him her number so he pings her constantly and even
>> >shares her files. But the XP swine gives her the cold shoulder - doesn't
>> >reply to her pings and blocks her out. What's a nice girl to do???
>> >
>> >Although this seems a fairly frequent problem I have spent many hours
>> >reviewing previous postings! challenge - spot what I missed!.
>> >
>> >Firstly HP home box:
>> ># Logon and password same as on 98
>> ># Guest account enables with no password
>> ># firewall if OFF (not intended as a permanent solution)
>> ># YES - Client for MS networks - Name Service provider is W Locator
>> >#Yes- file and printer sharing for MS networks
>> >#YES - TCP/IP
>> >The XP box CAN see the 98 shares and can happily read and write to them.
>> >The XP box CAN ping the 98 box.
>> >The network wizard has been run.
>> >
>> >Old Faithfull 98:
>> ># Yes it starts with a logon - same name and password as XP box
>> ># Network wizard disk was run. - so workgroup name is the same as XP box.
>> ># Network neighbourhood starts blank - not even local name shows -
>> >eventually wait long enough and you might be lucky enough to get an 'unable
>> >to browse network - network is unaccessible]
>> ># XP box ping just times out
>> ># start/run \\XPname eventually times out with 'network name cannot be found'
>> >#Network properties include:
>> >- client for MS networks
>> >- TCP/IP (enable netbios over TCPIP selected and greyed out)
>> > IP address selected automatically
>> > Bindings - client for ms networks & file and printer sharing
>> ># YES - file and printer sharing - give access to my files ...
>> >primary network logon - Client for MS netwqorks
>> >Identifiation - workgroup MSHOME (sanme as XP)
>> >Acces Control - share-level
>> >
>> >Internet gateway is in the systray - right click gives real time status of
>> >the XP box connection - so they ARE talking!!!
>> >- An web page however will time out on IE.
>> >
>> >Pleeeese help.
>> >
>> >Chris.
>>
>> Pinging a computer by IP address uses only the TCP/IP protocol. If
>> Win98SE can't ping XP's IP address, the most likely problems are that:
>>
>> 1. The computers have IP addresses in different subnets. Since 98SE
>> shows XP as the Internet gateway, this probably isn't the case.
>>
>> 2. A firewall on the XP computer is blocking access. It could be XP's
>> built-in firewall (Internet Connection Firewall on original and SP1,
>> Windows Firewall on SP2) or a third-part firewall program (Norton,
>> McAfee, ZoneAlarm, PCCillin, Sygate, EZ Armor, etc). Note that some
>> antivirus programs have an associated firewall component that might
>> not be obvious. It's possible that a firewall program was installed
>> on XP and was then partially or improperly un-installed so that it's
>> causing access problems.
>
>Steve,
>
>Many Thanks for your help. I was hoping the ping would be a giveaway - and
>so it proved. The DELL comes bundled with McAfee which I thought was an
>antivirus program - but nowadays comes with a vicious firewall to reject all
>potential suitors and keep XP for itself. Adding the 98 box IP address to
>McAfee 'trusted' computers solved the problem only after the 98 had re-booted
>- and file sharing is now possible. Whoopeeeee! McAfee even had a log of
>the long ( and sorry) history of all attempts to connect - shame it didn't
>pop-up a clue (maybe XP firewall blocked the MacAfee firewall pop-up? ... ;-)
> ).
>
>I can't help feeling the XP network troubleshooting guide and also
>miscrosoft on-line support are missing a trick here. Off the shelf DELL
>computers are quite common round these parts and McAfee must be pretty
>widespread - if blocking ALL network traffic is the default setting there
>must be more than one confused punter out there ... Several days ago I went
>laboriously through the the Microsoft Windows XP Technical Article "
>Troubleshooting File and Printer Sharing in Microsoft Windows XP". Within
>the section 'common problems with File and printer sharing' it suggests that
>if run:\\ipaddress doesn't work then Windows firewall might be to blame but
>doesn't suggest there might be another firewall around.
>
>So should I be thinking of changing my logon-name? ... well give me a couple
>more weeks to think about it ...

You're welcome, Chris. I'm glad that my suggestions helped you solve
the problem. Thanks for reporting the result.

I suspect that McAfee pays Dell to install its products on new
computers. I personally dislike McAfee products (especially the
Security Center) and won't run them on my computers or recommend them
to my clients. There's probably a setting in the McAfee firewall that
makes alerts appear on the screen, but a computer that's connected
directly to the Internet would get so many alerts (from probes by
Internet hackers) that it makes sense to turn off visible alerts by
default.

Microsoft and Dell would both be doing their users a favor if they
mentioned firewall programs early in their network troubleshooting
information.
>
>Chris.


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