Sign in with
Sign up | Sign in
Your question

win98se-win2kpro-winxp home lan

Last response: in Windows XP
Share
Anonymous
April 16, 2005 1:13:33 AM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

There has to be a FAQ fot this published somewhere.

in win2K, I can see the win98SE machine an the win2K machine (My
Network) and can read/write data to it.

on the win98SE, network neighborhood, I get "unable to browse the
network" and cannot read or write to either other machine

on the winxp machine, I get nothing either.

all 3 machine can hit the internet nicely via the router, all 3 have
different IP addresses, are on the same workgroup and have mathcing
login names/passwords.

I cannot even add the explicit IP as a network place, e.g. in the
form of \\192.168.2.x\

help.....

- chagin1 @ yahoo . com
Anonymous
April 16, 2005 3:24:42 PM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

"jankin" <chagin_one@yahoo.com> wrote in message
news:MPG.1cc9f8fb7bc9b21989720@news-server.nc.rr.com...
> There has to be a FAQ fot this published somewhere.
>
> in win2K, I can see the win98SE machine an the win2K machine (My
> Network) and can read/write data to it.
>
> on the win98SE, network neighborhood, I get "unable to browse the
> network" and cannot read or write to either other machine
>
> on the winxp machine, I get nothing either.
>
> all 3 machine can hit the internet nicely via the router, all 3 have
> different IP addresses, are on the same workgroup and have mathcing
> login names/passwords.
>
> I cannot even add the explicit IP as a network place, e.g. in the
> form of \\192.168.2.x\
>
> help.....
>
> - chagin1 @ yahoo . com
>
>

While testing, do this:
- Give each machine a fixed IP address, e.g.
192.168.2.1, 192.168.2.2, 192.168.2.3
- Turn off all firewalls (this is essential!)
- Start your tests by pinging each PC from every other PC.

Repost if still unable to resolve the issue.
Anonymous
April 16, 2005 9:37:52 PM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

In article <uGNpSMiQFHA.2680@TK2MSFTNGP09.phx.gbl>, I.can@fly.com
says...
....
> While testing, do this:
> - Give each machine a fixed IP address, e.g.
> 192.168.2.1, 192.168.2.2, 192.168.2.3
> - Turn off all firewalls (this is essential!)
> - Start your tests by pinging each PC from every other PC.
>
> Repost if still unable to resolve the issue.

details:

win2K ip: 192.168.2.3, FW is ZA (free). Can ping other 2 machines w/
or w/o any/all firewalls running.
winxp ip: 192.168.2.12, FW is native XP. Can ping other 2 machines.
Can ping other 2 machines w/ or w/o any/all firewalls running.

win98se ip: 192.168.2.4, FW is ZA (free). Attempts to run ping
results in error "ping cannot run in DOS mode" - which is the first
time I've ever seen that....

Now with getting the various gateways and DNS right (all set to
192.168.2.1 which is the router, and all machines assigned to
"workgroup"), I look in network neighborhood (and equivalents) and
find:

the XP machine can see the 98SE machine and itself, but not the win2K
machine, and can access files on the 98 machine;

the win2K machine can see the 98se machine and itself but not the XP
machine, and can acccess files on the 98 machine; attempts to
specifically add by IP the XP machine results in a username/password
demand, which is rejected despite having correct entries;

the 98se machine can see the XP machine and itself, but not the win2K
machine. Attempts to connect with the XP machine results in a demand
for a password for IPC$, despite having equal accounts on all 3
machines (username & password).

Protocols running:

win2K: Client for microsoft networks, file&print sharing, netbeui,
tcpip.

winXP: Client for microsoft networks, file&print sharing, NWLink
IPX/SPX/NetBIOS, TCPIP v6, TCPIP

win98SE: Client for microsoft networks, family logon, file&print
sharing, netbeui, tcpip.

Which comes down to 2 problems: why can't the win2K machine be seen?
Why is the win98se machine barfing with ping?

- elmar
Related resources
Anonymous
April 17, 2005 2:48:52 PM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

