Re: Network Connection Issue (File Sharing)

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Fred (FredFlinstone59_at_Yahoo.com)
Date: 09/23/04

  • Next message: Moses: "RE: Can't pick up DHCP"
    Date: Thu, 23 Sep 2004 13:31:31 -0700
    
    

    Chuck,

    Ok I deleted the IPv6 protocal from both computers (no,
    I wasn't using it - it just loaded with the lynksys
    wireless adapter on computer "B" so I loaded it on
    computer "A" hoping it would help).

    Here are the new IPCONFIG results from Computer "A":

    Windows IP Configuration

            Host Name . . . . . . . . . . . . : DaddyDesktop

            Primary Dns Suffix . . . . . . . :

            Node Type . . . . . . . . . . . . : Mixed

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

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

            DNS Suffix Search List. . . . . . :
    dalect01.va.comcast.net

    Ethernet adapter Local Area Connection 4:

            Connection-specific DNS Suffix . :
    dalect01.va.comcast.net

            Description . . . . . . . . . . . : Realtek
    RTL8169/8110 Family Gigabit Ethernet NIC

            Physical Address. . . . . . . . . : 00-50-8D-E7-
    34-A8

            Dhcp Enabled. . . . . . . . . . . : Yes

            Autoconfiguration Enabled . . . . : Yes

            IP Address. . . . . . . . . . . . : 192.168.2.2

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

            Default Gateway . . . . . . . . . : 192.168.2.1

            DHCP Server . . . . . . . . . . . : 192.168.2.1

            DNS Servers . . . . . . . . . . . : 192.168.2.1

            Lease Obtained. . . . . . . . . . : Thursday,
    September 23, 2004 3:55:43 PM

            Lease Expires . . . . . . . . . . : Thursday,
    October 07, 2004 3:55:43 PM

    Ethernet adapter {B9C1EFDB-ED75-4787-8A46-0C4C2F47FEFC}:

            Connection-specific DNS Suffix . :

            Description . . . . . . . . . . . : Nortel
    IPSECSHM Adapter - Eacfilt Miniport

            Physical Address. . . . . . . . . : 44-45-53-54-
    42-00

            Dhcp Enabled. . . . . . . . . . . : No

            IP Address. . . . . . . . . . . . : 0.0.0.0

            Subnet Mask . . . . . . . . . . . : 0.0.0.0

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

    Here are the new IPCONFIG results from computer "B"

    Windows IP Configuration

            Host Name . . . . . . . . . . . . : DONDESKTOP

            Primary Dns Suffix . . . . . . . :

            Node Type . . . . . . . . . . . . : Mixed

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

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

            DNS Suffix Search List. . . . . . :
    dalect01.va.comcast.net

    Ethernet adapter {B22110DC-E278-40A8-A8E6-04E95580447D}:

            Connection-specific DNS Suffix . :

            Description . . . . . . . . . . . : Nortel
    IPSECSHM Adapter

            Physical Address. . . . . . . . . : 44-45-53-54-
    42-00

            Dhcp Enabled. . . . . . . . . . . : No

            IP Address. . . . . . . . . . . . : 0.0.0.0

            Subnet Mask . . . . . . . . . . . : 0.0.0.0

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

    Ethernet adapter Wireless Network Connection 6:

            Connection-specific DNS Suffix . :
    dalect01.va.comcast.net

            Description . . . . . . . . . . . : Linksys
    Wireless-G PCI Adapter

            Physical Address. . . . . . . . . : 00-0F-66-6D-
    20-BE

            Dhcp Enabled. . . . . . . . . . . : Yes

            Autoconfiguration Enabled . . . . : Yes

            IP Address. . . . . . . . . . . . : 192.168.2.4

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

            Default Gateway . . . . . . . . . : 192.168.2.1

            DHCP Server . . . . . . . . . . . : 192.168.2.1

            DNS Servers . . . . . . . . . . . : 192.168.2.1

            Lease Obtained. . . . . . . . . . : Thursday,
    September 23, 2004 3:57:02 PM

            Lease Expires . . . . . . . . . . : Thursday,
    October 07, 2004 3:57:02 PM

    >-----Original Message-----
    >On Wed, 22 Sep 2004 15:36:12 -0700, "Fred"
    <FredFlinstone59@Yahoo.com> wrote:
    >
    >>Chuck,
    >>
    >>Ok, I ran what the IPCONFIG on both computers. Here
    are
    >>the results for Computer "A" (wired to the Router):
    >
    ><SNIP IPConfig showing IPV6 configured>
    >
    >>I got the following error when I tried to run the net
    >>view: "The list of servers for this workgroup is not
    >>currently available."
    >>
    >>I also found the following one error and one warning on
    >>this computer under "System" in Event Viewer:
    >>
    >>DCOM Error: The server {F3A614DC-ABE0-11D2-A441-
    >>00C04F795683} did not register with DCOM within the
    >>required timeout.
    >>
    >>Warning: The time service has not been able to
    >>synchronize the system time for 49152 seconds because
    >>none of the time providers has been able to provide a
    >>usable time stamp. The system clock is unsynchronized.
    >>
    >>Here are the IPCONFIG results for Computer "B"
    >>(Wirelessly connected to the router):
    >
    ><SNIP IPConfig showing IPV6 configured>
    >
    >>I got the same error on computer "B" when I tried to
    run
    >>the net view: "The list of servers for this workgroup
    is
    >>not currently avaiable."
    >>
    >>I also had the following erro in "System" under Event
    >>Viewer on Computer "B":
    >>
    >>DCOM Error: The application-specific permission
    settings
    >>do not grant Local Launch permission for the COM Server
    >>application with CLSID
    >>{D851F103-8C90-4321-AFF0-58BA5BD421C2}
    >> to the user NT AUTHORITY\SYSTEM SID (S-1-5-18). This
    >>security permission can be modified using the Component
    >>Services administrative tool.
    >>
    >>I look in Administrative Tools under "Services and did
    >>not that "Server" and "Workstation" for both computers
    is
    >>started and set for automatic. I also noted that there
    >>is no TCP/IP filtering set for either network device.
    >
    >Fred,
    >
    >The first thing you need to do is get rid of IPV6 on
    both computers. Reboot
    >after un install. Then rerun "ipconfig /all
    >c:\ipconfig.txt" and repost with
    >new ipconfig.txt files.
    >
    >Are you actually accessing websites in the IPV6 address
    space? If so, we'll
    >figure out how to get IPV6 working, properly, after you
    get (IPV4) file sharing
    >working.
    >
    >Cheers,
    >Chuck
    >Paranoia comes from experience - and is not necessarily
    a bad thing.
    >.
    >


  • Next message: Moses: "RE: Can't pick up DHCP"

    Relevant Pages

    • Re: Ipv6 private network - ipv4 public network
      ... network with ipv6 ip adresses and a public internet network with ipv4 ... our ISP gives us 5 internet ip adresses. ... So the 5 computers all get an own internet ip adress. ... if I tell the router to make an ipv6 connection with the ...
      (microsoft.public.windowsxp.network_web)
    • IPv6 with IPsec on FreeBSD 4.10-R with racoon-20040408a
      ... I came across a problem with IPv6 and IPsec. ... I have two computers in my network, ... The policy rules on computer B corresponds to the ones above. ...
      (freebsd-questions)
    • Re: Ipv6 private network - ipv4 public network
      ... network with ipv6 ip adresses and a public internet network with ipv4 ... our ISP gives us 5 internet ip adresses. ... So the 5 computers all get an own internet ip adress. ... if I tell the router to make an ipv6 connection with the ...
      (microsoft.public.windowsxp.network_web)
    • Re: Ipv6 private network - ipv4 public network
      ... network with ipv6 ip adresses and a public internet network with ipv4 ... our ISP gives us 5 internet ip adresses. ... So the 5 computers all get an own internet ip adress. ... if I tell the router to make an ipv6 connection with the ...
      (microsoft.public.windowsxp.network_web)
    • Re: Programmatically setting static IPv6 address in Winodws CE
      ... The registry keys for IPv6 ... Set the registry settings and rebind the network adapter. ...
      (microsoft.public.windowsce.embedded)