Cannot network two Windows XP Pro computers via IP

[John]

*********** SYSTEM *****************

Windows XP Professional, SP1

Computer A - 192.168.2.100 Subnet 255.255.255.0
Computer B - 192.168.2.101 Subnet 255.255.255.0

Both computers are connected to a NAT router which connects to the Internet.
The NAT uses a single static IP address at my ISP for the gateway out to the Internet.

Disabled NetBIOS over TCP/IP for both computers.
This was done for security reasons.

*********** PROBLEM *****************

Problem: Cannot network two Windows XP Pro computers via IP

I tell MAP Network Drive to use Z: to \\192.168.2.100\C
where C is network shared.

MAP Network Drive says it "cannot find network path for
Z: to \\192.168.2.100\C"

I can ping both machines using their IP addresses.

What is really strange is that sometimes when I boot both
systems they do map and it works. But for some reason
they refuse to map now.

Any feedback would be appreciated. Thanks

 

[Yves Leclerc]

Both computer MUST BE part of the same Workgroup.

*********** SYSTEM *****************

Windows XP Professional, SP1

Computer A - 192.168.2.100 Subnet 255.255.255.0
Computer B - 192.168.2.101 Subnet 255.255.255.0

Both computers are connected to a NAT router which connects to the Internet.
The NAT uses a single static IP address at my ISP for the gateway out to the Internet.

Disabled NetBIOS over TCP/IP for both computers.
This was done for security reasons.

*********** PROBLEM *****************

Problem: Cannot network two Windows XP Pro computers via IP

I tell MAP Network Drive to use Z: to \\192.168.2.100\C
where C is network shared.

MAP Network Drive says it "cannot find network path for
Z: to \\192.168.2.100\C"

I can ping both machines using their IP addresses.

What is really strange is that sometimes when I boot both
systems they do map and it works. But for some reason
they refuse to map now.

Any feedback would be appreciated. Thanks

 

[John]

They are - MSHOME.
Both computer MUST BE part of the same Workgroup.

*********** SYSTEM *****************

Windows XP Professional, SP1

Computer A - 192.168.2.100 Subnet 255.255.255.0
Computer B - 192.168.2.101 Subnet 255.255.255.0

Both computers are connected to a NAT router which connects to the Internet.
The NAT uses a single static IP address at my ISP for the gateway out to the Internet.

Disabled NetBIOS over TCP/IP for both computers.
This was done for security reasons.

*********** PROBLEM *****************

Problem: Cannot network two Windows XP Pro computers via IP

I tell MAP Network Drive to use Z: to \\192.168.2.100\C
where C is network shared.

MAP Network Drive says it "cannot find network path for
Z: to \\192.168.2.100\C"

I can ping both machines using their IP addresses.

What is really strange is that sometimes when I boot both
systems they do map and it works. But for some reason
they refuse to map now.

Any feedback would be appreciated. Thanks

 

[NobodyMan]

*********** SYSTEM *****************

Windows XP Professional, SP1

Computer A - 192.168.2.100 Subnet 255.255.255.0
Computer B - 192.168.2.101 Subnet 255.255.255.0

Both computers are connected to a NAT router which connects to the Internet.
The NAT uses a single static IP address at my ISP for the gateway out to the Internet.

Disabled NetBIOS over TCP/IP for both computers.
This was done for security reasons.

*********** PROBLEM *****************

Problem: Cannot network two Windows XP Pro computers via IP

I tell MAP Network Drive to use Z: to \\192.168.2.100\C
where C is network shared.

MAP Network Drive says it "cannot find network path for
Z: to \\192.168.2.100\C"

I can ping both machines using their IP addresses.

What is really strange is that sometimes when I boot both
systems they do map and it works. But for some reason
they refuse to map now.

Any feedback would be appreciated. Thanks

I assume you know that both computers must be on the same workgroup,
and that both computers must have identical user accounts with
identical, non-blank passwords.