"jankin" <chagin_one@yahoo.com> wrote in message
news:MPG.1ccb17da47be951b989721@news-server.nc.rr.com...
> In article <uGNpSMiQFHA.2680@TK2MSFTNGP09.phx.gbl>, I.can@fly.com
> says...
> ...
> > While testing, do this:
> > - Give each machine a fixed IP address, e.g.
> > 192.168.2.1, 192.168.2.2, 192.168.2.3
> > - Turn off all firewalls (this is essential!)
> > - Start your tests by pinging each PC from every other PC.
> >
> > Repost if still unable to resolve the issue.
>
> details:
>
> win2K ip: 192.168.2.3, FW is ZA (free). Can ping other 2 machines w/
> or w/o any/all firewalls running.
> winxp ip: 192.168.2.12, FW is native XP. Can ping other 2 machines.
> Can ping other 2 machines w/ or w/o any/all firewalls running.
>
> win98se ip: 192.168.2.4, FW is ZA (free). Attempts to run ping
> results in error "ping cannot run in DOS mode" - which is the first
> time I've ever seen that....
>
> Now with getting the various gateways and DNS right (all set to
> 192.168.2.1 which is the router, and all machines assigned to
> "workgroup"), I look in network neighborhood (and equivalents) and
> find:
>
> the XP machine can see the 98SE machine and itself, but not the win2K
> machine, and can access files on the 98 machine;
>
> the win2K machine can see the 98se machine and itself but not the XP
> machine, and can acccess files on the 98 machine; attempts to
> specifically add by IP the XP machine results in a username/password
> demand, which is rejected despite having correct entries;
>
> the 98se machine can see the XP machine and itself, but not the win2K
> machine. Attempts to connect with the XP machine results in a demand
> for a password for IPC$, despite having equal accounts on all 3
> machines (username & password).
>
> Protocols running:
>
> win2K: Client for microsoft networks, file&print sharing, netbeui,
> tcpip.
>
> winXP: Client for microsoft networks, file&print sharing, NWLink
> IPX/SPX/NetBIOS, TCPIP v6, TCPIP
>
> win98SE: Client for microsoft networks, family logon, file&print
> sharing, netbeui, tcpip.
>
> Which comes down to 2 problems: why can't the win2K machine be seen?
> Why is the win98se machine barfing with ping?
>
> - elmar

Here are a few suggestions:
- It is not sufficient to have identical accounts/passwords on each
PC. You must actually use these accounts/passwords when logging on.
- "Network neighbourhood" is not a good tool to debug things.
The following commands, when executed from a Command Prompt,
net use x: \\192.168.2.12\SomeShare, or
net use x: \\WinXP-PC\SomeShare
tell you much more about what's going on. Note that the first
command won't work on the Win98 PC.
- ZoneAlarm is notorious for blocking packets even when disabled.
Uninstall it for your tests, then re-install it later on. Cut your
ISP link during your tests to keep out hackers.
- I'm posting this reply in a Win2000 newsgroup. Someone in
a Win98 newsgroup should be able to tell you why ping.exe
does not work on your Win98 PC.
Anonymous
April 17, 2005 8:25:51 PM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

In article <#7ck7cuQFHA.3140@tk2msftngp13.phx.gbl>, I.can@fly.com
says...
>
> "jankin" <chagin_one@yahoo.com> wrote in message
> news:MPG.1ccb17da47be951b989721@news-server.nc.rr.com...
> > In article <uGNpSMiQFHA.2680@TK2MSFTNGP09.phx.gbl>, I.can@fly.com
> > says...
....
> > > - Start your tests by pinging each PC from every other PC.
....

well, dang - now it gets wierd again.

I figured out the win98 problem - a confusion between msdos mode and
msdos prompt; ping works in the prompt, but not the mode.

Now it gets wierd: the win98 machine can ping both the other
machines. The win2K and the winxp machine can ping each other, but
NEITHER can ping the win98 machine.....urg, I think I hate
windows.....

- elmar
Anonymous
April 17, 2005 9:07:25 PM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

