Re: Long delay to find the other computer on network

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance




"Chuck" <none@xxxxxxxxxxx> wrote in message
news:rqsoo1pnml4ajuf3s8ujcfj88lb7djae7s@xxxxxxxxxx
> On Tue, 29 Nov 2005 07:18:30 -0500, "BP" <*email_address_deleted*> wrote:
>
>>I have a simple 2 computer home network set up with a crossover cable. The
>>serving machine runs XP-SP2 and the client runs W98SE. The XP server had
>>an
>>on-board Gigabit LAN controller (Asus P4C800-E) that was connected to the
>>cable modem and a Linksys NIC to connect to the LAN. At one time
>>everything
>>worked perfectly, very fast, and no burps, beeps, or delays. Then my
>>server's mainboard died. A new (Intel) mainboard was installed and a
>>repair
>>install of XP was performed. The new board does not have built in Gigabit
>>LAN, so a 3-Com NIC was added and connects to the modem. The same Linksys
>>NIC connectsto the LAN. After the system was back up and running there
>>were
>>a *lot* of bugs in the works. One was that the network connection could
>>not
>>be re-established. After much research I was able to find and delete
>>phantom
>>devices from the system, including the phantom Gigabit LAN controller and
>>gain access to the network connection. But only by changing the setting
>>under TCP/IP properties from "Obtain IP address automatically" and
>>manually assign address 192.168.0.1 (and the 255 subnet mask). By default
>>the "Use the following DNS server address" option is selected, but I left
>>this blank. Now the network works, but it is very slow to find the W98
>>computer in both Network Neighborhood and in Windows Explorer. The
>>hourglass
>>shows for 30 to 60 seconds before the files on W98 show up. Same with the
>>shared printer connected to the W98. Sometimes it won't even show at all
>>(grayed out). But, going the other way (from the W98 computer) everything
>>is
>>just like before: no delay, very fast. Shared printers on the XP machine
>>work great. ICS works great. And, once the XP does find the W98,
>>transferring files, data, and print jobs goes normally, no delays. It is
>>only *finding* the W98 computer on the network that goes slow.
>>I have lived with this setup like this for several months now. It works,
>>but
>>it's just annoying as all hell. Every now and then I see a post or webpage
>>that seems to relate to my problem and I try the fix suggested, make the
>>setting changes, edit the registry, hang garlic from the monitor, but no
>>solution. I've tried a *lot* of things, all the usual suspects,
>>so please bear with me if you offer stuff I've done before. This also
>>means
>>that a lot of original settings, files, and the printer's driver have been
>>changed, reinstalled, or deleted. I know the ultimate solution is to clean
>>install XP, but I wonder if anyone knows a less painful fix. Please let me
>>know if you need any more info, I'm attempting to keep this long story
>>short.
>
> First, make sure that you have only NetBIOS Over TCP/IP, and TCP/IP,
> installed
> as protocols. Extra protocols like IPX/SPX and NetBEUI will cause this
> problem.
> <http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>

Got that covered

> Next, look at the browser (no, I'm not talking about Internet Explorer)
> situation. When you combine Windows 98 and XP on the network, this is a
> problem.
> <http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
> http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

This I haven't seen. I will give that a try (time permitting) and post back.
Hadn't seen your site before either. Looks good. I'll read more.

Thanks

>
> --
> Cheers,
> Chuck, MS-MVP [Windows - Networking]
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem, when it's a normal response from experience.
> My email is AT DOT
> actual address pchuck mvps org.

http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
Got that covered

http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html
This I haven't seen. I will give that a try (time permitting) and post back.
Hadn't seen your site before either. Looks good. I'll read more.

Thanks



.



Relevant Pages

  • Re: Windows 98 wont connect w/ XP printer on network; file sharing OK
    ... shared name matches W98 setting ... I ran the Windows XP Network Setup Wizard on Computer 1 ... Norten firewall is off, Windows ... >Windows XP and all sorts of bad things could happen if I install it. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Kaseya
    ... network and referencing the results to it's database of PCs that it's ... The Kaseya server feedback's not mandatory but once it's given, ... that has rights to install software on the machine. ... a "probe" equipment at the remote LAN. ...
    (Pen-Test)
  • Re: DHCP Breaks XP Network Printing
    ... So first you will need to add the W98 PC back to ... Reinstall W98 driver/software for that Printer. ... have a choose to install printer as a local or network printer. ...
    (microsoft.public.windowsxp.network_web)
  • Re: DHCP Breaks XP Network Printing
    ... Neil ... So first you will need to add the W98 PC back ... > have a choose to install printer as a local or network printer. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Changing a company from 100% Windows to 100% FreeBSD.
    ... >> install. ... >> recommend running it on the network or if it would be better to ... Although the LAN is ... >> installworld to upgrade, too. ...
    (freebsd-questions)