I pose a question: why assign hard-coded IP addresses? Let your
broadband router act as a DHCP server and hand out addresses. That
may very well help you out.

 

[Nepatsfan]

For starters, if both machines are using XP Pro in a workgroup and simple
file sharing has not been disabled, you do not need to add user accounts to
either PC. Windows will use the Guest account to access resources within the
LAN. If you're curious do a search on Google or MSKB with the term
"forceguest".

When you enter static IP addresses, the value for the Default Gateway should
be the local address of your router (e. g. 192.168.2.1) not the address your
ISP assigned to you. Check the Lan section of your router's configuration
app to find the correct value.
You should enter the addresses of your ISP's DNS servers if you want to
access the internet.

Post back if you're still having problems.

Nepatsfan

 

[John]

File & Print sharing is installed.
The NAT router is a fire wall.
Zone Alarm is off while trying to find problem.
Disabled NetBIOS over TCP/IP for both computers.
This was done for security reasons since hackers like
to get through firewalls via NetBIOS ports.
This is why I use \\192.168.2.100\C rather than say
\\MyComputer\C
Computers have different names.
Both have same workgroup name.

When I booted both systems this afternoon they were
able to network. I have no idea why they sometimes
network and other times they don't see each other.
I assume there is some network cache that needs to get
flushed, but I don't know what to flush.

Thank you for your feedback.

 

[Steven Cooke]

They dont have to be in the same workgroup and it doesnt seem like there are
and software issues, except maybe try creating the username and password
account you use on the one pc, on the other pc, otherwise it sounds like its
probably a network card fault

--
Steven Cooke


File & Print sharing is installed.
The NAT router is a fire wall.
Zone Alarm is off while trying to find problem.
Disabled NetBIOS over TCP/IP for both computers.
This was done for security reasons since hackers like
to get through firewalls via NetBIOS ports.
This is why I use \\192.168.2.100\C rather than say
\\MyComputer\C
Computers have different names.
Both have same workgroup name.

When I booted both systems this afternoon they were
able to network. I have no idea why they sometimes
network and other times they don't see each other.
I assume there is some network cache that needs to get
flushed, but I don't know what to flush.

Thank you for your feedback.

 

[cquirke (MVP Win9x)]

Windows XP Professional, SP1

Computer A - 192.168.2.100 Subnet 255.255.255.0
Computer B - 192.168.2.101 Subnet 255.255.255.0

Both computers are connected to a NAT router which connects to the Internet.
The NAT uses a single static IP address at my ISP for the gateway out to the Internet.

What's the router'sinternal (gateway) IP?

Disabled NetBIOS over TCP/IP for both computers.
This was done for security reasons.

OK. Any firewall sware running?

Problem: Cannot network two Windows XP Pro computers via IP

As per Ping 192.168.2.100, Ping A or File and Print Sharing?

If you can Ping, then that rules out TCP/IP issues, and leaves you
with File and Print Sharing (F&PS) issues - such as:
- matching workgroup name?
- clashing PC names?
- F&PS bound to the LAN card?
- anything shared?
- firewall getting in the way?
- any other "yopu aren't allowed to do that" issues?

As you probably know, you should NOT have to open F&PS ports in the
router for F&PS on the LAN to work. But if the PC's are running
firewall software on the LAN card that connects to do F&PS, then ports
may have to be opened in that firewall software.

I tell MAP Network Drive to use Z: to \\192.168.2.100\C
where C is network shared.

Bad idea to full-share all of C:\ and especially to call that share C.
I don't do that, even for testing purposes - several malware can
attack such shares directly, dropping themselves into Startup groups,
patching themselves into Win.ini Run=, etc. etc.

MAP Network Drive says it "cannot find network path for
Z: to \\192.168.2.100\C"

If possible, it may be best to use direct \\pcname\path syntax rather
than mapping drive letters. In this context, it's one less thing to
tshoot... can you see the workgroup in Windows Explorer? If so, what
PCs can you see in there?

