file/printer sharing

L

Lane

Hi,

I have 2 computers PCA and PCB running win xp sp2. One is connected directly
to a router, which is connected to a DSL modem. Another is connected using a
wireless USB connector.

I tried to run the network setup wizard on both computers using the
other->"This computer connects to the internet directly or through a network
hun. Other computers on my network also connect to the internet directly or
through a hub." option with same workgroup name, but I don't see anything in
my network places. I also tried to add a network place "\\PCB\SharedDocs",
but that doesn't connect either.

I guess the problem is one computer is not seeing the other computer. I
can't ping eachother.

Can someone please help me with this?

Thanks,
Lane
 
G

Guest

With windows xp sp1 you need to disable the windows xp firewall or open up
some ports for file sharing/printer sharing to work
check this out, Troubleshooting File and Printer Sharing in Microsoft
Windows XP:
microsoft.com/downloads/details.aspx?FamilyID=fd7fd48d-6b4a-448e-a632-076f98a351a2&displaylang=en
check this out too =), How to configure file sharing in Windows XP:
support.microsoft.com/default.aspx?scid=kb;en-us;304040
 
S

Steve Winograd [MVP]

"Carey Holzman" said:
The first thing you need to be able to do, before you go any further, is to
be able to ping one computer from the other.

I recommend you follow Tip #1 on all PCs at
www.careyholzman.com/netfixes.htm

Carey
Click to expand...

Carey, the steps in your Tip #1 don't apply to Windows XP, don't have
anything to do with pinging one computer from another, and don't have
anything to do with the problem that Lane reports.

Lane, that Wizard option causes the Wizard to enable XP's Internet
Connection Firewall, which blocks file and printer sharing.

Tell the Wizard that the computers connect to the Internet through a
residential gateway.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
C

Carey Holzman

Steve,

My tips do, in fact, apply to Windows XP and do resolve many ping issues.

Read my guestbook and see for yourself.

Carey
 
L

Lane

Steve,

Thanks for your response.

I tried that option as well, but my computer just doesn't see the other one.
I turn off the windows firewall upon completion of the wizard. Also, file
and printer sharing is in the exception list, because I am using SP2.
 
L

Lane

Carey,

Thanks for your reply.

I can't access your website for some reason. I guess I need to have them
able to ping eachother before they can share anything.
 
S

Steve Winograd [MVP]

"Carey Holzman" said:
Steve,

My tips do, in fact, apply to Windows XP and do resolve many ping issues.

Read my guestbook and see for yourself.

Carey
Click to expand...

No, your tips don't apply.

With a single exception, noted below, the network settings in Tip #1
don't exist in Windows XP. They exist in Windows 95/98/Me, but not in
Windows XP. Anyone who actually tries applying Tip #1 on a Windows XP
computer can see that. Do you have a computer running Windows XP? If
so, try Tip #1 and see. Let's look at each of your steps and see why
they don't apply to Windows XP:

1. The patch is only for Windows Me.
2. There's no Network icon in Control Panel.
3. NetBEUI isn't supported in Windows XP. IPX/SPX has a
different name.
4. There's no "Log on to Windows XP domain" setting.
5. There's no BINDINGS tab.
6. There's no BINDINGS tab or "Allow Binding to ATM" setting.
7. There's no "I want to enable NetBIOS over IPX/SPX" setting.
8. There's no Browse Master or LM Announce setting.
9. There's no Primary Network Logon.
10. There's no "File and Printer Sharing" button.
11. There's no Identification tab.
12. There's no Access Control tab.
13. There's no Sharing tab.
14. This step says it applies to Windows 95 and 98.
15. There's no Entire Network icon in My Network Places.
16. This is the only step that applies to Windows XP.
18-22. There's no NetCrawl registry key.

Tip #1 doesn't have anything to do with pinging. Pinging uses only
the TCP/IP protocol. It doesn't use any of the other network settings
that Tip #1 says to check: IPX/SPX, File and Printer Sharing, Client
for Microsoft Networks, bindings, sharing, workgroup names, access
control, etc. None of those settings have any effect on pinging. If
you think that they do, then you don't understand Windows networking.

Tip #1 doesn't say anything about pinging. It doesn't mention
firewalls, which are the most likely cause of pinging problems.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
L

Lou Ramsey

Justin said:
With windows xp sp1 you need to disable the windows xp firewall or open up
some ports for file sharing/printer sharing to work
check this out, Troubleshooting File and Printer Sharing in Microsoft
Windows XP:
microsoft.com/downloads/details.aspx?FamilyID=fd7fd48d-6b4a-448e-a632-076f98a351a2&displaylang=en
check this out too =), How to configure file sharing in Windows XP:
support.microsoft.com/default.aspx?scid=kb;en-us;304040
Click to expand...

Justin,

Your posts would be sort of useful if you could post links properly.

