Forum Home
Press F1
 
Thread ID: 68679 2006-05-07 08:32:00 WinXP File-sharing issues Chilling_Silence (9) Press F1
Post ID Timestamp Content User
452927 2006-05-09 08:31:00 The NV Firewall, I think isnt a LAN card. Its onboard more recent mobos.

And it can screw things up, including corrupting files you download.

If its enabled.
Speedy Gonzales (78)
452928 2006-05-09 14:16:00 I really cant be assed going up to the house right now to check it out and coz im such a lazy sod i havent setup anything like VNC...

Anyways, no, its not any of the nForce-related motherboards or anything. The LAN card is a Realtek one IIRC.
Chilling_Silence (9)
452929 2006-05-10 00:09:00 Just to clarify:
* You have several network devices.
* All but one can connect to \\192.178.0.7\shared
Or did I miss something?
kingdragonfly (309)
452930 2006-05-10 14:39:00 Correct!

And I KNOW its not a permissions problem either because \\192.168.0.7 is a linux box and Ive set it up so it needs no authentication :)
Chilling_Silence (9)
452931 2006-05-11 08:09:00 Any other suggestions ladies and gents? Chilling_Silence (9)
452932 2006-05-11 11:42:00 The linux box is on
Clashing IP's
Subnet mask
Delete the mapped drive then setup again
Try a browse in my network places
Check cables

LOL your sig makes me want to PM you :D
Rob99 (151)
452933 2006-05-11 22:40:00 Not much to go on but you could look here.. (forums.gentoo.org) Myth (110)
452934 2006-05-12 00:25:00 Workgroup=WORKGROUP (or the same on all) for Windows Netwrpok? Graham L (2)
452935 2006-05-12 02:34:00 The problem is NOT the server

As mentioned, the samba server is FINE, I have NO PROBLEMS setting that up coz its accessible from other boxes

Yes, workgroups the same
Chilling_Silence (9)
452936 2006-05-12 04:02:00 The "\\192.168.0.7\" address might not work because the last "\" is specifying the root directory of the Linux box running the Samba server.

But it's not getting far enough to hit that possible problem. The "... can't find..." and "...cannot be reached" messages indicate a routing problem. Since it "should" be on the same LAN, there shouldn't be any routing needed. :groan: Somehow that address doesn't appear (to MS) to be on the same LAN. ;)

Subnet masks?, actual IP address of that client computer? (yes, you "know" it's right).
Graham L (2)
1 2 3 4