MVPs Please!

[GO]

It can take up to 24-48 hrs before
someone will post an answer to you.

Exactly! And on top of that sometimes it can take that long for messages
to appear. This group (as the other MS usenet groups) is also "hosted" on
other Usenet servers throughout the world, and on occasion there can be some
very lengthy replication delays.

 

[Gerry]

Um. I have seen fish chasing their tail before <G>. Are you an e-nibbler
what ever that may be or a t-nibbler. Any chance it's someone who posts
to themself?


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Robert Moir]

maybe people think of this
newsgroup like a mickey D's:

"Hello...?, I gotz a networking problem and
i need a mac value professional NOW...!"

"and dont forget the apple pie..!"

mmmm... pie

 

[Ken Blake, MVP]

Ken, you too have been a BIG help to me over the years.

Glad to hear it, and thanks for the kind words.

The post did not
say MVPs only...it said MVPs.

OK, but my point, and I think Shenan's too, is that your subject line
is likely to turn off others who might have been able to help.

I saw you guys skipping over it.

I don't recall the question at this point, but if I skipped over it, I
probably didn't have an answer for you. None of us knows everything.

 

[mcp6453]

I've taken the thread to microsoft.public.windowsxp.network_web, as I
was chastised to do, but here are the answers to your questions:


Absolutely nothing of any help. No errors, no nothing.


Path not found.


Server cannot be found.


Some machines are DHCP, some are static. I have not been to each machine
to do an ipconfig /all. The problem is only happening with one machine.
The only difference is that the one XP machine cannot connect to the
share drives or folders on other machines using UNC. All machines are
using the same DNS, and all machines are in the same subnet.


Yes, verified twice.


Server is XP Pro. Problem machine is XP Pro. Server is accessible from
other XP Pro and Win2K machines with no problem.


XP Pro. All computers are completely patched, no viruses, no spyware.


Yes, multiple times. I have also tried LSPFix.exe. It did not report a
problem with the winsock. I also removed and reinstalled Client for
Microsoft Windows, File and printer sharing, and TCP/IP.


I tried netsh, netdiag, msinfo32, and several other utilities, but I
cannot see the problem.


Yes, I went through that article in detail before I made my first post.


No, it is not.

Thanks

In case anyone is still reading, the problem turned out to be an IP
address conflict. I cannot explain why it was happening. Several
machines on the network are DHCP. It makes no sense to me why the ZyXEL
router would hand out the same IP address to more than one computer, but
that's okay. The machine has now been set to static, and it's cooking.

Sorry for all the newsgroup noise.

 

[Shenan Stanley]

In case anyone is still reading, the problem turned out to be an IP
address conflict. I cannot explain why it was happening. Several
machines on the network are DHCP. It makes no sense to me why the
ZyXEL router would hand out the same IP address to more than one
computer, but that's okay. The machine has now been set to static,
and it's cooking.
Sorry for all the newsgroup noise.

Was that discovered by doing an IPCONFIG /all on all of the machines?

 

[Leythos]

In case anyone is still reading, the problem turned out to be an IP
address conflict. I cannot explain why it was happening. Several
machines on the network are DHCP. It makes no sense to me why the ZyXEL
router would hand out the same IP address to more than one computer, but
that's okay. The machine has now been set to static, and it's cooking.

Many of those cheap units will reset their DHCP table, so that they
don't know what addresses have been handed out.

If you are giving your FIXED IP computers an address in your DHCP scope,
then you're making a mistake. The Fixed IP computers should not be in
the DHCP range provided by the firewall.

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
(e-mail address removed) (remove 999 for proper email address)