In article <MPG.1ccc588e493170d2989726@news-server.nc.rr.com>,
chagin_one@yahoo.com says...
> In article <#7ck7cuQFHA.3140@tk2msftngp13.phx.gbl>, I.can@fly.com
> says...
> >
> > "jankin" <chagin_one@yahoo.com> wrote in message
> > news:MPG.1ccb17da47be951b989721@news-server.nc.rr.com...
> > > In article <uGNpSMiQFHA.2680@TK2MSFTNGP09.phx.gbl>, I.can@fly.com
> > > says...
> ...
> > > > - Start your tests by pinging each PC from every other PC.
> ...
>
> well, dang - now it gets wierd again.
>
> I figured out the win98 problem - a confusion between msdos mode and
> msdos prompt; ping works in the prompt, but not the mode.
>
> Now it gets wierd: the win98 machine can ping both the other
> machines. The win2K and the winxp machine can ping each other, but
> NEITHER can ping the win98 machine.....urg, I think I hate
> windows.....
>
> - elmar
>
>
Let me add the ipconfig /all for the 3 machines...

Windows 2000 IP Configuration (no modem, just a NIC)

Host Name . . . . . . . . . . . . : SHINOBI
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : ASUSTeK/Broadcom 440x
10/100 Integrated Controller
Physical Address. . . . . . . . . : 00-E0-18-B1-19-C4
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Primary WINS Server . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Disabled


Windows 98 IP Configuration (note, this has a disconnected modem
installed)

Host Name . . . . . . . . . : athlon
DNS Servers . . . . . . . . : 192.168.2.1
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : Yes

0 Ethernet adapter :

Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-00
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

1 Ethernet adapter :

Description . . . . . . . . : SMC EZ Card 10/100 (SMC1244TX)
Physical Address. . . . . . : 00-50-BF-74-40-27
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 192.168.2.4
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.2.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :


Windows IP Configuration (XP machine, with a wireless and a modem as
well as a NIC)

Host Name . . . . . . . . . . . . : Flappy
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/Wireless
2200BG Network Connection
Physical Address. . . . . . . . . : 00-0E-35-CB-F4-B5

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT
Mobile Connection
Physical Address. . . . . . . . . : 00-11-25-13-EF-21
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.12
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::211:25ff:fe13:ef21%
5
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-
Interface
Physical Address. . . . . . . . . : 00-00-51-3A-E7-2C-51-23
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . :
3ffe:831f:4004:1950:0:513a:e72c:5123
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%6
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : C0-A8-02-0C
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.2.12%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
NetBIOS over Tcpip. . . . . . . . : Disabled

One final piece of data - I CAN connect the XP machine to a share on
the 2K machine and read/write to it, but the XP machine tells me that
the win98 machine is not accessible (you may not have permission to
use this network resource). OTOH, the win2K machine can see,
read/write files to the 98 machine fine.

grrrrr.
Anonymous
April 18, 2005 12:26:12 PM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

