Re: Network Connection Problem - Intermittent

Bob,

Definately not ICS/ICF, the Workgroups names are the same and there are no XP computers on the network.

I looked in the Event Log and found a few of these events around the time of the problem:

Log Name: System
Source: netbt
Event ID: 4321

The name "XXX :1d" could not be registered on the interface with IP address 192.168.1.105. The computer with the IP address 192.168.1.111 did not allow the name to be claimed by this computer.

XXX is my Group Name
192.168.1.105 is XPS-710
192.168.1.111 is Laptop-PC


Anything else I should look for?

Thanks,
John



"Robert L. (MS-MVP)" <findemail@xxxxxxxxxxxxxxx> wrote in message news:uyjsUKsiJHA.1288@xxxxxxxxxxxxxxxxxxxxxxx
Any errors in the event viewer? Or this search result may help.
System Errors
2) If you use the net view command, you may receive "System error 6118 has occurred. The list of servers for this workgroup is not currently available. ...
www.chicagotech.net/systemerrors.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"John" <noemail@xxxxxxxx> wrote in message news:eBucmlriJHA.3656@xxxxxxxxxxxxxxxxxxxxxxx
I have 3 computers on a private home network. Here is my current setup:



XPS-710

- Vista Ultimate

- McAfee Security Center



SERVER

- Vista Home Premium

- Zone Alarm



LAPTOP-PC

- Vista Business

- Norton AV 2009

- Zone Alarm



This information is common for all systems:

- Private Network

- Same Workgroup

- Network Discovery: ON

- File Sharing: ON

- Public Folder Sharing: ON

- Password protected sharing: OFF



I am able to connect to all systems from all other systems without a problem.



Occasionally, a problem occurs and I am not able to access SERVER from XPS-710. When this problem occurs, I am able to ping SERVER from a CMD prompt both by name and IP address, but I am not able to access any files.



This time, I tried a NET VIEW from XPS-710 and received the following:



C:\Users\John>net view

System error 6118 has occurred.



The list of servers for this workgroup is not currently available



C:\Users\John>ipconfig /all



Windows IP Configuration



Host Name . . . . . . . . . . . . : XPS-710

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : hsd1.nj.comcast.net.



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : hsd1.nj.comcast.net.

Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller

Physical Address. . . . . . . . . : 00-19-B9-3F-10-5A

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::c0c2:a31d:7ad:a33a%9(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.1.105(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Lease Obtained. . . . . . . . . . : Friday, February 06, 2009 6:15:10 PM

Lease Expires . . . . . . . . . . : Tuesday, February 10, 2009 6:15:09 AM

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 68.87.64.146

68.87.75.194

68.87.71.226

NetBIOS over Tcpip. . . . . . . . : Enabled



Tunnel adapter Local Area Connection* 6:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 02-00-54-55-4E-01

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes



Tunnel adapter Local Area Connection* 7:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . : hsd1.nj.comcast.net.

Description . . . . . . . . . . . : isatap.hsd1.nj.comcast.net.

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes









Five minutes later, I was able to access SERVER from XPS-71- without a problem.



C:\Users\John>net view

Server Name Remark



-------------------------------------------------------------------------------

\\LAPTOP-PC

\\SERVER

\\XPS-710

The command completed successfully.







The only thing I did was to re-boot LAPTOP-PC. I am not sure why that would have had an effect.



Any suggestions on what I should try the next time the problem occurs?



Thanks,

John







.

Relevant Pages

  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ...
    (microsoft.public.win2000.networking)
  • Re: Single NIC configuration with cable modem/router
    ... Internal or single network adapter configuration ... Verify the Domain Name System (DNS) pointers. ... Right-click Server Local Area Connection, ...
    (microsoft.public.windows.server.sbs)
  • Re: Network Connection Problem - Intermittent
    ... Master browser name is: SERVER ... This may occur if the workgroup name and the domain name are the different. ... Starting Computer Browser Service on one of w2k/xp computers should fix the problem. ... How to Setup Windows, Network, VPN & Remote Access on ...
    (microsoft.public.windows.vista.networking_sharing)
  • Re: SBS 2003 Shutdown Automatically?
    ... I am by no means a domain/server whizz but I have set up SBS 2003 for 5 of my clients and they all think I'm a genius! ... workgroup network to an SBS domain network. ... If you wanted workgroup then perhaps plain Windows 2003 Server would have been a better choice. ...
    (microsoft.public.windows.server.sbs)