Note: You need to explicitly share something. If by ...\C you ere
expecting to see the hidden admin c$ share, you shouldn't - by design,
it's supposed to stay hidden (tho we all know it's there)

I can ping both machines using their IP addresses.

Ah; I was waiting for that

What is really strange is that sometimes when I boot both
systems they do map and it works. But for some reason
they refuse to map now.

Look for name or IP clashes, including the share name itself. An
oddity in Win9x is that if the volume name had a dir shared with same
name on it (say, I have D: called DATA and I share D:\DATA as a share
called DATA) one variably finds it impossible to see anything in there

 

[cquirke (MVP Win9x)]

File & Print sharing is installed.
The NAT router is a fire wall.
Zone Alarm is off while trying to find problem.

May have to try removing that altogether :-(

Disabled NetBIOS over TCP/IP for both computers.
This was done for security reasons since hackers like
to get through firewalls via NetBIOS ports.
This is why I use \\192.168.2.100\C rather than say
\\MyComputer\C

Better (additive) safety is to share less, and full-share even less.
FWIW, I never full share any part of any startup axis (dropper attack)
and have useage policy about what is expected to be where. For
example, if users know there are never to be code files in a shared
data subtree, and they can see file name extensions of course, then
they won't peck on MyPicture..JPG.exe when that turns up there.

Or put it this way; If I'm there, they won't do it twice

Computers have different names.
Both have same workgroup name.

When I booted both systems this afternoon they were
able to network. I have no idea why they sometimes
network and other times they don't see each other.

That behaviour may be mediated via the Network Client; to do with who
is browse master, or the automatic election thereof. Only 2 PCs mean
it's not too many incoming connects (XP Home limits to 5, Pro to 10)

I've never changed NetBIOS over TCP/IP status, so I can't tell you if
that's a problem. To test, I'd unplug the DSL line and disable that
setting, see if that holds; if so, so pros and cons to figure out.

I assume there is some network cache that needs to get
flushed, but I don't know what to flush.

The way that F&PS "sees" PCs on the LAN is a bit wobbly - seems as if
a search is made every now and then, etc. Usual trade-off between
"look often, too bad about the traffic" vs. "look seldom, faster LAN".

 

[jeffrey]

Hi,

Try restarting the Browse Master. Designate your main computer as the
browse master and turn it off on the other computer. That might be your
problem. Especially if you can ping the other computer, but not able to
connect to it.

Jeff

 

[John]

It is important to note that I have
"Disabled NetBIOS over TCP/IP for both computers"
in the TCP/IP properties.

Therefore, if I type
nbtstat -c or
nbtstat -n
It says there are "no names in cache"
so there does not appear to be a Master Browser.

In theory, a MAP Network Drive of Z: to \\192.168.2.100\C
should directly find the IP address without requiring
a Master Browser. What is strange is sometimes it works
and other times it does not.

Thank you for your feedback.

 

[cquirke (MVP Win9x)]

It is important to note that I have
"Disabled NetBIOS over TCP/IP for both computers"
in the TCP/IP properties.

Therefore, if I type
nbtstat -c or
nbtstat -n
It says there are "no names in cache"
so there does not appear to be a Master Browser.

In theory, a MAP Network Drive of Z: to \\192.168.2.100\C
should directly find the IP address without requiring
a Master Browser. What is strange is sometimes it works
and other times it does not.

Ahhh... if killing NetBIOS kills the ability to find PCs by name, then
I'd expect most of not all bets to be off for F&PS.

Using raw IP addresses may find PCs when using TCP/IP services, but
F&PS is not a TCP/IP service - it's an MS OS service that doesn't care
what network protocol it's travelling on.

So you may find navigating to 192.168.2.100\C works, on the basis that
Windows Explorer also operates as IE, and may work a la FTP or
something. But for true file system namespace browsability, you may
need full F&PS visibility.

The above is conceptual guesswork on my part; perhaps a newtork guru
can come along, flame my mistakes, and see us right

-------------------- ----- ---- --- -- - - - -

Reality is that which, when you stop believing
in it, does not go away (PKD)

 

[John]

Cquirke

Thank you for the feedback.

I disabled ZoneAlarm on both computers while
trying to isolate the problem.

It is important to note that I have
"Disabled NetBIOS over TCP/IP for both computers"
in the TCP/IP properties.

Therefore, if I type
nbtstat -c or
nbtstat -n
It says there are "no names in cache"
so there does not appear to be a Master Browser.

In theory, a MAP Network Drive of Z: to \\192.168.2.100\C
should directly find the IP address without requiring
a Master Browser.

What is strange is sometimes the computers network just fine
and othertimes they do not.

Yes, I know I should not share the entire C drive as
the unhidden I named "C", but I do. It is interesting that
when the systems do network, File Explorer does not allow you
to see the contents of the Documents and Settings directory of Z
as a security protection.

I am unclear if I can uninstall File & Printer Sharing. Specifically,
I have a Xerox printer on the ethernet. Both computers have the
Xerox driver installed as "locally" - not shared. So I am not sure
if the File & Printer Sharing is required for this to continue to work.
However, after uninstalling the F&PS, the printer still seems to be working.
I need to run further tests to see if having uninstalled the F&PS solves
the problem of the computers sometimes not networking.

Thank you for your feedback.

 

[cquirke (MVP Win9x)]

Cquirke
Hi!

I disabled ZoneAlarm on both computers while
trying to isolate the problem.

OK. There can be a difference between disabling and uninstalling ZA,
based on earlier experience in Win9x at least (something I found out
the hard way, when chasing "why doesn't it network"). Specifically,
there are ZA components loaded as services that remain at least
partially effective even if ZA's disabled through the "front door".

I know it's a drag uninstalling and re-installing (SR can be your pal
there) but it's a bullet you may have to bite. Put it this way: if it
was a factor, how else would find that out?