"jankin" <chagin_one@yahoo.com> wrote in message
news:MPG.1ccc624dcb8ba16e989727@news-server.nc.rr.com...
> In article <MPG.1ccc588e493170d2989726@news-server.nc.rr.com>,
> chagin_one@yahoo.com says...
> > In article <#7ck7cuQFHA.3140@tk2msftngp13.phx.gbl>, I.can@fly.com
> > says...
> > >
> > > "jankin" <chagin_one@yahoo.com> wrote in message
> > > news:MPG.1ccb17da47be951b989721@news-server.nc.rr.com...
> > > > In article <uGNpSMiQFHA.2680@TK2MSFTNGP09.phx.gbl>, I.can@fly.com
> > > > says...
> > ...
> > > > > - Start your tests by pinging each PC from every other PC.
> > ...
> >
> > well, dang - now it gets wierd again.
> >
> > I figured out the win98 problem - a confusion between msdos mode and
> > msdos prompt; ping works in the prompt, but not the mode.
> >
> > Now it gets wierd: the win98 machine can ping both the other
> > machines. The win2K and the winxp machine can ping each other, but
> > NEITHER can ping the win98 machine.....urg, I think I hate
> > windows.....
> >
> > - elmar
> >
> >
> Let me add the ipconfig /all for the 3 machines...
>
> Windows 2000 IP Configuration (no modem, just a NIC)
>
> Host Name . . . . . . . . . . . . : SHINOBI
> Primary DNS Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : ASUSTeK/Broadcom 440x
> 10/100 Integrated Controller
> Physical Address. . . . . . . . . : 00-E0-18-B1-19-C4
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.2.3
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.2.1
> DNS Servers . . . . . . . . . . . : 192.168.2.1
> Primary WINS Server . . . . . . . : 192.168.2.1
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
>
> Windows 98 IP Configuration (note, this has a disconnected modem
> installed)
>
> Host Name . . . . . . . . . : athlon
> DNS Servers . . . . . . . . : 192.168.2.1
> Node Type . . . . . . . . . : Broadcast
> NetBIOS Scope ID. . . . . . :
> IP Routing Enabled. . . . . : No
> WINS Proxy Enabled. . . . . : No
> NetBIOS Resolution Uses DNS : Yes
>
> 0 Ethernet adapter :
>
> Description . . . . . . . . : PPP Adapter.
> Physical Address. . . . . . : 44-45-53-54-00-00
> DHCP Enabled. . . . . . . . : Yes
> IP Address. . . . . . . . . : 0.0.0.0
> Subnet Mask . . . . . . . . : 0.0.0.0
> Default Gateway . . . . . . :
> DHCP Server . . . . . . . . : 255.255.255.255
> Primary WINS Server . . . . :
> Secondary WINS Server . . . :
> Lease Obtained. . . . . . . :
> Lease Expires . . . . . . . :
>
> 1 Ethernet adapter :
>
> Description . . . . . . . . : SMC EZ Card 10/100 (SMC1244TX)
> Physical Address. . . . . . : 00-50-BF-74-40-27
> DHCP Enabled. . . . . . . . : No
> IP Address. . . . . . . . . : 192.168.2.4
> Subnet Mask . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . : 192.168.2.1
> Primary WINS Server . . . . :
> Secondary WINS Server . . . :
> Lease Obtained. . . . . . . :
> Lease Expires . . . . . . . :
>
>
> Windows IP Configuration (XP machine, with a wireless and a modem as
> well as a NIC)
>
> Host Name . . . . . . . . . . . . : Flappy
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Ethernet adapter Wireless Network Connection:
>
> Media State . . . . . . . . . . . : Media disconnected
> Description . . . . . . . . . . . : Intel(R) PRO/Wireless
> 2200BG Network Connection
> Physical Address. . . . . . . . . : 00-0E-35-CB-F4-B5
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT
> Mobile Connection
> Physical Address. . . . . . . . . : 00-11-25-13-EF-21
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.2.12
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> IP Address. . . . . . . . . . . . : fe80::211:25ff:fe13:ef21%
> 5
> Default Gateway . . . . . . . . . : 192.168.2.1
> DNS Servers . . . . . . . . . . . : 192.168.2.1
> fec0:0:0:ffff::1%2
> fec0:0:0:ffff::2%2
> fec0:0:0:ffff::3%2
>
> Tunnel adapter Teredo Tunneling Pseudo-Interface:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-
> Interface
> Physical Address. . . . . . . . . : 00-00-51-3A-E7-2C-51-23
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . :
> 3ffe:831f:4004:1950:0:513a:e72c:5123
> IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%6
> Default Gateway . . . . . . . . . : ::
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> Tunnel adapter Automatic Tunneling Pseudo-Interface:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Automatic Tunneling
> Pseudo-Interface
> Physical Address. . . . . . . . . : C0-A8-02-0C
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : fe80::5efe:192.168.2.12%2
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2
> fec0:0:0:ffff::2%2
> fec0:0:0:ffff::3%2
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> One final piece of data - I CAN connect the XP machine to a share on
> the 2K machine and read/write to it, but the XP machine tells me that
> the win98 machine is not accessible (you may not have permission to
> use this network resource). OTOH, the win2K machine can see,
> read/write files to the 98 machine fine.
>
> grrrrr.
>


