Unsolved
This post is more than 5 years old
2 Posts
0
4276
December 23rd, 2003 14:00
Microsoft Network on XP Pro not working
I am baffled by a problem I am having on my new Dimension 8300.
I have a D-Link router. I have two laptops running Win2k and the Dimension 8300 running XP Pro connected to the router.
All 3 machines have the same workgroup - 3SI
Each machine has a unique name.
The D8300 connects fine to the Internet. It can ping other machines on my LAN. It can also ping the loopback. However it can't ping its own DHCP assigned IP address.
When I try and browse the workgroup -- it times out with "3si is not accessible. ... The list of servers for this workgroup is not currently available". Related, when I do "net view \\machines_ip_addr" -- I get "System error 53 ... the network path was not found"
I have run the home network wizard several times. All of the properties associated with the NIC (Intel Pro/100 VE) seem correct. I have TCP/IP, File and Printer Sharing, and Microsoft Client for Microsoft Networks. (I have tried with/without the Net Firewall Service).
This is frustrating. I have never seen a machine that could ping other IP addresses but couldn't ping itself. (It does resolve its IP address ok). So "ping 3SIDESK" tries to connect to 192.168.0.104 -- but that times out.
I have updated the driver for the NIC. That didn't change things either.
Anyone seen this with XP Pro? Dimensions? Anything else?
This is preventing me from sharing printer and files. It also impacts a VPN client of mine from being able to support traffic through the established IP SEC connection.
Gary
jmwills
2 Intern
•
12K Posts
0
December 23rd, 2003 15:00
Thanks up front for a detailed and concise statment of the problem. On the 8300 machine, under
Advanced TCP/IP properties, under the WINS tab, is Enable NetBios over TCP/IP checked? If not, do so.
I just put a 8300 on line this past week and it was a snap to get going. Specs are below.
Dimension 8300 with Windows XP Pro (SP1a) -Intel P4 3.0 Ghz-1024mb PC2100 RAM - Disk 0: 80Gb Maxtor HDD (7200 RPM) - Disk 1: 80Gb HDD (7200 RPM) Samsung DVD 16x IDE -Sony DRU-510A DVD-/DVD+ DVDRW - Iomega ZIP 100 USB Drive -Dell 18" Ultra Sharp Flat Panel - nVidia GeForce 5200 AGP 8x(128mb RAM) -Intel Pro/100 Internal NIC- HP LaserJet 5L -Linksys BEFCMU10 Modem- Linksys BEFSR41 Router - Linksys BEFW11S4 Router configured as Access Point
Power Edge 600SC with MS Server 2003 - P4 2.4Ghz - 384mb Ram - Disk 0: 40Gb Maxtor HDD (7200 RPM) - 48x CD ROM - Intel Pro 1000 Gigabit NIC
A+ Network+ Certified Microsoft Partner
glcraig
2 Posts
0
December 23rd, 2003 18:00
Thanks for the suggestion. I had gone to the Microsoft Knowledge base and found the same suggestion.
Unfortunately that didn't change things.
The most perplexing behavior is the inability to ping 192.168.0.104 (self). This should be raw TCP/IP behavior not Client for Microsoft Network. Particularly when ping 192.168.0.100 (another machine on the LAN) works fine.
Gary
jmwills
2 Intern
•
12K Posts
0
December 23rd, 2003 19:00
What protocols are installed for this adapter? The only ones you need are:
Anything else is not need needed for the basic home user.
robnalex
2 Intern
•
720 Posts
0
December 24th, 2003 00:00
Check the following:
Be sure the Windows firewall is diabled on the XP computer.
If you are using a software firewall, be sure to configure the network in the firewall software.
This site has good directions for setting up a network (XP):
http://www.homenethelp.com/web/howto/net.asp