Re: Need Help with Browser/Name Resolution Problem

In article <B10387C9-5530-4969-96EB-C6BB3E27EF13@xxxxxxxxxxxxx>,
Charlie Pyeatte <story@xxxxxxxxxxxxxxxxxxx> wrote:
>I have a 2-computer network (machines are identical) using Windows XP Home
>SP2 and connected by a crossover cable. Their names are FRED and WILMA. The
>workgroup is STUDYNET. I have confirmed physical connectivity by testing
>each comp (and the cable) using a Windows 98 laptop. Some time ago, I tried
>to disable ICS and lost network connections. Most recently, I deleted the NIC
>and all protocols and ran the setup wizard again on both machines,
>identifying them as being part of a network with no Internet connection.
>
>They did not connect. I could not ping either comp by name or IP address.
>Each could ping itself. Both comps increased their time to boot up by about
>4x.
>
>I looked at the Windows firewall and saw that WILMA had some features that
>FRED did not: Peer Name Resolution Protocol (opening UDP port 3540) and
>Windows Peer-to-Peer Grouping (opening TCP port 3587). I set Fred to have
>the same features. That didn?t change the lack of connections. I then
>disabled the firewall on the local connection of both comps. They still do
>not connect.
>
>I enabled Net BIOS over TCP/IP on both, but no change occurred. I ran
>browstat and saw that both were master browsers. I disabled the browsing
>service on WILMA. They still could not ping each other. Both sides would
>time out. In Workgroup view, FRED sees only FRED. WILMA returns the error
>message: ?STUDYNET is not accessible. You might not have permission to use
>this network resource. The network path was not found.?
>
>I can see that there is a name resolution/browser problem, but for all the
>reading I?ve done on this forum, I don?t know what to do next. Three points
>that might matter:
> (1) The store that built our computers gave them both the name ?Ch? which
>is displayed with the Windows OEM serial number.
>(2) I had to restore Windows on FRED at one point and used WILMA?s backup
>record to do it, later changing the computer name to FRED. I ran Registry
>Mechanic to clean up both comps.
>(3) There may be remnants of the Windows 98 computer name in the registry.
>
>Here are the current reports on browstat and ipconfig for each, beginning
>with FRED:
>
>Status for domain STUDYNET on transport
>\Device\NetBT_Tcpip_{A1253276-EAD1-42D1-A9E9-3DD99B800697}
> Browsing is active on domain.
> Master browser name is: FRED
> Master browser is running build 2600
> 1 backup servers retrieved from master FRED
> \\FRED
> There are 1 servers in domain STUDYNET on transport
>\Device\NetBT_Tcpip_{A1253276-EAD1-42D1-A9E9-3DD99B800697}
> There are 1 domains in domain STUDYNET on transport
>\Device\NetBT_Tcpip_{A1253276-EAD1-42D1-A9E9-3DD99B800697}
>
> Windows IP Configuration
>Host Name . . . . . . . . . . . . : FRED
>Primary Dns Suffix . . . . . . . :
>Node Type . . . . . . . . . . . . : Mixed
>IP Routing Enabled. . . . . . . . : No
>WINS Proxy Enabled. . . . . . . . : No
>
>Ethernet adapter Local Area Connection:
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
>
>Physical Address. . . . . . . . . : 00-0B-6A-EE-4A-E6
>Dhcp Enabled. . . . . . . . . . . : Yes
>Autoconfiguration Enabled . . . . : Yes
>Autoconfiguration IP Address. . . : 169.254.107.156
>Subnet Mask . . . . . . . . . . . : 255.255.0.0
>Default Gateway . . . . . . . . . :
>
>WILMA:
>
>Status for domain STUDYNET on transport
>\Device\NetBT_Tcpip_{964D1183-85C6-4B4B-A144-B96EB9640719}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>
>Windows IP Configuration
> Host Name . . . . . . . . . . . . : WILMA
>Primary Dns Suffix . . . . . . . :
>Node Type . . . . . . . . . . . . : Mixed
>IP Routing Enabled. . . . . . . . : No
>WINS Proxy Enabled. . . . . . . . : No
>
>Ethernet adapter Local Area Connection :
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
>
>Physical Address. . . . . . . . . : 00-0B-6A-EF-6D-04
>Dhcp Enabled. . . . . . . . . . . : Yes
>Autoconfiguration Enabled . . . . : Yes
>Autoconfiguration IP Address. . . : 169.254.183.111
>Subnet Mask . . . . . . . . . . . : 255.255.0.0
>Default Gateway . . . . . . . . . :

You have to solve the ping problem first. High-level networking
functions (browsing, file sharing, workgroups, NetBIOS, etc) can't
work until the computers can ping themselves and each other by IP
address and by computer name.

I don't know what registry cleanup and restoring you did, but it might
have damaged the entries for TCP/IP. Run this command on each
computer to repair TCP/IP, then reboot:

netsh winsock reset catalog

Turn off the Windows Firewall. Un-install all other firewall programs
(Norton, McAfee, PC-cillin, ZoneAlarm, etc). Don't just disable them.
Un-install them. Note that some antivirus programs include firewall
features that must be configured to allow access on the local area
network -- for example Norton Antivirus 2006 has "Internet Worm"
protection.

Since there's no DHCP server on your network, your computers are
assigning themselves automatic private IP addresses in the 169.254.x.x
range. Those addresses could change from one boot to the next.
Consider assigning them static IP addresses in the ranges reserved for
private networks by the Internet Assigned Numbers Authority:

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

Examples of pairs of private network addresses are:

10.0.0.1 and 10.0.0.2, subnet mask 255.0.0.0
172.16.0.1 and 172.16.0.2, subnet mask 255.240.0.0
192.168.0.1 and 192.168.0.2, subnet mask 255.255.255.0
--
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
.

Relevant Pages

  • Serious Security Issue in Windows XP SP2s Firewall
    ... PC-WELT discovers and fixes serious security issue in Windows XP SP2 ... Internet via dial-up or ISDN. ... Internet Connection Sharing of the PC ... network at home: Often, we did not even encounter password protection. ...
    (Bugtraq)
  • Re: Big hole??
    ... supposedly safe SP2 for Windows XP invites any Internet ... Connection Sharing of the PC has to be disabled. ... visible in their network at home: ...
    (microsoft.public.windowsxp.general)
  • Re: Still cant connect to RWW or OWA remotely
    ... another program or service is running that might use the network address ... This sounds like a Windows Firewall problem. ... match the broadband connection, the two NIC firewall, the remote ...
    (microsoft.public.windows.server.sbs)
  • Re: Using two network connections - by application
    ... Windows can route traffic by application / ... Then go to Windows Firewall settings Advanced tab, click settings on Network ... Connection Settings for each spefic network adapter that accesses the ... allow or disallow unsolicited incoming connection requests from the ...
    (microsoft.public.windowsxp.network_web)
  • Re: Tried everything, whats next?
    ... I looked at both desktop computers, ... They are named FRED and WILMA. ... The network worked fine ... >>Ethernet adapter local area connection: ...
    (microsoft.public.windowsxp.network_web)