Time to uninstall ZoneAlarm.
Anonymous
April 21, 2005 1:46:38 AM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

In article <eI083x5QFHA.3140@tk2msftngp13.phx.gbl>, I.can@fly.com
says...
> > One final piece of data - I CAN connect the XP machine to a share on
> > the 2K machine and read/write to it, but the XP machine tells me that
> > the win98 machine is not accessible (you may not have permission to
> > use this network resource). OTOH, the win2K machine can see,
> > read/write files to the 98 machine fine.
> >
> > grrrrr.
> >
>
>
> Time to uninstall ZoneAlarm.


I did, and there's no change. The XP machine can't see the win2K
machine in the network neighborhood, although it can explicitly link
to shared folders on it, and the XP machine cannot connect to the
win98 machine shares even though it DOES see it in the network
neighborhood. The win32K machine cannot see the XP machine at all
either.
Anonymous
April 21, 2005 2:32:29 AM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

I had a W2000 machine sharing a printer with another W2000 machine (Both
advanced server I reckon) and for at least a year it told me the printer was
not accessible and then printed on it anyway, but it would not let me manage
the printer at all. Didn't bother me, all I wanted to do was print, but it
was annoying to get the message so I tried just about everything (except the
right thing, obviously) to fix it, including reinstall, blah blah blah...

Then after all that time and effort I went to use it one night and the
problem had gone. I had tried all kinds of option in network settings, wins
server stuff, I think the lot, nothing, nada, zilch, then suddenly it
worked, so I wish I could tell you what I did in case it had some bearing on
your sharing problem but I haven't a clue.

Do you have the same services running on the 2000 and XP machines? I have
found that network neighborhood (or equivalent) is not always reliable at
showing things accurately - ie sometimes a machine does not appear but is
there, and my network places seems a bit vague at times too, and sometimes
98 machines would appear 20 minutes later for no apparent reason - I wonder
if there's something in the way these items are "Refreshed" that anyone here
know of? Some kind of network "Polling" or "Announcement" or something?

Charlie



"jankin" <chagin_one@yahoo.com> wrote in message
news:MPG.1cd09841ccb474e698972b@news-server.nc.rr.com...
> In article <eI083x5QFHA.3140@tk2msftngp13.phx.gbl>, I.can@fly.com
> says...
>> > One final piece of data - I CAN connect the XP machine to a share on
>> > the 2K machine and read/write to it, but the XP machine tells me that
>> > the win98 machine is not accessible (you may not have permission to
>> > use this network resource). OTOH, the win2K machine can see,
>> > read/write files to the 98 machine fine.
>> >
>> > grrrrr.
>> >
>>
>>
>> Time to uninstall ZoneAlarm.
>
>
> I did, and there's no change. The XP machine can't see the win2K
> machine in the network neighborhood, although it can explicitly link
> to shared folders on it, and the XP machine cannot connect to the
> win98 machine shares even though it DOES see it in the network
> neighborhood. The win32K machine cannot see the XP machine at all
> either.
Anonymous
April 21, 2005 4:49:05 PM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

"jankin" <chagin_one@yahoo.com> wrote in message
news:MPG.1cd09841ccb474e698972b@news-server.nc.rr.com...
> In article <eI083x5QFHA.3140@tk2msftngp13.phx.gbl>, I.can@fly.com
> says...
> > > One final piece of data - I CAN connect the XP machine to a share on
> > > the 2K machine and read/write to it, but the XP machine tells me that
> > > the win98 machine is not accessible (you may not have permission to
> > > use this network resource). OTOH, the win2K machine can see,
> > > read/write files to the 98 machine fine.
> > >
> > > grrrrr.
> > >
> >
> >
> > Time to uninstall ZoneAlarm.
>
>
> I did, and there's no change. The XP machine can't see the win2K
> machine in the network neighborhood, although it can explicitly link
> to shared folders on it, and the XP machine cannot connect to the
> win98 machine shares even though it DOES see it in the network
> neighborhood. The win32K machine cannot see the XP machine at all
> either.