Lane, Try these links:
http://www.microsoft.com/downloads/...db-aef8-4bef-925e-7ac9be791028&DisplayLang=en
http://www.microsoft.com/downloads/...8d-6b4a-448e-a632-076f98a351a2&displaylang=en
http://support.microsoft.com/?id=304040
 
C

Carey Holzman

My web host is having some difficulties today.

Don't let the opinions of others discourage you from trying any suggestion
anyone might be kind enough to offer. Steve Winograds comments are quite
common and, well, all I can say is see for yourself if he is right or wrong.
:)

Carey
 
C

Carey Holzman

Steve,

The tips apply universally to all OSes. It does not hold the users hand,
step by step, but rather gets to the point on what needs to be done.

With regards to the firewall: The tips have always started by saying to
uinstall firewall software software and/or to disable the Windows XP
firewall. Recently, the tips were re-written and re-formated by a company to
make them easier to follow. Apparently, the firewall comments did not make
the transition and I was unaware of this until you just mentioned.

With regards to pinging: My tips have everything to do with resting the
network connection, which must be set up correctly for ping (or anything
else networking related) to work correctly.

You might be surprised that the people who ask for help here have the
ability to determine for themselves which solution will work for them. Heck,
they might as well try any solution anyone offers.

If someone follows my tips, which lately you seem to be on a campaign to
discourage, what possible harm will come to them?

Carey
 
G

Guest

I was advised by Dell that XP SP2 has problems with wireless networks and
that MS is working on the problem. Dell advised me not to upgrade to SP2
yet. My wireless
network works fine in SP1.
 
L

Lou Ramsey

WilburDav said:
I was advised by Dell that XP SP2 has problems with wireless networks and
that MS is working on the problem. Dell advised me not to upgrade to SP2
yet. My wireless
network works fine in SP1.
Click to expand...

I remain unimpressed by Microsoft testing / validation of SP2.

Example: I would sure love to know what the validation of Security
Center - Antivirus Status Check was like. How they could release
Security Center with "Norton Antivirus reports that it is installed, but
its status is unknown". One of the most common antivirus products.
1) They didn't test SC with NAV.
2) They didn't see the problem.
3) They didn't care about the problem.
Either of the three possibilities doesn't say much for their testing.
 
C

Carey Holzman

It has nothing to do with testing. It has to do with the abilities of the
A/V software. Simply go to LiveUpdate and the 2004 version of NAV will have
a WMI update waiting for you that will make it compatible with the security
center. If you're NAV is older than that, your security is more of a concern
than Microsofts.

The 2005 version of NAV has this 'WMI' feature already in it.

Because Symantec will not provide a WMI update to versions of NAV older than
2004 makes this Microsoft's problem?

That's a spin...
 
L

Lane

I figured out my problem. I have software firewalls on both computer that
are blocking it. When I disable them, I can ping eachother and share
everything. The weird thing is they just block it and I can't see it in
their security logs, neither do they ask me to allow or disallow it.

So my question is do you know what ports I should set in my firewall for
file and printer sharing?

Thanks a bunch guys.
Lane
 
C

Chuck

I figured out my problem. I have software firewalls on both computer that
are blocking it. When I disable them, I can ping eachother and share
everything. The weird thing is they just block it and I can't see it in
their security logs, neither do they ask me to allow or disallow it.

So my question is do you know what ports I should set in my firewall for
file and printer sharing?

Thanks a bunch guys.
Lane
Click to expand...

Lane,

Opening ports TCP 139, 445 and UDP 137, 138, 445 in a personal firewall should
enable file sharing.

If your PF provides for it, you should only open those ports for specific
addresses, or your local subnet. On a wireless LAN, you should use fixed ip
addresses, and open those ports for specific addresses only.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
L

Lane

Chuck,

Thanks for the info.

For specifying the ports, beside the protocol type, it asks for local and
remote ports.

I am not sure which ports should be local and which should be remote. Should
I specify all of them for both local and remote?

Thanks,
Lane
 
C

Chuck

Chuck,

Thanks for the info.

For specifying the ports, beside the protocol type, it asks for local and
remote ports.

I am not sure which ports should be local and which should be remote. Should
I specify all of them for both local and remote?

Thanks,
Lane
Click to expand...

Lane,

You open local ports to permit incoming traffic, and remote ports to permit
outgoing traffic. For file sharing, you need to permit traffic both ways.

What personal firewall blocks outgoing traffic? Not ICF. And with WF, you only
have to enable the FPS exception. Is this a third party PF?

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

File sharing problem (not working even with simple file sharing enabled) 3
Network Wizard stop responding 4
Wireless LAN 7
cannot ping and access from some pc in workgroup 3
Network (File Sharing) Problem 1
XP to Vista printer sharing 4
Removing Internet Connection Sharing 2
Configuring XP PRO for home LAN 2

Top