In theory, a MAP Network Drive of Z: to \\192.168.2.100\C
should directly find the IP address without requiring
a Master Browser.

I don't know enough about how F&PS and Client work to figure that out.
Specifically, I don't know whether the logic still relies on the "what
is the PC's name?" logic to resolve the share name of C - I know the
path may be TCP/IP-valid, but etc.

What is strange is sometimes the computers network just fine
and othertimes they do not.

Yes; I'm wondering if there's some wobbliness about initial states
being refreshed by browse-master scans that fail.

Yes, I know I should not share the entire C drive as
the unhidden I named "C", but I do.

It is interesting that when the systems do network, File Explorer
does not allow you to see the contents of the Documents and
Settings directory of Z

Try writing programatically to a StartUp group (the path to AllUsers
is guessable) as malware would do. Even if that's closed, there are
other auto-run opportunites, e.g. \Autorun.inf, Desktop.ini, and
possibly some path override effects such as those formally used by
malware, e.g. dropping a \explorer.exe etc.

Even if you manage these risks (e.g. set NoDrivetypeAutoRun to 9D
instead of 91 so HD volumes don't autorun) there can be brittleness
there (e.g. CD titles that force NoDriveTypeAutoRun to 91 or 95).

So etc.

I am unclear if I can uninstall File & Printer Sharing. Specifically,
I have a Xerox printer on the ethernet. Both computers have the
Xerox driver installed as "locally" - not shared. So I am not sure
if the File & Printer Sharing is required for this to continue to work.

In Win9x, file sharing and printer sharing can be set individually; I
don't know if XP supports this, or how, or whether you can share
printers but not files by controlling ports in firewalls in a
particular way. AFAIK, printer sharing doesn't require file sharing,
and wouldn't care about //192.168.x.x/C either way.

However, after uninstalling the F&PS, the printer still seems to be working.

Cool! It may even work independently of F&PS, e.g. if it has its own
IP on the LAN and thus not "owned" by any particular PC.

Thank you for your feedback.

Keep 'em coming ;-)