I have seen a few posts like this one before. In each and every
case the OP was prepared to bet a large amount of money on
not having a firewall installed, and in each and every case it turned
out that it was a firewall that he was not aware of. Now I'm not
saying that yours is a firewall issue - I'm simply stating my experience.
Anonymous
April 21, 2005 11:31:56 PM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

In article <#EJHALiRFHA.3076@tk2msftngp13.phx.gbl>, charlie@tames.net
says...
> Do you have the same services running on the 2000 and XP machines? I have
> found that network neighborhood (or equivalent) is not always reliable at
> showing things accurately - ie sometimes a machine does not appear but is
> there, and my network places seems a bit vague at times too, and sometimes
> 98 machines would appear 20 minutes later for no apparent reason - I wonder
> if there's something in the way these items are "Refreshed" that anyone here
> know of? Some kind of network "Polling" or "Announcement" or something?
>
> Charlie

Well, I just ran into an article that states one can add netbeui to
xp in order to retain compatability with earlier versions. So I will
do that as see what I can find.
Anonymous
April 22, 2005 1:45:51 AM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

In article <uzOvwyhRFHA.3476@TK2MSFTNGP10.phx.gbl>, I.can@fly.com
says...
....
>
> I have seen a few posts like this one before. In each and every
> case the OP was prepared to bet a large amount of money on
> not having a firewall installed, and in each and every case it turned
> out that it was a firewall that he was not aware of. Now I'm not
> saying that yours is a firewall issue - I'm simply stating my experience.
>

Well, this one is different, It wasn't the firewall, it was the lack
of netbeui on the xp machine. I installed that, and lo and behold -
all is kosher - I can see both the other machines, and they can see
the xp machine. Problem solved. Thanks a;;.

- elmar
Anonymous
April 22, 2005 1:49:21 AM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

In article <MPG.1cd1ca2e293688d798972c@news-server.nc.rr.com>,
chagin_one@yahoo.com says...
> In article <#EJHALiRFHA.3076@tk2msftngp13.phx.gbl>, charlie@tames.net
> says...
> > Do you have the same services running on the 2000 and XP machines? I have
> > found that network neighborhood (or equivalent) is not always reliable at
> > showing things accurately - ie sometimes a machine does not appear but is
> > there, and my network places seems a bit vague at times too, and sometimes
> > 98 machines would appear 20 minutes later for no apparent reason - I wonder
> > if there's something in the way these items are "Refreshed" that anyone here
> > know of? Some kind of network "Polling" or "Announcement" or something?
> >
> > Charlie
>
> Well, I just ran into an article that states one can add netbeui to
> xp in order to retain compatability with earlier versions. So I will
> do that as see what I can find.
>
>
Just to add data, now all works except neither the win2K nor the xp
machine can ping the win98 machine although the respond to the win98
machine's pings; all other ping directions also work. Everything
else works though (folder and file access, internet access, etc.).
Scanning the net, it is obvious that this is not a unique problem and
may be unsovable.
Anonymous
April 23, 2005 5:33:38 PM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

In article <MPG.1cd1ea5f3c8e4cef98972e@news-server.nc.rr.com>,
chagin_one@yahoo.com says...
> In article <MPG.1cd1ca2e293688d798972c@news-server.nc.rr.com>,
> chagin_one@yahoo.com says...
> > In article <#EJHALiRFHA.3076@tk2msftngp13.phx.gbl>, charlie@tames.net
> > says...
> > > Do you have the same services running on the 2000 and XP machines? I have
> > > found that network neighborhood (or equivalent) is not always reliable at
> > > showing things accurately - ie sometimes a machine does not appear but is
> > > there, and my network places seems a bit vague at times too, and sometimes
> > > 98 machines would appear 20 minutes later for no apparent reason - I wonder
> > > if there's something in the way these items are "Refreshed" that anyone here
> > > know of? Some kind of network "Polling" or "Announcement" or something?
> > >
> > > Charlie
> >
> > Well, I just ran into an article that states one can add netbeui to
> > xp in order to retain compatability with earlier versions. So I will
> > do that as see what I can find.
> >
> >
> Just to add data, now all works except neither the win2K nor the xp
> machine can ping the win98 machine although the respond to the win98
> machine's pings; all other ping directions also work. Everything
> else works though (folder and file access, internet access, etc.).
> Scanning the net, it is obvious that this is not a unique problem and
> may be unsovable.
>
OK - more data - I changed all 3 firewalls to the symantec client
(got rid of zonealarm entirely. NOW the machines can all ping each
other! So I have tcpip and netbeui running on all 3 machines,
including the xp machine. Two problems remain:

1) the win 98 machine that cannot see or connect to the win2K machine
in any manner. The win98 machine has logins enabled and they are
used. It can see the xp machine, but it csan't open the shared
foldres (demanding a password for IPC$)

