A trend with XP networking problems

  • Thread starter Thread starter Chris
  • Start date Start date
C

Chris

After many hours of reading message after message of XP
networking problems, I am thinking there are serious
problems with XP itself. Every time someone suggests the
fixes, they are all the same (disable firewall, use
NETBUI, set IP adresses, etc.) and even though most
people are taking these steps or have already done these
steps, it still doesn't fix the problem.

I've also noticed that after one of the many "techies"
answers a call for help and suggests the above fixes, and
they still don't work, they never answer that person
again. And the people who need the help never come back
and say "Hey, it worked ... thanks!"

For those of us who can't get their XP machines to
network with Win2000 or other XP machines, regardless of
all of the fixes that have been suggested over and over
again, what is the next step?
 
"Chris" said:
After many hours of reading message after message of XP
networking problems, I am thinking there are serious
problems with XP itself. Every time someone suggests the
fixes, they are all the same (disable firewall, use
NETBUI, set IP adresses, etc.) and even though most
people are taking these steps or have already done these
steps, it still doesn't fix the problem.

I've also noticed that after one of the many "techies"
answers a call for help and suggests the above fixes, and
they still don't work, they never answer that person
again. And the people who need the help never come back
and say "Hey, it worked ... thanks!"

For those of us who can't get their XP machines to
network with Win2000 or other XP machines, regardless of
all of the fixes that have been suggested over and over
again, what is the next step?
Click to expand...

I hope that you meant NetBIOS, not NetBEUI. NetBEUI is an
un-supported protocol in Windows XP, which means that Microsoft:

a. Hasn't tested it extensively.
b. Recommends against using it.
c. Won't give technical support on it.

In my experience, these steps solve the vast majority of Windows XP
networking problems:

1. Un-install (don't just disable) all firewall programs on all
computers while troubleshooting.

2. Run XP's Network Setup Wizard, being sure to specify the right
answer to its somewhat confusing question about how the computer
connects to the Internet. The Wizard calls a broadband router a
"residential gateway". If you specify the "hub" option, it will block
file and printer sharing.

3. Permanently disable XP's Internet Connection Firewall on the local
area network connection. ICF is designed for use only on a direct
modem connection to the Internet. If you have a broadband router, you
don't have a direct modem connection.

4.. Make sure that NetBIOS over TCP/IP is enabled (not default) on all
computers.

5. Use the same, single protocol for file and printer sharing on all
computers. Installing a second protocol on even one computer can
disrupt the entire network.

6. If there's a DHCP server on the network (broadband router or ICS
host), DON'T assign static IP addresses. Configure the computers to
obtain an IP address automatically.

If all that doesn't help, run these tests on each computer and report
the results:

1. Make sure they have IP addresses in the same subnet.

2. Ping itself and the other computer by IP address and by computer
name.

3. If #2 succeeds, try to access itself and the other computer by
typing these entries in the Start | Run box:

\\ip-address
\\computer-name
--
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
 
Steve,

How will using DHCP from the router work with a multihomed
server? I'm having possible DNS issues that cause my XP
Pro workstation to lose its connection to the domain
controller. I've read that the adapter on the DC should
point to itself as the primary DNS server in the TCP/IP
settings, but how can this be done if ip addresses are
dynamic?

We have 1 w2k server, 2 w2k pro workstations that work
FINE, and a new XP Pro workstation that works sometimes,
but loses its connection to the DC. I have static ip
addressing now, and ran the tests you suggest at the end
of your post.

I can perform 1, 2 and 3 successfully from the server and
w2k Pro machines to all other machines, including the XP
Pro, perfectly

I can perform 1 and 2 successfully from XP Pro to all
other machines. I can only perform 3 to computer name
from XP Pro to itself and server, not the other 2
workstations. I cannot perform 3 via ip addresses to ANY
computers!

Your help is appreciated.
-----Original Message-----
Click to expand...
 
I am having exactly the same problem as yourself chris
and it all really started after installing SP1 and any
other critical updates.. now I have to move files to one
of my 2k machines to then move them to my server because
my XP pro machine just hangs... and to think companies
are putting XP on their desktops.. I am not anti
microsoft but I am getting tired of having to format and
reinstall then update to find when first installed
everything works do the update's it all fails all with
out having any other software installed......whats the
point
 
Back
Top