A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » New Users to Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

win98se-win2kpro-winxp home lan



 
 
Thread Tools Display Modes
  #1  
Old April 16th 05, 02:24 AM
Pegasus \(MVP\)
external usenet poster
 
Posts: n/a
Default win98se-win2kpro-winxp home lan


"jankin" wrote in message
...
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.


Ads
  #2  
Old April 17th 05, 01:48 AM
Pegasus \(MVP\)
external usenet poster
 
Posts: n/a
Default


"jankin" wrote in message
...
In article ,
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.


  #3  
Old April 17th 05, 11:26 PM
Pegasus \(MVP\)
external usenet poster
 
Posts: n/a
Default


"jankin" wrote in message
...
In article ,
says...
In article ,

says...

"jankin" wrote in message
...
In article ,

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.


  #5  
Old April 21st 05, 04:32 AM
Charlie Tame
external usenet poster
 
Posts: n/a
Default

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" wrote in message
...
In article ,
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.



  #6  
Old April 23rd 05, 02:51 PM
Pegasus \(MVP\)
external usenet poster
 
Posts: n/a
Default


"jankin" wrote in message
...
In article ,
says...
In article ,
says...
In article ,

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


  #8  
Old April 24th 05, 04:33 AM
James Egan
external usenet poster
 
Posts: n/a
Default

On Sat, 23 Apr 2005 16:45:26 GMT, jankin 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.

  #9  
Old April 24th 05, 12:53 PM
Airman Thunderbird
external usenet poster
 
Posts: n/a
Default

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.

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Differences between XP Home and XP Pro? KunK General XP issues or comments 13 November 9th 04 06:08 PM
WinXP Home share problem Brian E. Clark Networking and the Internet with Windows XP 1 October 11th 04 10:57 PM
Need To Use WinXP (Home) Recovery Console Eric Performance and Maintainance of XP 2 October 11th 04 02:59 AM
winXP Home and or Professional News Rho_1r General XP issues or comments 0 September 21st 04 11:49 PM
XP Home vs. Pro; Feature Contrast Chad Harris General XP issues or comments 20 July 30th 04 09:36 PM






All times are GMT +1. The time now is 11:31 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.