2) the win2K machine can see all 3 machines, but cannot get to the xp
machines shared folders, rejecting the login unsername & password.
Needless top say, these do exist and I am not mispelling them.

Nopte that the XP machine can see & connect to all 3 mchines without
problems. (and no, I will not change all 3 machine to xp - I need
the win98 machine to run legacy programs).
Anonymous
April 24, 2005 3:51:28 AM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

"jankin" <chagin_one@yahoo.com> wrote in message
news:MPG.1cd41932457d59b898972f@news-server.nc.rr.com...
> In article <MPG.1cd1ea5f3c8e4cef98972e@news-server.nc.rr.com>,
> chagin_one@yahoo.com says...
> > In article <MPG.1cd1ca2e293688d798972c@news-server.nc.rr.com>,
> > chagin_one@yahoo.com says...
> > > In article <#EJHALiRFHA.3076@tk2msftngp13.phx.gbl>, charlie@tames.net
> > > says...
> > > > Do you have the same services running on the 2000 and XP machines? I
have
> > > > found that network neighborhood (or equivalent) is not always
reliable at
> > > > showing things accurately - ie sometimes a machine does not appear
but is
> > > > there, and my network places seems a bit vague at times too, and
sometimes
> > > > 98 machines would appear 20 minutes later for no apparent reason - I
wonder
> > > > if there's something in the way these items are "Refreshed" that
anyone here
> > > > know of? Some kind of network "Polling" or "Announcement" or
something?
> > > >
> > > > Charlie
> > >
> > > Well, I just ran into an article that states one can add netbeui to
> > > xp in order to retain compatability with earlier versions. So I will
> > > do that as see what I can find.
> > >
> > >
> > Just to add data, now all works except neither the win2K nor the xp
> > machine can ping the win98 machine although the respond to the win98
> > machine's pings; all other ping directions also work. Everything
> > else works though (folder and file access, internet access, etc.).
> > Scanning the net, it is obvious that this is not a unique problem and
> > may be unsovable.
> >
> OK - more data - I changed all 3 firewalls to the symantec client
> (got rid of zonealarm entirely. NOW the machines can all ping each
> other! So I have tcpip and netbeui running on all 3 machines,
> including the xp machine. Two problems remain:
>
> 1) the win 98 machine that cannot see or connect to the win2K machine
> in any manner. The win98 machine has logins enabled and they are
> used. It can see the xp machine, but it csan't open the shared
> foldres (demanding a password for IPC$)
>
> 2) the win2K machine can see all 3 machines, but cannot get to the xp
> machines shared folders, rejecting the login unsername & password.
> Needless top say, these do exist and I am not mispelling them.
>
> Nopte that the XP machine can see & connect to all 3 mchines without
> problems. (and no, I will not change all 3 machine to xp - I need
> the win98 machine to run legacy programs).
>

Mmh. It seems the firewall ***was*** the problem all along . . .
I suggest you get rid of NetBEUI. You don't need it, as TCP/IP
will do everything you want. Having an unnecessary protocol will
only cloud the issues.

About your Win98 problem: Make sure that all machines use
the same account / password. Also: Try to walk before you run,
by creating an ordinary share on the Win2000 PC instead of
trying to connect to the administrative share C$ straight away.

About your WinXP problem: Launch "My Computer" on the
WinXP PC, then click Tools / Folder Options / View and
click "Use simple file sharing".
Anonymous
April 24, 2005 3:51:29 AM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

