XP professional - network

Howdy.

I cannot for the life of me figure this out. I have 2 machines on home network. I just want file sharing between the two. Both run XP Professional with up-to-date fixes.
(Build 2600.xpsp2.030422-1633).

Athlon PC: 192.168.1.1
Intel PC: 192.168.1.2

Both NIC's have Client for MS Networks, File & Printer Sharing, MS TCP/IP v6, NWLink NetBIOS, NWLink IPX/SPX/NetBIOS , Internet Protocol (TCP/IP) checked.

I can do the following:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

Wed 10/08/2003 19:17:58.62
C:\Documents and Settings\dad.ATHLON2600> net start browser
The Computer Browser service is starting.....
The Computer Browser service was started successfully.


Wed 10/08/2003 19:19:45.37
C:\Documents and Settings\dad.ATHLON2600> net view
Server Name Remark

-------------------------------------------------------------------------------
\\ATHLON2600 Main PC
\\INTEL-P3 Intel Pentium III
The command completed successfully.

Wed 10/08/2003 19:21:50.42
C:\Documents and Settings\dad.ATHLON2600> net view \\intel-p3
Shared resources at \\intel-p3

Intel Pentium III

Share name Type Used as Comment

-------------------------------------------------------------------------------
c Disk
D Disk
E Disk
F Disk
g Disk
h Disk
I Disk
j Disk
k Disk
Printer Print HP LaserJet 6L
Printer2 Print Print to this device to send a photo quality fax.
Printer3 Print Print to this device to send a fax.
Printer5 Print hp LaserJet 1000
Printer6 Print Acrobat Distiller
SharedDocs Disk
The command completed successfully.

Wed 10/08/2003 19:22:34.42
C:\Documents and Settings\dad.ATHLON2600> dir \\intel-p3\d
Volume in drive \\intel-p3\d is INTEL PIII
Volume Serial Number is 3EFD-9E1F

Directory of \\intel-p3\d

File Not Found

Wed 10/08/2003 19:23:15.20
C:\Documents and Settings\dad.ATHLON2600> dir \\intel-p3\d\w*
Volume in drive \\intel-p3\d is INTEL PIII
Volume Serial Number is 3EFD-9E1F

Directory of \\intel-p3\d

07/07/2003 07:22 PM <DIR> WINDOWS
0 File(s) 0 bytes
1 Dir(s) 1,154,478,080 bytes free

Wed 10/08/2003 19:23:19.76
C:\Documents and Settings\dad.ATHLON2600> net view \\intel-p3
Shared resources at \\intel-p3

Intell Pentium III

Share name Type Used as Comment

-------------------------------------------------------------------------------
c Disk
D Disk
E Disk
F Disk
g Disk
h Disk
I Disk
j Disk
k Disk
Printer Print HP LaserJet 6L
Printer2 Print Print to this device to send a photo quality fax.
Printer3 Print Print to this device to send a fax.
Printer5 Print hp LaserJet 1000
Printer6 Print Acrobat Distiller
SharedDocs Disk
The command completed successfully.

Wed 10/08/2003 19:23:57.48
C:\Documents and Settings\dad.ATHLON2600> ping intel-p3
Ping request could not find host intel-p3. Please check the name and try again.

Wed 10/08/2003 19:24:23.45
C:\Documents and Settings\dad.ATHLON2600> ping 192.168.1.2

Pinging 192.168.1.2 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Wed 10/08/2003 19:25:07.10
C:\Documents and Settings\dad.ATHLON2600> ping athlon2600

Pinging ATHLON2600 [::1] with 32 bytes of data:

Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

Ping statistics for ::1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Wed 10/08/2003 19:26:15.98
C:\Documents and Settings\dad.ATHLON2600> ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

My questions:

1) Why can't I get a complete directory listing? If there are more than 12 files with the beginning letter, I get the "File Not Found" Error.
2) If files are short, I can copy them.
3) Can't view directories at all in WinExplorer, but shares are displayed in Network Neighborhood.
4) Why can I do a short 'dir' but cannot ping?
5) Why does Athlon see Intel shares, but not vice-versa? (Intel 'net view' only shows Intel)
6) Neither machine can ping the other?

whew!

any gurus out there want to tackle this one?

thank you.

s'marty

Geez - that is a doozie...

In my experience as a Windows network systems administrator, I can suggest that you ensure the following three services are running on both machines:

Computer Browser
Server
Workstation

Also, ensure your IP configuration is correct. One thing I'd like to suggest is to remove IPv6 unless there is some odd reason you absolutely have to have it. Sounds to me like you have a fairly simple network, so IPv4 should suffice. You can also remove the NWLink protocols (unless you are participating on a NetWare network, which I doubt).

Additionally, ensure both computers are configured for the same subnet. 192.168 is traditionally a class C subnet, so both machines should have 255.255.255.0 as their subnet mask.

On a network as simple as yours (from what you described), there should be no reason to have any wierd TCP/IP configuration, so set it all back to default with the exception of the IP address and subnet mask.

(For all you wise-guys out there: yes, I know 255.255.255.0 is not the only subnet mask possible, so please don't waste our time. I'm trying to keep it simple here, and I probably know more about TCP/IP networking than you.)

Anyway, if you still have problems, you may consider one alternative that may be quicker and easier than trying to fix this: reload the OSs on both machines. Why both? One of them's messed up, it seems to me, and it could be rather difficult to figure out which one. The reason I recommend reloading is because sometimes it's a quicker and easier alternative (believe me on this one).

Standing by...

Matthew,

All three of those services WERE running.

i'm going to re-install XP-Pro on the Intel-p3 and see what happens.

Interestingly enough, when both PC's had XP service pack 1, (xpsp1.20828-1920), the symptoms i'm having now were present.

When i upgraded the Athlon2600 to service pack 1a, (xpsp2.030422-1633), pings worked both ways, the Athlon could "explorer.exe" the Intel-p3, and everything was ok 'cept the Intel could not explore the Athlon.

So i figured if the SP1A fixed everything on the Athlon, it would fix everything on the Intel. This was a wrong assumption. An uninstall of SP1a on the Intel didn't work.

So, I will re-install the OS and see if i'm back where i started last week.

Thank you.

s'martymarty

Yeah, I just thought I'd mention the services just in case.

Good luck with the reload, and to make sure you're starting off fresh, don't install any other networking protocols or services.

Let me know how it goes, and I'll stand by to help if you need it.

matthew,

well i re-installed XP Pro on the intel, and as you predicted, the intel machine works as before i installed SP1a.

i can now ping both machines by name and IP.

however, the intel-p3 can NOT do a "net view \\athlon2600" or "net view \\192.168.1.1"--'System error 1726 has occurred. The remote procedure call failed.'

it now acts as the athlon did before the intel re-install.

the athlon2600 receives complete directory listings of any of the intel-p3 shares, and can copy any size file FROM the intel-p3 to the athlon. however, the athlon can NOT write a file greater than 383 bytes without getting a "The specified network name is no longer available." error message.

the athlon CAN, however, write files greater than 383 bytes if i keep the record size at 383 bytes or less.

an interesting note: i will get a "request timed out" on any ping with a length > 463 bytes. this happens either way--that is, athlon pinging intel, intel pinging athlon.

i'd prefer not to re-install on the athlon as i have so many many things installed--it would take a couple days to reinstall everything.

any more ideas anyone??

thanks,
s'marty marty