Re: Networking with Windows 2000 Professional Machines



I've tried the things you have suggested. However, I suspect that I am
having a problem with my Network Adaptor or its driver.
I actually can not run the ipconfig commands that you suggest as they have
no reponse from the command prompt. I also can not ping my own IP address -
Request Timed Out. Finally, when I go to the Device Manager and try to view
the Properties of the Intel(R) Pro 100 VE Network Connection, the Device
Manager freezes (permanent Hourglass). I've tried downloading the latest
driver from Dell but this did not fix the problems. Any thoughts would be
greatly appreciated!

"Dana Cline - MVP" wrote:

> You shouldn't need a host file on any machine, just make sure your TCP/IP
> drivers are configured to use a DHCP address. So if you have a hosts file,
> rename it to something else and reboot. On each PC, open a DOS window and
> run "ipconfig /release" and then "ipconfig /renew". Make sure each PC gets a
> good IP address from the router.
>
> At this point, with all PCs set to the same workgroup and having the same
> users/passwords, it should work. Make sure a directory is shared on each PC
> otherwise the network might not see that PC.
>
> Which router are you using?
>
> Dana Cline - MVP
>
> "Paul" <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:DFAF74AB-8342-4152-8CB8-7FF139BD5AAF@xxxxxxxxxxxxxxxx
> > I bought a new computer with XP Media Center Edition.
> > I've tried to share some files and printers with 2 other computers running
> > Windows 2000 Professional.
> > I ran the Network Setup Wizard on the new XP computer. I was unable to
> run
> > it on the other computers as it did not support Windows 2000.
> > I tried to manually configure the 2000 machines but have not been able to
> > get the networking to work.
> >
> > Steps I've taken:
> > Disabled the LAN firewall on the XP machine (all three machines are
> > connected to a router)
> > I've created the same workgroup on each machine.
> > Created the same account name and password on each machine.
> > Tried to update the hosts file on the machines, but may have done this
> > incorrectly as I haven't been able to get the IP address of the XP
> machine.
> >
> > Symptoms:
> > When I "View workgroup computers" on the XP machine I get <workgroup> is
> not
> > available. You might not have permission to use this network resource.
> > Contact the administrator of the server to find out if you have access
> > permissions.
> > When I search for one of the 2000 computer names, the computer is not
> found.
> > From the command prompt, I can ping the 2000 computer using the IP
> address.
> > However, I can't ping the computer using it's hostname, in fact, "ping
> > basement", "ping localhost", and even ipconfig all freeze the XP command
> > console.
> >
> > When I search for the XP computer "office" from the 2000 machine, it finds
> > it okay. However, when I try to access the computer, I get "network path
> not
> > found"
> >
> > I'm afraid I'm now doing more harm than good, so I'd appreciate any help I
> > could get.
>
>
>
.



Relevant Pages

  • Re: Frequent network access freeze (in 7.0)
    ... problem with the if_tx driver. ... The usual starting diagnostics when ping fails are to try to use tcpdump to determine whether it's receive or transmit failing. ... Quiet the network between two endpoints as much as you can so you can avoid noise from making the dumps more complex, and dump arp and icmp at both endpoints. ... This would be indicative of a driver bug in which it fails to properly handle transmit queues filling, and might only trigger under very high load. ...
    (freebsd-current)
  • Re: Frequent network access freeze (in 7.0)
    ... Network access freezes very frequently. ... ping to any ip address. ... problem with the if_tx driver. ... example) transmit queues ...
    (freebsd-current)
  • Re: Linux Firewall/LoadBalancer
    ... The bonding driver originally came from Donald Becker's beowulf patches for ... Build kernel with the bonding driver ... "Bonding driver support" in the "Network device support" section. ... so the bonding driver will automatically load when the bond0 interface is ...
    (Security-Basics)
  • Re: Configuring hostname, domainname, and IP address
    ... solved by tweaking the hosts file. ... Why the installation missed them, ... I'm sure that this one node network can be tweaked ... a ping will return that IP address. ...
    (comp.os.linux.networking)
  • Re: Configuring hostname, domainname, and IP address
    ... solved by tweaking the hosts file. ... Why the installation missed them, ... I'm sure that this one node network can be tweaked ... a ping will return that IP address. ...
    (linux.redhat.install)