In article <O$jxNuASFHA.1564@TK2MSFTNGP09.phx.gbl>, I.can@fly.com
says...
> Mmh. It seems the firewall ***was*** the problem all along . . .

My, doesn't crow taste good? <rueful grin> For win98 for certain,
you were right, I was wrong. Didn't bother the xp/2k connection much
though. With the Symantec firewall, since pings get through in all
directions, the trusted zone containing the range of IPs behind my
router seems to work.

> I suggest you get rid of NetBEUI. You don't need it, as TCP/IP
> will do everything you want. Having an unnecessary protocol will
> only cloud the issues.

Won't that destroy the network neighborhood functions, ie. no way to
browse the network, etc.?

> About your Win98 problem: Make sure that all machines use
> the same account / password.

Yes, - that I know of and have done

> Also: Try to walk before you run,
> by creating an ordinary share on the Win2000 PC instead of
> trying to connect to the administrative share C$ straight away.

I am trying to connect to a specific shared folder to both the 2K
machine and the XP machine. The IPC$ comes up for the XP machine
only; the win2K machine can't be "reached" by the win98 machine.

> About your WinXP problem: Launch "My Computer" on the
> WinXP PC, then click Tools / Folder Options / View and
> click "Use simple file sharing".

That was the default, and I just confirmed it. More diddling, I
guess.....
Anonymous
April 24, 2005 8:33:18 AM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

On Sat, 23 Apr 2005 16:45:26 GMT, jankin <chagin_one@yahoo.com> wrote:

>> I suggest you get rid of NetBEUI. You don't need it, as TCP/IP
>> will do everything you want. Having an unnecessary protocol will
>> only cloud the issues.
>
>Won't that destroy the network neighborhood functions, ie. no way to
>browse the network, etc.?
>

When you installed netbeui you merely replaced the (not working)
tcp/ip as the protocol being used to network the machines locally.

After you uninstall all the firewalls, if you can ping okay in all
directions then you should be able to do away with netbeui since
tcp/ip will be working correctly. If you can't ping in all directions
then something is still wrong.

In theory it should be okay to leave netbeui installed and the two
protocols (netbeui and tcp/ip) should happily co-exist but xp doesn't
appear to handle this as well as win9x so most pundits reckon just
using the one protocol is the best way to go.


Jim.
Anonymous
April 24, 2005 10:53:29 AM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

If it works, why fix it? Besides the old saw about NETBEUI being safer
from intrusion on internet capable machines.

James Egan wrote:
> When you installed netbeui you merely replaced the (not working)
> tcp/ip as the protocol being used to network the machines locally.
>
> After you uninstall all the firewalls, if you can ping okay in all
> directions then you should be able to do away with netbeui since
> tcp/ip will be working correctly. If you can't ping in all directions
> then something is still wrong.
>
> In theory it should be okay to leave netbeui installed and the two
> protocols (netbeui and tcp/ip) should happily co-exist but xp doesn't
> appear to handle this as well as win9x so most pundits reckon just
> using the one protocol is the best way to go.
>
>
> Jim.
>
Anonymous
April 24, 2005 12:49:29 PM

Archived from groups: microsoft.public.win2000.networking,microsoft.public.win98.networking,microsoft.public.windowsxp.newusers (More info?)

"jankin" <chagin_one@yahoo.com> wrote in message
news:MPG.1cd44627c5c02cd989730@news-server.nc.rr.com...
> In article <O$jxNuASFHA.1564@TK2MSFTNGP09.phx.gbl>, I.can@fly.com
> says...
> > Mmh. It seems the firewall ***was*** the problem all along . . .
>
> My, doesn't crow taste good? <rueful grin>

This has nothing to do with crowing. I recommended several
times that you must uninstall ZoneAlarm, and you actually
confirmed, in writing, that you had removed it. It now comes
as a bit of a surprise that you misled everyone and did not
uninstall it until much, much later. We respondents cannot
see your machine - we must rely on your open and honest
reports. If they are not open and honest then you're wasting
everyone's time.
!