1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Single Vista machine connected to DSL modem getting conflict with another computer claiming to be ma

Discussion in 'General Malware And Security' started by Nubie, Mar 10, 2008.

Page 2 of 2
  1. Nubie

    Nubie Guest

    I just forwarded the details of this incident to them. According to AT&T
    (sbcglobal.net) It will take up to 24 hours for them to get back to me. I
    will keep the group posted on this thread.



    "Bob F." <bob@NOSPAN.com> wrote in message
    news:F30FEC29-A851-4DE9-89E8-8C31842B0A95@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > What did your ISP say?
    >
    > --
    > BobF.
    > "Nubie" <newsgoup_contact@atigen.com> wrote in message
    > news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> 0016D3A2E7AD is my machines regular (wire) network card. The wireless
    >> card is disabled in device manager (which presumably rules any wireles
    >> connection out). 68.127.186.255 is AT&T's network, which is my ISP (ARIN
    >> lookup below):
    >>
    >> AT&T Internet Services SBCIS-SIS80 (NET-68-120-0-0-1)
    >> 68.120.0.0 - 68.127.255.255
    >> bras4.pltnca SBC068127176000040211 (NET-68-127-176-0-1)
    >> 68.127.176.0 - 68.127.191.255
    >>
    >> The constantly repeating reconnection notices at 5 minute intervals,
    >> (with resulting successfully assigned IP addresses), is probably a result
    >> of the fact that I remove the ethernet cable from my network card
    >> whenever I step away from my machine.
    >>
    >> The only other remotely possible connection to my PC would have been
    >> bluetooth, however the wireless card which provides bluetooth
    >> connectivity is always turned off (at the switch).
    >>
    >> This leaves 2 questions
    >>
    >> 1) How could there be a master browser called JAYS showing up on my logs
    >> (given the above).
    >>
    >> and (less importantly)
    >>
    >> 2) Why is my machine having a conversation with the outside world (my
    >> ISP) about its workgroup. My understanding was that a workgroup would be
    >> something that would be limited to my LAN alone.
    >>
    >>
    >>
    >>
    >> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >> news:6AD5B7D8-0DFF-4421-8DF9-3FF57637594C@microsoft.com...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> The anomalous name being in the router was only a suggestion, it's an
    >>> option in mine that could also be in yours. As far as not finding the
    >>> LAN DHCP server in the netbios table, this ....
    >>>
    >>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None The
    >>> IP
    >>>>>> address lease 192.168.1.64 for the Network Card with network address
    >>>>>> 0016D3A2E7AD has been denied by the DHCP server 192.168.0.1 (The DHCP
    >>>>>> Server sent a DHCPNACK message).
    >>>
    >>> says that it exists, at least some of the time, and that your computer
    >>> tried to use it with an incorrect network address and got booted. This
    >>> on the other hand....
    >>>
    >>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>>> could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>
    >>> says your computer subsequently tried to connect to a server on the
    >>> internet, probably your ISP, possibly somewhere else. There's no
    >>> indication here whether it is the same network adapter making the
    >>> connection as the one above but we can see from the text that your
    >>> network adapter in this case also "somehow" had some incorrect
    >>> information set in its configuration at the time.
    >>>
    >>> OTOH these constantly repeating reconnection notices at 5 minute
    >>> intervals....
    >>>
    >>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>
    >>> Are very much like what you can see happening with wireless connections.
    >>> If I were going to make a guess as to what is going on here I'd say that
    >>> apart from the ethernet adapter you connect to your own modem with you
    >>> do have a wireless adapter in that computer, it is always turned on and
    >>> it is set to automatically connect to any available network. Every so
    >>> often your PC is piggybacking a ride, or trying to, on poor JAYS
    >>> wireless network. :)
    >>>
    >>>
    >>>
    >>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>> news:OUZ0QCKhIHA.4740@TK2MSFTNGP05.phx.gbl...
    >>>>
    >>>> If JAYS were the name of the modem or in its netbios table, then it
    >>>> should still be there presumably. (I have not reconfigured the modem
    >>>> in several months, and at that I time I set it to factory defaults - so
    >>>> the name JAYS should not be assigned to the modem).
    >>>>
    >>>> I checked the mode that the modem is operating. This is as follows:
    >>>>
    >>>> PPP is on the modem. (PPP session is initiated from the modem.) - i.e.
    >>>> Not operating in Bridging mode
    >>>>
    >>>> I believe my DHCP server is assigned by the gateway, when I connect
    >>>> (i.e. no static IP configured on my machine).
    >>>>
    >>>> I did a lookup of the netbios name table on my PC which I listed below
    >>>> (When I tried nbtstat -a 192.168.0.1 for the modem I got "host not
    >>>> found").
    >>>>
    >>>>
    >>>> NetBIOS Local Name Table
    >>>>
    >>>> Name Type Status
    >>>> ---------------------------------------------
    >>>> MYPC <00> UNIQUE Registered
    >>>> WORKGROUP <00> GROUP Registered
    >>>> MYPC <20> UNIQUE Registered
    >>>> WORKGROUP <1E> GROUP Registered
    >>>> WORKGROUP <1D> UNIQUE Registered
    >>>> ..__MSBROWSE__. <01> GROUP Registered
    >>>>
    >>>>
    >>>>
    >>>>
    >>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>> news:EBF529EE-1C6A-4D4F-BB48-82EA200A86A9@microsoft.com...
    >>>>> It looks like your network connection may be misconfigured. From the
    >>>>> events at timestamp 10:01 and later it appears you have two
    >>>>> conflicting DHCP services being used. You have a DHCP server at
    >>>>> 192.168.0.1 which I presume is the DSL Modem with routing
    >>>>> capabilities enabled. You are also trying to get a DHCP address
    >>>>> directly from your ISP, probably using IP 68.127.186.255 as the DHCP
    >>>>> server address. You should use only one or the other. I'd try turning
    >>>>> off DHCP in the modem first and see how that works out.
    >>>>>
    >>>>> The modem can probably be configured in several different operating
    >>>>> modes. I have no way of knowing what your available options are or
    >>>>> which mode has been enabled. My own has 4 distinct DSL operating modes
    >>>>> plus various combinations of routing and firewall features. IOW, there
    >>>>> are umpteen ways to screw up the connection. :)
    >>>>>
    >>>>> Typically there are two common connection modes that might be used.
    >>>>> One way is to have the modem set in 'bridge" mode, where it only makes
    >>>>> the hardware connection to the DSL carrier signal. You would Windows
    >>>>> built in PPPOE "dialer" to log into your ISP from your computer. In
    >>>>> this configuration the ISP's DHCP server would give your computer an
    >>>>> internet IP ... i.e.. 68.127.186.115. You would need to set up your
    >>>>> ISP username and password in the PPPOE dialer to log on. Workgroup
    >>>>> related settings in the PC would be irrelevant in this case as long as
    >>>>> the computer can communicate to the modem. The PPPOE dialer is a
    >>>>> virtual device which becomes the effective internet connection. All of
    >>>>> the required settings information would be supplied by the ISP.
    >>>>> Alternatively, a router could be used instead to make the connections
    >>>>> through the modem when it is in this configuration.
    >>>>>
    >>>>> In the second configuration your modem could be set to connect to the
    >>>>> ISP automatically using its own internal firmware. The relevant
    >>>>> networking settings are made in the modem using its web interface,
    >>>>> either by you yourself or sometimes this information is pre-programmed
    >>>>> in the modem by the ISP if they supplied the modem. You can normally
    >>>>> access the modem's web interface using your browser (try typing
    >>>>> 192.168.0.1 in the address bar). The modem could be set to auto-dial
    >>>>> (AKA always-on) or "dial on demand" mode (i.e.. the modem connects
    >>>>> whenever the PC tries to access the internet and can disconnect again
    >>>>> after a set timeout period of no activity). In this configuration it
    >>>>> is the modem which gets the internet IP from your ISP and then passes
    >>>>> the internet connection to the PC through its LAN port at address
    >>>>> 192.168.0.1 (or whatever the default is). Routing and DHCP may or may
    >>>>> not be enabled in the modem, but if they are enabled your computer
    >>>>> should use 192.168.0.1 as its DHCP server address and receive a LAN
    >>>>> address from the modem, not an internet IP. Possibly 192.168.0.1
    >>>>> should be also entered into the computer's TCP/IP settings as the
    >>>>> gateway address if DNS pass-through is enabled in the modem. Otherwise
    >>>>> the ISP's DNS server addresses should be used. If DHCP is not enabled
    >>>>> in the modem you would enter a fixed LAN address into the computer's
    >>>>> TCP/IP configuration, in the range 192.168.0.x. The modem itself might
    >>>>> have an optional workgroup or domain name entered into its LAN
    >>>>> configuration settings, which is where 'JAYS' could be coming from.
    >>>>> You can probably change or eliminate that yourself.
    >>>>>
    >>>>>
    >>>>>
    >>>>>
    >>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>> news:%23ObFDy%23gIHA.5280@TK2MSFTNGP04.phx.gbl...
    >>>>>> No its a dynamic IP Address assigned by my ISP
    >>>>>>
    >>>>>> I have attached all of the event log in the 3 hours around the time
    >>>>>> of the browser conflict below. Im not sure if this contains any
    >>>>>> other information which might give a clue as to what is going on.
    >>>>>>
    >>>>>> Level Date and Time Source Event ID Task Category
    >>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:22:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:17:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:12:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:11:07 PM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the stopped state.
    >>>>>> Information 3/5/2008 12:10:11 PM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the running state.
    >>>>>> Information 3/5/2008 12:07:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:02:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:00:46 PM EventLog 6013 None The system uptime
    >>>>>> is 57335 seconds.
    >>>>>> Information 3/5/2008 11:57:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 11:52:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 11:48:19 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 11:47:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 11:43:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 11:42:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 11:37:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 11:37:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 11:32:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 11:32:41 AM Microsoft-Windows-User-PnP 20003
    >>>>>> None Driver Management has concluded the process to add Service
    >>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>> status: 0.
    >>>>>> Information 3/5/2008 11:32:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 11:28:17 AM BROWSER 8033 None The browser has
    >>>>>> forced an election on network
    >>>>>> DeviceNetBT_Tcpip_{6C1B0769-602C-49AD-95C1-0AD3B66DA864} because a
    >>>>>> master browser was stopped.
    >>>>>> Information 3/5/2008 11:24:52 AM Service Control Manager 7036 None
    >>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>> stopped state.
    >>>>>> Information 3/5/2008 11:24:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 11:19:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 11:14:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 11:09:56 AM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the stopped state.
    >>>>>> Information 3/5/2008 11:09:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 11:08:55 AM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the running state.
    >>>>>> Information 3/5/2008 11:08:22 AM Service Control Manager 7036 None
    >>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>> running state.
    >>>>>> Information 3/5/2008 11:05:06 AM volsnap 33 None The oldest shadow
    >>>>>> copy of volume C: was deleted to keep disk space usage for shadow
    >>>>>> copies of volume C: below the user defined limit.
    >>>>>> Information 3/5/2008 11:04:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 10:59:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 10:54:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 10:49:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:45:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Error 3/5/2008 10:45:09 AM BROWSER 8009 None The browser was unable
    >>>>>> to promote itself to master browser. The computer that currently
    >>>>>> believes it is the master browser is JAYS.
    >>>>>> Information 3/5/2008 10:44:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:39:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:39:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:34:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:34:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:29:38 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:29:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:24:28 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:24:21 AM Microsoft-Windows-User-PnP 20003
    >>>>>> None Driver Management has concluded the process to add Service
    >>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>> status: 0.
    >>>>>> Information 3/5/2008 10:24:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 10:18:41 AM Service Control Manager 7036 None
    >>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>> stopped state.
    >>>>>> Error 3/5/2008 10:17:06 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:16:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:11:54 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:11:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:06:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 10:05:43 AM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the stopped state.
    >>>>>> Information 3/5/2008 10:05:33 AM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the running state.
    >>>>>> Information 3/5/2008 10:05:26 AM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the stopped state.
    >>>>>> Information 3/5/2008 10:02:39 AM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the running state.
    >>>>>> Information 3/5/2008 10:02:11 AM Service Control Manager 7036 None
    >>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>> running state.
    >>>>>> Information 3/5/2008 10:01:36 AM Microsoft-Windows-User-PnP 20003
    >>>>>> None Driver Management has concluded the process to add Service
    >>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>> status: 0.
    >>>>>> Error 3/5/2008 10:01:30 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:01:17 AM Microsoft-Windows-User-PnP 20003
    >>>>>> None Driver Management has concluded the process to add Service
    >>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the following
    >>>>>> status: 0.
    >>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None
    >>>>>> The IP address lease 192.168.1.64 for the Network Card with network
    >>>>>> address 0016D3A2E7AD has been denied by the DHCP server 192.168.0.1
    >>>>>> (The DHCP Server sent a DHCPNACK message).
    >>>>>> Warning 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1003 None
    >>>>>> "The description for Event ID 1003 from source
    >>>>>> Microsoft-Windows-Dhcp-Client cannot be found. Either the component
    >>>>>> that raises this event is not installed on your local computer or the
    >>>>>> installation is corrupted. You can install or repair the component on
    >>>>>> the local computer.
    >>>>>>
    >>>>>> If the event originated on another computer, the display information
    >>>>>> had to be saved with the event.
    >>>>>>
    >>>>>> The following information was included with the event:
    >>>>>>
    >>>>>> 0016D3A2E7AD
    >>>>>> %%2163146757
    >>>>>>
    >>>>>> The description string for parameter reference (%1) could not be
    >>>>>> found
    >>>>>> "
    >>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 9:57:44 AM Service Control Manager 7036 None The
    >>>>>> LiveUpdate service entered the stopped state.
    >>>>>> Information 3/5/2008 9:57:37 AM Service Control Manager 7036 None The
    >>>>>> LiveUpdate service entered the running state.
    >>>>>> Information 3/5/2008 9:52:42 AM Service Control Manager 7036 None The
    >>>>>> LiveUpdate service entered the stopped state.
    >>>>>> Information 3/5/2008 9:52:35 AM Service Control Manager 7036 None The
    >>>>>> LiveUpdate service entered the running state.
    >>>>>> Information 3/5/2008 9:38:26 AM Service Control Manager 7036 None The
    >>>>>> WinHTTP Web Proxy Auto-Discovery Service service entered the stopped
    >>>>>> state.
    >>>>>> Information 3/5/2008 9:37:56 AM Microsoft-Windows-User-PnP 20003 None
    >>>>>> Driver Management has concluded the process to add Service tunnel for
    >>>>>> Device Instance ID ROOT*ISATAP002 with the following status: 0.
    >>>>>> Information 3/5/2008 9:37:48 AM Service Control Manager 7036 None The
    >>>>>> Windows Image Acquisition (WIA) service entered the running state.
    >>>>>> Information 3/5/2008 9:37:39 AM
    >>>>>> Microsoft-Windows-Power-Troubleshooter 1 None "The system has resumed
    >>>>>> from sleep.
    >>>>>>
    >>>>>> Sleep Time: 3/5/2008 7:12:57 AM
    >>>>>> Wake Time: 3/5/2008 5:37:34 PM
    >>>>>>
    >>>>>> Wake Source: Unknown"
    >>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>> "Bob F." <bob@NOSPAN.com> wrote in message
    >>>>>> news:52055B79-F315-4C46-986D-CB8AFBFF2D37@microsoft.com...
    >>>>>>> Where did you get the setup information for your internet
    >>>>>>> connection? Did you use a static IP? Maybe it's incorrect and you
    >>>>>>> are encroaching onto someone else's IP space.
    >>>>>>>
    >>>>>>> --
    >>>>>>> BobF.
    >>>>>>> "Dave" <dave@beepbeep.com> wrote in message
    >>>>>>> news:eBrCR47gIHA.4436@TK2MSFTNGP02.phx.gbl...
    >>>>>>>> What shows up in Start - Network?
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>> news:#orAgk7gIHA.2448@TK2MSFTNGP03.phx.gbl...
    >>>>>>>>> My (lone) machine is connected directly to the DSL router with no
    >>>>>>>>> wireless capabilities on the router. Despite this I get the
    >>>>>>>>> following message in the event log:
    >>>>>>>>>
    >>>>>>>>> The browser was unable to promote itself to master browser. The
    >>>>>>>>> computer that currently believes it is the master browser is JAYS.
    >>>>>>>>>
    >>>>>>>>> Once again, my computer is not called JAYS. Friends and family
    >>>>>>>>> are not Vista Security experts. Looking for capable / expert
    >>>>>>>>> advice from this forum.
    >>>>>>>>>
    >>>>>>>>> What are the possible explanations for this???
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> "Malke" <malke@invalid.invalid> wrote in message
    >>>>>>>>> news:O5eVD62gIHA.4692@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>>> Nubie wrote:
    >>>>>>>>>>
    >>>>>>>>>>> What should I be looking for in the Settings?
    >>>>>>>>>>>
    >>>>>>>>>>> ALSO: How would the config of my DSL modem confuse my vista
    >>>>>>>>>>> machine to
    >>>>>>>>>>> think that there is another computer called JAYS on my local
    >>>>>>>>>>> network.
    >>>>>>>>>>
    >>>>>>>>>>>> Nubie;642434 Wrote:
    >>>>>>>>>>>>> Hi
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> I have a single (lone) windows Vista machine connected
    >>>>>>>>>>>>> directly to the
    >>>>>>>>>>>>> internet via a dsl modem. I just viewed the following in my
    >>>>>>>>>>>>> eventlogs:
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> "The browser was unable to promote itself to master browser.
    >>>>>>>>>>>>> The
    >>>>>>>>>>>>> computer
    >>>>>>>>>>>>> that
    >>>>>>>>>>>>> currently believes it is the master browser is JAYS. My
    >>>>>>>>>>>>> machine is NOT
    >>>>>>>>>>>>> called JAYS."
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> What is happening here!!?? If my machine is connected to a DSL
    >>>>>>>>>>>>> modem
    >>>>>>>>>>>>> with
    >>>>>>>>>>>>> no additional
    >>>>>>>>>>>>> machines connected to that modem why is this message appearing
    >>>>>>>>>>>>> ????
    >>>>>>>>>>>>> What is
    >>>>>>>>>>>>> happening here ??
    >>>>>>>>>>
    >>>>>>>>>> It certainly seems as though someone else is on your network. Is
    >>>>>>>>>> this a
    >>>>>>>>>> combination modem/wireless router? If yes, you probably haven't
    >>>>>>>>>> secured
    >>>>>>>>>> your wireless properly and a stranger is using your bandwidth. If
    >>>>>>>>>> you only
    >>>>>>>>>> have a single computer connected directly to a DSL modem by
    >>>>>>>>>> ethernet cable
    >>>>>>>>>> (no wireless router), then call your ISP. Because you don't
    >>>>>>>>>> really know
    >>>>>>>>>> what you're looking at - and I mean no disrespect to you, I'm
    >>>>>>>>>> just being
    >>>>>>>>>> practical - it might be smart for you to have a computer
    >>>>>>>>>> professional come
    >>>>>>>>>> on-site and take a look. This will not be someone from a
    >>>>>>>>>> BigComputerStore/GeekSquad type of place. Get recommendations
    >>>>>>>>>> from friends,
    >>>>>>>>>> family, colleagues.
    >>>>>>>>>>
    >>>>>>>>>> Malke
    >>>>>>>>>> --
    >>>>>>>>>> MS-MVP
    >>>>>>>>>> Elephant Boy Computers
    >>>>>>>>>>
    >>>>>>>>>> Don't Panic!
    >>>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>><!--colorc--><!--/colorc-->
    >><!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     
    Nubie, Mar 13, 2008
    #21
  3. RalfG

    RalfG Guest

    Open a command prompt and enter "ipconfig /all", without the quotes. What do
    you get?

    Other points in-line below.

    "Nubie" <newsgoup_contact@atigen.com> wrote in message
    news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > 0016D3A2E7AD is my machines regular (wire) network card. The wireless
    > card is disabled in device manager (which presumably rules any wireles
    > connection out). 68.127.186.255 is AT&T's network, which is my ISP (ARIN
    > lookup below):
    >
    > AT&T Internet Services SBCIS-SIS80 (NET-68-120-0-0-1)
    > 68.120.0.0 - 68.127.255.255
    > bras4.pltnca SBC068127176000040211 (NET-68-127-176-0-1)
    > 68.127.176.0 - 68.127.191.255
    >
    > The constantly repeating reconnection notices at 5 minute intervals, (with
    > resulting successfully assigned IP addresses), is probably a result of the
    > fact that I remove the ethernet cable from my network card whenever I step
    > away from my machine.<!--colorc--><!--/colorc-->

    You really shouldn't do that. Only USB is generally safe to hot-plug. Sooner
    or later you're luck will run out and one or the other ethernet devices will
    fry. That aside, unplugging it doesn't account for those repeating
    reconnections. The timing is too consistent, down to the second.
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    > The only other remotely possible connection to my PC would have been
    > bluetooth, however the wireless card which provides bluetooth connectivity
    > is always turned off (at the switch).
    >
    > This leaves 2 questions
    >
    > 1) How could there be a master browser called JAYS showing up on my logs
    > (given the above).<!--colorc--><!--/colorc-->

    You would both have to be peers connected on the same LAN or directly to
    each other (same thing). Any PC on a LAN can be a master browser. I have one
    XP PC on mine that always insists on taking that status when it joins the
    LAN.
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > and (less importantly)
    >
    > 2) Why is my machine having a conversation with the outside world (my ISP)
    > about its workgroup. My understanding was that a workgroup would be
    > something that would be limited to my LAN alone.<!--colorc--><!--/colorc-->

    Let's see what ipconfig shows.
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    >
    >
    > "RalfG" <itsnotme@ladeda.deda> wrote in message
    > news:6AD5B7D8-0DFF-4421-8DF9-3FF57637594C@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> The anomalous name being in the router was only a suggestion, it's an
    >> option in mine that could also be in yours. As far as not finding the LAN
    >> DHCP server in the netbios table, this ....
    >>
    >> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None The IP<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>>> address lease 192.168.1.64 for the Network Card with network address
    >>>>> 0016D3A2E7AD has been denied by the DHCP server 192.168.0.1 (The DHCP
    >>>>> Server sent a DHCPNACK message).<!--colorc--><!--/colorc-->
    >>
    >> says that it exists, at least some of the time, and that your computer
    >> tried to use it with an incorrect network address and got booted. This on
    >> the other hand....
    >>
    >> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP :1d""<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."<!--colorc--><!--/colorc-->
    >>
    >> says your computer subsequently tried to connect to a server on the
    >> internet, probably your ISP, possibly somewhere else. There's no
    >> indication here whether it is the same network adapter making the
    >> connection as the one above but we can see from the text that your
    >> network adapter in this case also "somehow" had some incorrect
    >> information set in its configuration at the time.
    >>
    >> OTOH these constantly repeating reconnection notices at 5 minute
    >> intervals....
    >><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.<!--colorc--><!--/colorc-->
    >>
    >> Are very much like what you can see happening with wireless connections.
    >> If I were going to make a guess as to what is going on here I'd say that
    >> apart from the ethernet adapter you connect to your own modem with you do
    >> have a wireless adapter in that computer, it is always turned on and it
    >> is set to automatically connect to any available network. Every so often
    >> your PC is piggybacking a ride, or trying to, on poor JAYS wireless
    >> network. :)
    >>
    >>
    >>
    >> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >> news:OUZ0QCKhIHA.4740@TK2MSFTNGP05.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>
    >>> If JAYS were the name of the modem or in its netbios table, then it
    >>> should still be there presumably. (I have not reconfigured the modem in
    >>> several months, and at that I time I set it to factory defaults - so the
    >>> name JAYS should not be assigned to the modem).
    >>>
    >>> I checked the mode that the modem is operating. This is as follows:
    >>>
    >>> PPP is on the modem. (PPP session is initiated from the modem.) - i.e.
    >>> Not operating in Bridging mode
    >>>
    >>> I believe my DHCP server is assigned by the gateway, when I connect
    >>> (i.e. no static IP configured on my machine).
    >>>
    >>> I did a lookup of the netbios name table on my PC which I listed below
    >>> (When I tried nbtstat -a 192.168.0.1 for the modem I got "host not
    >>> found").
    >>>
    >>>
    >>> NetBIOS Local Name Table
    >>>
    >>> Name Type Status
    >>> ---------------------------------------------
    >>> MYPC <00> UNIQUE Registered
    >>> WORKGROUP <00> GROUP Registered
    >>> MYPC <20> UNIQUE Registered
    >>> WORKGROUP <1E> GROUP Registered
    >>> WORKGROUP <1D> UNIQUE Registered
    >>> ..__MSBROWSE__. <01> GROUP Registered
    >>>
    >>>
    >>>
    >>>
    >>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>> news:EBF529EE-1C6A-4D4F-BB48-82EA200A86A9@microsoft.com...
    >>>> It looks like your network connection may be misconfigured. From the
    >>>> events at timestamp 10:01 and later it appears you have two conflicting
    >>>> DHCP services being used. You have a DHCP server at 192.168.0.1 which
    >>>> I presume is the DSL Modem with routing capabilities enabled. You are
    >>>> also trying to get a DHCP address directly from your ISP, probably
    >>>> using IP 68.127.186.255 as the DHCP server address. You should use only
    >>>> one or the other. I'd try turning off DHCP in the modem first and see
    >>>> how that works out.
    >>>>
    >>>> The modem can probably be configured in several different operating
    >>>> modes. I have no way of knowing what your available options are or
    >>>> which mode has been enabled. My own has 4 distinct DSL operating modes
    >>>> plus various combinations of routing and firewall features. IOW, there
    >>>> are umpteen ways to screw up the connection. :)
    >>>>
    >>>> Typically there are two common connection modes that might be used. One
    >>>> way is to have the modem set in 'bridge" mode, where it only makes the
    >>>> hardware connection to the DSL carrier signal. You would Windows built
    >>>> in PPPOE "dialer" to log into your ISP from your computer. In this
    >>>> configuration the ISP's DHCP server would give your computer an
    >>>> internet IP ... i.e.. 68.127.186.115. You would need to set up your ISP
    >>>> username and password in the PPPOE dialer to log on. Workgroup related
    >>>> settings in the PC would be irrelevant in this case as long as the
    >>>> computer can communicate to the modem. The PPPOE dialer is a virtual
    >>>> device which becomes the effective internet connection. All of the
    >>>> required settings information would be supplied by the ISP.
    >>>> Alternatively, a router could be used instead to make the connections
    >>>> through the modem when it is in this configuration.
    >>>>
    >>>> In the second configuration your modem could be set to connect to the
    >>>> ISP automatically using its own internal firmware. The relevant
    >>>> networking settings are made in the modem using its web interface,
    >>>> either by you yourself or sometimes this information is pre-programmed
    >>>> in the modem by the ISP if they supplied the modem. You can normally
    >>>> access the modem's web interface using your browser (try typing
    >>>> 192.168.0.1 in the address bar). The modem could be set to auto-dial
    >>>> (AKA always-on) or "dial on demand" mode (i.e.. the modem connects
    >>>> whenever the PC tries to access the internet and can disconnect again
    >>>> after a set timeout period of no activity). In this configuration it
    >>>> is the modem which gets the internet IP from your ISP and then passes
    >>>> the internet connection to the PC through its LAN port at address
    >>>> 192.168.0.1 (or whatever the default is). Routing and DHCP may or may
    >>>> not be enabled in the modem, but if they are enabled your computer
    >>>> should use 192.168.0.1 as its DHCP server address and receive a LAN
    >>>> address from the modem, not an internet IP. Possibly 192.168.0.1 should
    >>>> be also entered into the computer's TCP/IP settings as the gateway
    >>>> address if DNS pass-through is enabled in the modem. Otherwise the
    >>>> ISP's DNS server addresses should be used. If DHCP is not enabled in
    >>>> the modem you would enter a fixed LAN address into the computer's
    >>>> TCP/IP configuration, in the range 192.168.0.x. The modem itself might
    >>>> have an optional workgroup or domain name entered into its LAN
    >>>> configuration settings, which is where 'JAYS' could be coming from. You
    >>>> can probably change or eliminate that yourself.
    >>>>
    >>>>
    >>>>
    >>>>
    >>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>> news:%23ObFDy%23gIHA.5280@TK2MSFTNGP04.phx.gbl...
    >>>>> No its a dynamic IP Address assigned by my ISP
    >>>>>
    >>>>> I have attached all of the event log in the 3 hours around the time of
    >>>>> the browser conflict below. Im not sure if this contains any other
    >>>>> information which might give a clue as to what is going on.
    >>>>>
    >>>>> Level Date and Time Source Event ID Task Category
    >>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 12:22:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 12:17:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 12:12:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 12:11:07 PM Service Control Manager 7036 None The
    >>>>> LiveUpdate service entered the stopped state.
    >>>>> Information 3/5/2008 12:10:11 PM Service Control Manager 7036 None The
    >>>>> LiveUpdate service entered the running state.
    >>>>> Information 3/5/2008 12:07:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 12:02:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 12:00:46 PM EventLog 6013 None The system uptime
    >>>>> is 57335 seconds.
    >>>>> Information 3/5/2008 11:57:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 11:52:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Error 3/5/2008 11:48:19 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Information 3/5/2008 11:47:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Error 3/5/2008 11:43:09 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Information 3/5/2008 11:42:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Error 3/5/2008 11:37:59 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Information 3/5/2008 11:37:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Error 3/5/2008 11:32:49 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Information 3/5/2008 11:32:41 AM Microsoft-Windows-User-PnP 20003 None
    >>>>> Driver Management has concluded the process to add Service tunnel for
    >>>>> Device Instance ID ROOT*6TO4MP001 with the following status: 0.
    >>>>> Information 3/5/2008 11:32:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system detected
    >>>>> that network adapter Local Area Connection was connected to the
    >>>>> network, and has initiated normal operation.
    >>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system detected
    >>>>> that network adapter Local Area Connection was connected to the
    >>>>> network, and has initiated normal operation.
    >>>>> Information 3/5/2008 11:28:17 AM BROWSER 8033 None The browser has
    >>>>> forced an election on network
    >>>>> DeviceNetBT_Tcpip_{6C1B0769-602C-49AD-95C1-0AD3B66DA864} because a
    >>>>> master browser was stopped.
    >>>>> Information 3/5/2008 11:24:52 AM Service Control Manager 7036 None The
    >>>>> WinHTTP Web Proxy Auto-Discovery Service service entered the stopped
    >>>>> state.
    >>>>> Information 3/5/2008 11:24:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 11:19:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 11:14:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 11:09:56 AM Service Control Manager 7036 None The
    >>>>> LiveUpdate service entered the stopped state.
    >>>>> Information 3/5/2008 11:09:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 11:08:55 AM Service Control Manager 7036 None The
    >>>>> LiveUpdate service entered the running state.
    >>>>> Information 3/5/2008 11:08:22 AM Service Control Manager 7036 None The
    >>>>> WinHTTP Web Proxy Auto-Discovery Service service entered the running
    >>>>> state.
    >>>>> Information 3/5/2008 11:05:06 AM volsnap 33 None The oldest shadow
    >>>>> copy of volume C: was deleted to keep disk space usage for shadow
    >>>>> copies of volume C: below the user defined limit.
    >>>>> Information 3/5/2008 11:04:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 10:59:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 10:54:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 10:49:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Error 3/5/2008 10:45:09 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Error 3/5/2008 10:45:09 AM BROWSER 8009 None The browser was unable to
    >>>>> promote itself to master browser. The computer that currently
    >>>>> believes it is the master browser is JAYS.
    >>>>> Information 3/5/2008 10:44:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Error 3/5/2008 10:39:59 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Information 3/5/2008 10:39:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Error 3/5/2008 10:34:49 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Information 3/5/2008 10:34:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Error 3/5/2008 10:29:38 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Information 3/5/2008 10:29:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Error 3/5/2008 10:24:28 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Information 3/5/2008 10:24:21 AM Microsoft-Windows-User-PnP 20003 None
    >>>>> Driver Management has concluded the process to add Service tunnel for
    >>>>> Device Instance ID ROOT*6TO4MP001 with the following status: 0.
    >>>>> Information 3/5/2008 10:24:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system detected
    >>>>> that network adapter Local Area Connection was connected to the
    >>>>> network, and has initiated normal operation.
    >>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system detected
    >>>>> that network adapter Local Area Connection was connected to the
    >>>>> network, and has initiated normal operation.
    >>>>> Information 3/5/2008 10:18:41 AM Service Control Manager 7036 None The
    >>>>> WinHTTP Web Proxy Auto-Discovery Service service entered the stopped
    >>>>> state.
    >>>>> Error 3/5/2008 10:17:06 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Information 3/5/2008 10:16:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Error 3/5/2008 10:11:54 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Information 3/5/2008 10:11:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Information 3/5/2008 10:06:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>> None Your computer was successfully assigned an address from the
    >>>>> network, and it can now connect to other computers.
    >>>>> Information 3/5/2008 10:05:43 AM Service Control Manager 7036 None The
    >>>>> LiveUpdate service entered the stopped state.
    >>>>> Information 3/5/2008 10:05:33 AM Service Control Manager 7036 None The
    >>>>> LiveUpdate service entered the running state.
    >>>>> Information 3/5/2008 10:05:26 AM Service Control Manager 7036 None The
    >>>>> LiveUpdate service entered the stopped state.
    >>>>> Information 3/5/2008 10:02:39 AM Service Control Manager 7036 None The
    >>>>> LiveUpdate service entered the running state.
    >>>>> Information 3/5/2008 10:02:11 AM Service Control Manager 7036 None The
    >>>>> WinHTTP Web Proxy Auto-Discovery Service service entered the running
    >>>>> state.
    >>>>> Information 3/5/2008 10:01:36 AM Microsoft-Windows-User-PnP 20003 None
    >>>>> Driver Management has concluded the process to add Service tunnel for
    >>>>> Device Instance ID ROOT*6TO4MP001 with the following status: 0.
    >>>>> Error 3/5/2008 10:01:30 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>> could not be registered on the interface with IP address
    >>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>> not allow the name to be claimed by this computer."
    >>>>> Information 3/5/2008 10:01:17 AM Microsoft-Windows-User-PnP 20003 None
    >>>>> Driver Management has concluded the process to add Service tunnel for
    >>>>> Device Instance ID ROOT*ISATAP002 with the following status: 0.
    >>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None The
    >>>>> IP address lease 192.168.1.64 for the Network Card with network
    >>>>> address 0016D3A2E7AD has been denied by the DHCP server 192.168.0.1
    >>>>> (The DHCP Server sent a DHCPNACK message).
    >>>>> Warning 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1003 None
    >>>>> "The description for Event ID 1003 from source
    >>>>> Microsoft-Windows-Dhcp-Client cannot be found. Either the component
    >>>>> that raises this event is not installed on your local computer or the
    >>>>> installation is corrupted. You can install or repair the component on
    >>>>> the local computer.
    >>>>>
    >>>>> If the event originated on another computer, the display information
    >>>>> had to be saved with the event.
    >>>>>
    >>>>> The following information was included with the event:
    >>>>>
    >>>>> 0016D3A2E7AD
    >>>>> %%2163146757
    >>>>>
    >>>>> The description string for parameter reference (%1) could not be found
    >>>>> "
    >>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system detected
    >>>>> that network adapter Local Area Connection was connected to the
    >>>>> network, and has initiated normal operation.
    >>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system detected
    >>>>> that network adapter Local Area Connection was connected to the
    >>>>> network, and has initiated normal operation.
    >>>>> Information 3/5/2008 9:57:44 AM Service Control Manager 7036 None The
    >>>>> LiveUpdate service entered the stopped state.
    >>>>> Information 3/5/2008 9:57:37 AM Service Control Manager 7036 None The
    >>>>> LiveUpdate service entered the running state.
    >>>>> Information 3/5/2008 9:52:42 AM Service Control Manager 7036 None The
    >>>>> LiveUpdate service entered the stopped state.
    >>>>> Information 3/5/2008 9:52:35 AM Service Control Manager 7036 None The
    >>>>> LiveUpdate service entered the running state.
    >>>>> Information 3/5/2008 9:38:26 AM Service Control Manager 7036 None The
    >>>>> WinHTTP Web Proxy Auto-Discovery Service service entered the stopped
    >>>>> state.
    >>>>> Information 3/5/2008 9:37:56 AM Microsoft-Windows-User-PnP 20003 None
    >>>>> Driver Management has concluded the process to add Service tunnel for
    >>>>> Device Instance ID ROOT*ISATAP002 with the following status: 0.
    >>>>> Information 3/5/2008 9:37:48 AM Service Control Manager 7036 None The
    >>>>> Windows Image Acquisition (WIA) service entered the running state.
    >>>>> Information 3/5/2008 9:37:39 AM Microsoft-Windows-Power-Troubleshooter
    >>>>> 1 None "The system has resumed from sleep.
    >>>>>
    >>>>> Sleep Time: 3/5/2008 7:12:57 AM
    >>>>> Wake Time: 3/5/2008 5:37:34 PM
    >>>>>
    >>>>> Wake Source: Unknown"
    >>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system detected
    >>>>> that network adapter Local Area Connection was connected to the
    >>>>> network, and has initiated normal operation.
    >>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system detected
    >>>>> that network adapter Local Area Connection was connected to the
    >>>>> network, and has initiated normal operation.
    >>>>>
    >>>>>
    >>>>>
    >>>>>
    >>>>>
    >>>>>
    >>>>> "Bob F." <bob@NOSPAN.com> wrote in message
    >>>>> news:52055B79-F315-4C46-986D-CB8AFBFF2D37@microsoft.com...
    >>>>>> Where did you get the setup information for your internet connection?
    >>>>>> Did you use a static IP? Maybe it's incorrect and you are
    >>>>>> encroaching onto someone else's IP space.
    >>>>>>
    >>>>>> --
    >>>>>> BobF.
    >>>>>> "Dave" <dave@beepbeep.com> wrote in message
    >>>>>> news:eBrCR47gIHA.4436@TK2MSFTNGP02.phx.gbl...
    >>>>>>> What shows up in Start - Network?
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>> news:#orAgk7gIHA.2448@TK2MSFTNGP03.phx.gbl...
    >>>>>>>> My (lone) machine is connected directly to the DSL router with no
    >>>>>>>> wireless capabilities on the router. Despite this I get the
    >>>>>>>> following message in the event log:
    >>>>>>>>
    >>>>>>>> The browser was unable to promote itself to master browser. The
    >>>>>>>> computer that currently believes it is the master browser is JAYS.
    >>>>>>>>
    >>>>>>>> Once again, my computer is not called JAYS. Friends and family are
    >>>>>>>> not Vista Security experts. Looking for capable / expert advice
    >>>>>>>> from this forum.
    >>>>>>>>
    >>>>>>>> What are the possible explanations for this???
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "Malke" <malke@invalid.invalid> wrote in message
    >>>>>>>> news:O5eVD62gIHA.4692@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>> Nubie wrote:
    >>>>>>>>>
    >>>>>>>>>> What should I be looking for in the Settings?
    >>>>>>>>>>
    >>>>>>>>>> ALSO: How would the config of my DSL modem confuse my vista
    >>>>>>>>>> machine to
    >>>>>>>>>> think that there is another computer called JAYS on my local
    >>>>>>>>>> network.
    >>>>>>>>>
    >>>>>>>>>>> Nubie;642434 Wrote:
    >>>>>>>>>>>> Hi
    >>>>>>>>>>>>
    >>>>>>>>>>>> I have a single (lone) windows Vista machine connected directly
    >>>>>>>>>>>> to the
    >>>>>>>>>>>> internet via a dsl modem. I just viewed the following in my
    >>>>>>>>>>>> eventlogs:
    >>>>>>>>>>>>
    >>>>>>>>>>>> "The browser was unable to promote itself to master browser.
    >>>>>>>>>>>> The
    >>>>>>>>>>>> computer
    >>>>>>>>>>>> that
    >>>>>>>>>>>> currently believes it is the master browser is JAYS. My machine
    >>>>>>>>>>>> is NOT
    >>>>>>>>>>>> called JAYS."
    >>>>>>>>>>>>
    >>>>>>>>>>>> What is happening here!!?? If my machine is connected to a DSL
    >>>>>>>>>>>> modem
    >>>>>>>>>>>> with
    >>>>>>>>>>>> no additional
    >>>>>>>>>>>> machines connected to that modem why is this message appearing
    >>>>>>>>>>>> ????
    >>>>>>>>>>>> What is
    >>>>>>>>>>>> happening here ??
    >>>>>>>>>
    >>>>>>>>> It certainly seems as though someone else is on your network. Is
    >>>>>>>>> this a
    >>>>>>>>> combination modem/wireless router? If yes, you probably haven't
    >>>>>>>>> secured
    >>>>>>>>> your wireless properly and a stranger is using your bandwidth. If
    >>>>>>>>> you only
    >>>>>>>>> have a single computer connected directly to a DSL modem by
    >>>>>>>>> ethernet cable
    >>>>>>>>> (no wireless router), then call your ISP. Because you don't really
    >>>>>>>>> know
    >>>>>>>>> what you're looking at - and I mean no disrespect to you, I'm just
    >>>>>>>>> being
    >>>>>>>>> practical - it might be smart for you to have a computer
    >>>>>>>>> professional come
    >>>>>>>>> on-site and take a look. This will not be someone from a
    >>>>>>>>> BigComputerStore/GeekSquad type of place. Get recommendations from
    >>>>>>>>> friends,
    >>>>>>>>> family, colleagues.
    >>>>>>>>>
    >>>>>>>>> Malke
    >>>>>>>>> --
    >>>>>>>>> MS-MVP
    >>>>>>>>> Elephant Boy Computers
    >>>>>>>>>
    >>>>>>>>> Don't Panic!
    >>>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>><!--colorc--><!--/colorc-->
    >><!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     
    RalfG, Mar 14, 2008
    #22
  4. Nubie

    Nubie Guest

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : mypc
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : domain_not_set.invalid

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . : domain_not_set.invalid
    Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
    Physical Address. . . . . . . . . : 00-16-D3-A2-E7-AD
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . :
    ff80::80f6:625f:f376:8301%6(Preferred)
    IPv4 Address. . . . . . . . . . . : 68.127.175.71(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Friday, March 14, 2008 12:05:54 PM
    Lease Expires . . . . . . . . . . : Friday, March 14, 2008 3:41:18 PM
    Default Gateway . . . . . . . . . : 68.127.175.72
    DHCP Server . . . . . . . . . . . : 192.168.0.1
    DHCPv6 IAID . . . . . . . . . . . : 203332435
    DNS Servers . . . . . . . . . . . : 192.168.0.1
    192.168.0.1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 6:

    Connection-specific DNS Suffix . : domain_not_set.invalid
    Description . . . . . . . . . . . : isatap.domain_not_set.invalid
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . :
    ff80::200:5fff:68.128.185.71%14(Preferred
    )
    Default Gateway . . . . . . . . . :
    DNS Servers . . . . . . . . . . . : 192.168.0.1
    192.168.0.1
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 7:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . :
    2001:0:4337:9f66:18f9:3343:ff80:50f8(Pref
    erred)
    Link-local IPv6 Address . . . . . :
    ff80::38f9:3343:ff80:50f8%12(Preferred)
    Default Gateway . . . . . . . . . :
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 14:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : 6TO4 Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 10:

    Connection-specific DNS Suffix . : domain_not_set.invalid
    Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Temporary IPv6 Address. . . . . . : 2002:227f:ff27::227f:ff27(Preferred)
    Default Gateway . . . . . . . . . : 2002:f058:6301::f058:6301
    DNS Servers . . . . . . . . . . . : 192.168.0.1
    192.168.0.1
    NetBIOS over Tcpip. . . . . . . . : Disabled




    "RalfG" <itsnotme@ladeda.deda> wrote in message
    news:C5E12624-0EEF-4A6D-84C9-AF9BB6440665@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Open a command prompt and enter "ipconfig /all", without the quotes. What
    > do you get?
    >
    > Other points in-line below.
    >
    > "Nubie" <newsgoup_contact@atigen.com> wrote in message
    > news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> 0016D3A2E7AD is my machines regular (wire) network card. The wireless
    >> card is disabled in device manager (which presumably rules any wireles
    >> connection out). 68.127.186.255 is AT&T's network, which is my ISP (ARIN
    >> lookup below):
    >>
    >> AT&T Internet Services SBCIS-SIS80 (NET-68-120-0-0-1)
    >> 68.120.0.0 - 68.127.255.255
    >> bras4.pltnca SBC068127176000040211 (NET-68-127-176-0-1)
    >> 68.127.176.0 - 68.127.191.255
    >>
    >> The constantly repeating reconnection notices at 5 minute intervals,
    >> (with resulting successfully assigned IP addresses), is probably a result
    >> of the fact that I remove the ethernet cable from my network card
    >> whenever I step away from my machine.<!--colorc--><!--/colorc-->
    >
    > You really shouldn't do that. Only USB is generally safe to hot-plug.
    > Sooner or later you're luck will run out and one or the other ethernet
    > devices will fry. That aside, unplugging it doesn't account for those
    > repeating reconnections. The timing is too consistent, down to the second.
    ><!--coloro:green--><span style="color:green <!--/coloro-->
    >>
    >> The only other remotely possible connection to my PC would have been
    >> bluetooth, however the wireless card which provides bluetooth
    >> connectivity is always turned off (at the switch).
    >>
    >> This leaves 2 questions
    >>
    >> 1) How could there be a master browser called JAYS showing up on my logs
    >> (given the above).<!--colorc--><!--/colorc-->
    >
    > You would both have to be peers connected on the same LAN or directly to
    > each other (same thing). Any PC on a LAN can be a master browser. I have
    > one XP PC on mine that always insists on taking that status when it joins
    > the LAN.
    ><!--coloro:green--><span style="color:green <!--/coloro-->
    >> and (less importantly)
    >>
    >> 2) Why is my machine having a conversation with the outside world (my
    >> ISP) about its workgroup. My understanding was that a workgroup would be
    >> something that would be limited to my LAN alone.<!--colorc--><!--/colorc-->
    >
    > Let's see what ipconfig shows.
    ><!--coloro:green--><span style="color:green <!--/coloro-->
    >>
    >>
    >>
    >> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >> news:6AD5B7D8-0DFF-4421-8DF9-3FF57637594C@microsoft.com...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> The anomalous name being in the router was only a suggestion, it's an
    >>> option in mine that could also be in yours. As far as not finding the
    >>> LAN DHCP server in the netbios table, this ....
    >>>
    >>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None The
    >>> IP
    >>>>>> address lease 192.168.1.64 for the Network Card with network address
    >>>>>> 0016D3A2E7AD has been denied by the DHCP server 192.168.0.1 (The DHCP
    >>>>>> Server sent a DHCPNACK message).
    >>>
    >>> says that it exists, at least some of the time, and that your computer
    >>> tried to use it with an incorrect network address and got booted. This
    >>> on the other hand....
    >>>
    >>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>>> could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>
    >>> says your computer subsequently tried to connect to a server on the
    >>> internet, probably your ISP, possibly somewhere else. There's no
    >>> indication here whether it is the same network adapter making the
    >>> connection as the one above but we can see from the text that your
    >>> network adapter in this case also "somehow" had some incorrect
    >>> information set in its configuration at the time.
    >>>
    >>> OTOH these constantly repeating reconnection notices at 5 minute
    >>> intervals....
    >>>
    >>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>
    >>> Are very much like what you can see happening with wireless connections.
    >>> If I were going to make a guess as to what is going on here I'd say that
    >>> apart from the ethernet adapter you connect to your own modem with you
    >>> do have a wireless adapter in that computer, it is always turned on and
    >>> it is set to automatically connect to any available network. Every so
    >>> often your PC is piggybacking a ride, or trying to, on poor JAYS
    >>> wireless network. :)
    >>>
    >>>
    >>>
    >>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>> news:OUZ0QCKhIHA.4740@TK2MSFTNGP05.phx.gbl...
    >>>>
    >>>> If JAYS were the name of the modem or in its netbios table, then it
    >>>> should still be there presumably. (I have not reconfigured the modem
    >>>> in several months, and at that I time I set it to factory defaults - so
    >>>> the name JAYS should not be assigned to the modem).
    >>>>
    >>>> I checked the mode that the modem is operating. This is as follows:
    >>>>
    >>>> PPP is on the modem. (PPP session is initiated from the modem.) - i.e.
    >>>> Not operating in Bridging mode
    >>>>
    >>>> I believe my DHCP server is assigned by the gateway, when I connect
    >>>> (i.e. no static IP configured on my machine).
    >>>>
    >>>> I did a lookup of the netbios name table on my PC which I listed below
    >>>> (When I tried nbtstat -a 192.168.0.1 for the modem I got "host not
    >>>> found").
    >>>>
    >>>>
    >>>> NetBIOS Local Name Table
    >>>>
    >>>> Name Type Status
    >>>> ---------------------------------------------
    >>>> MYPC <00> UNIQUE Registered
    >>>> WORKGROUP <00> GROUP Registered
    >>>> MYPC <20> UNIQUE Registered
    >>>> WORKGROUP <1E> GROUP Registered
    >>>> WORKGROUP <1D> UNIQUE Registered
    >>>> ..__MSBROWSE__. <01> GROUP Registered
    >>>>
    >>>>
    >>>>
    >>>>
    >>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>> news:EBF529EE-1C6A-4D4F-BB48-82EA200A86A9@microsoft.com...
    >>>>> It looks like your network connection may be misconfigured. From the
    >>>>> events at timestamp 10:01 and later it appears you have two
    >>>>> conflicting DHCP services being used. You have a DHCP server at
    >>>>> 192.168.0.1 which I presume is the DSL Modem with routing
    >>>>> capabilities enabled. You are also trying to get a DHCP address
    >>>>> directly from your ISP, probably using IP 68.127.186.255 as the DHCP
    >>>>> server address. You should use only one or the other. I'd try turning
    >>>>> off DHCP in the modem first and see how that works out.
    >>>>>
    >>>>> The modem can probably be configured in several different operating
    >>>>> modes. I have no way of knowing what your available options are or
    >>>>> which mode has been enabled. My own has 4 distinct DSL operating modes
    >>>>> plus various combinations of routing and firewall features. IOW, there
    >>>>> are umpteen ways to screw up the connection. :)
    >>>>>
    >>>>> Typically there are two common connection modes that might be used.
    >>>>> One way is to have the modem set in 'bridge" mode, where it only makes
    >>>>> the hardware connection to the DSL carrier signal. You would Windows
    >>>>> built in PPPOE "dialer" to log into your ISP from your computer. In
    >>>>> this configuration the ISP's DHCP server would give your computer an
    >>>>> internet IP ... i.e.. 68.127.186.115. You would need to set up your
    >>>>> ISP username and password in the PPPOE dialer to log on. Workgroup
    >>>>> related settings in the PC would be irrelevant in this case as long as
    >>>>> the computer can communicate to the modem. The PPPOE dialer is a
    >>>>> virtual device which becomes the effective internet connection. All of
    >>>>> the required settings information would be supplied by the ISP.
    >>>>> Alternatively, a router could be used instead to make the connections
    >>>>> through the modem when it is in this configuration.
    >>>>>
    >>>>> In the second configuration your modem could be set to connect to the
    >>>>> ISP automatically using its own internal firmware. The relevant
    >>>>> networking settings are made in the modem using its web interface,
    >>>>> either by you yourself or sometimes this information is pre-programmed
    >>>>> in the modem by the ISP if they supplied the modem. You can normally
    >>>>> access the modem's web interface using your browser (try typing
    >>>>> 192.168.0.1 in the address bar). The modem could be set to auto-dial
    >>>>> (AKA always-on) or "dial on demand" mode (i.e.. the modem connects
    >>>>> whenever the PC tries to access the internet and can disconnect again
    >>>>> after a set timeout period of no activity). In this configuration it
    >>>>> is the modem which gets the internet IP from your ISP and then passes
    >>>>> the internet connection to the PC through its LAN port at address
    >>>>> 192.168.0.1 (or whatever the default is). Routing and DHCP may or may
    >>>>> not be enabled in the modem, but if they are enabled your computer
    >>>>> should use 192.168.0.1 as its DHCP server address and receive a LAN
    >>>>> address from the modem, not an internet IP. Possibly 192.168.0.1
    >>>>> should be also entered into the computer's TCP/IP settings as the
    >>>>> gateway address if DNS pass-through is enabled in the modem. Otherwise
    >>>>> the ISP's DNS server addresses should be used. If DHCP is not enabled
    >>>>> in the modem you would enter a fixed LAN address into the computer's
    >>>>> TCP/IP configuration, in the range 192.168.0.x. The modem itself might
    >>>>> have an optional workgroup or domain name entered into its LAN
    >>>>> configuration settings, which is where 'JAYS' could be coming from.
    >>>>> You can probably change or eliminate that yourself.
    >>>>>
    >>>>>
    >>>>>
    >>>>>
    >>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>> news:%23ObFDy%23gIHA.5280@TK2MSFTNGP04.phx.gbl...
    >>>>>> No its a dynamic IP Address assigned by my ISP
    >>>>>>
    >>>>>> I have attached all of the event log in the 3 hours around the time
    >>>>>> of the browser conflict below. Im not sure if this contains any
    >>>>>> other information which might give a clue as to what is going on.
    >>>>>>
    >>>>>> Level Date and Time Source Event ID Task Category
    >>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:22:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:17:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:12:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:11:07 PM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the stopped state.
    >>>>>> Information 3/5/2008 12:10:11 PM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the running state.
    >>>>>> Information 3/5/2008 12:07:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:02:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 12:00:46 PM EventLog 6013 None The system uptime
    >>>>>> is 57335 seconds.
    >>>>>> Information 3/5/2008 11:57:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 11:52:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 11:48:19 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 11:47:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 11:43:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 11:42:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 11:37:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 11:37:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 11:32:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 11:32:41 AM Microsoft-Windows-User-PnP 20003
    >>>>>> None Driver Management has concluded the process to add Service
    >>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>> status: 0.
    >>>>>> Information 3/5/2008 11:32:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 11:28:17 AM BROWSER 8033 None The browser has
    >>>>>> forced an election on network
    >>>>>> DeviceNetBT_Tcpip_{6C1B0769-602C-49AD-95C1-0AD3B66DA864} because a
    >>>>>> master browser was stopped.
    >>>>>> Information 3/5/2008 11:24:52 AM Service Control Manager 7036 None
    >>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>> stopped state.
    >>>>>> Information 3/5/2008 11:24:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 11:19:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 11:14:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 11:09:56 AM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the stopped state.
    >>>>>> Information 3/5/2008 11:09:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 11:08:55 AM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the running state.
    >>>>>> Information 3/5/2008 11:08:22 AM Service Control Manager 7036 None
    >>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>> running state.
    >>>>>> Information 3/5/2008 11:05:06 AM volsnap 33 None The oldest shadow
    >>>>>> copy of volume C: was deleted to keep disk space usage for shadow
    >>>>>> copies of volume C: below the user defined limit.
    >>>>>> Information 3/5/2008 11:04:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 10:59:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 10:54:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 10:49:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:45:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Error 3/5/2008 10:45:09 AM BROWSER 8009 None The browser was unable
    >>>>>> to promote itself to master browser. The computer that currently
    >>>>>> believes it is the master browser is JAYS.
    >>>>>> Information 3/5/2008 10:44:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:39:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:39:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:34:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:34:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:29:38 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:29:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:24:28 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:24:21 AM Microsoft-Windows-User-PnP 20003
    >>>>>> None Driver Management has concluded the process to add Service
    >>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>> status: 0.
    >>>>>> Information 3/5/2008 10:24:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 10:18:41 AM Service Control Manager 7036 None
    >>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>> stopped state.
    >>>>>> Error 3/5/2008 10:17:06 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:16:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:11:54 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:11:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:06:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>> None Your computer was successfully assigned an address from the
    >>>>>> network, and it can now connect to other computers.
    >>>>>> Information 3/5/2008 10:05:43 AM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the stopped state.
    >>>>>> Information 3/5/2008 10:05:33 AM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the running state.
    >>>>>> Information 3/5/2008 10:05:26 AM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the stopped state.
    >>>>>> Information 3/5/2008 10:02:39 AM Service Control Manager 7036 None
    >>>>>> The LiveUpdate service entered the running state.
    >>>>>> Information 3/5/2008 10:02:11 AM Service Control Manager 7036 None
    >>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>> running state.
    >>>>>> Information 3/5/2008 10:01:36 AM Microsoft-Windows-User-PnP 20003
    >>>>>> None Driver Management has concluded the process to add Service
    >>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>> status: 0.
    >>>>>> Error 3/5/2008 10:01:30 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>> not allow the name to be claimed by this computer."
    >>>>>> Information 3/5/2008 10:01:17 AM Microsoft-Windows-User-PnP 20003
    >>>>>> None Driver Management has concluded the process to add Service
    >>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the following
    >>>>>> status: 0.
    >>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None
    >>>>>> The IP address lease 192.168.1.64 for the Network Card with network
    >>>>>> address 0016D3A2E7AD has been denied by the DHCP server 192.168.0.1
    >>>>>> (The DHCP Server sent a DHCPNACK message).
    >>>>>> Warning 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1003 None
    >>>>>> "The description for Event ID 1003 from source
    >>>>>> Microsoft-Windows-Dhcp-Client cannot be found. Either the component
    >>>>>> that raises this event is not installed on your local computer or the
    >>>>>> installation is corrupted. You can install or repair the component on
    >>>>>> the local computer.
    >>>>>>
    >>>>>> If the event originated on another computer, the display information
    >>>>>> had to be saved with the event.
    >>>>>>
    >>>>>> The following information was included with the event:
    >>>>>>
    >>>>>> 0016D3A2E7AD
    >>>>>> %%2163146757
    >>>>>>
    >>>>>> The description string for parameter reference (%1) could not be
    >>>>>> found
    >>>>>> "
    >>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 9:57:44 AM Service Control Manager 7036 None The
    >>>>>> LiveUpdate service entered the stopped state.
    >>>>>> Information 3/5/2008 9:57:37 AM Service Control Manager 7036 None The
    >>>>>> LiveUpdate service entered the running state.
    >>>>>> Information 3/5/2008 9:52:42 AM Service Control Manager 7036 None The
    >>>>>> LiveUpdate service entered the stopped state.
    >>>>>> Information 3/5/2008 9:52:35 AM Service Control Manager 7036 None The
    >>>>>> LiveUpdate service entered the running state.
    >>>>>> Information 3/5/2008 9:38:26 AM Service Control Manager 7036 None The
    >>>>>> WinHTTP Web Proxy Auto-Discovery Service service entered the stopped
    >>>>>> state.
    >>>>>> Information 3/5/2008 9:37:56 AM Microsoft-Windows-User-PnP 20003 None
    >>>>>> Driver Management has concluded the process to add Service tunnel for
    >>>>>> Device Instance ID ROOT*ISATAP002 with the following status: 0.
    >>>>>> Information 3/5/2008 9:37:48 AM Service Control Manager 7036 None The
    >>>>>> Windows Image Acquisition (WIA) service entered the running state.
    >>>>>> Information 3/5/2008 9:37:39 AM
    >>>>>> Microsoft-Windows-Power-Troubleshooter 1 None "The system has resumed
    >>>>>> from sleep.
    >>>>>>
    >>>>>> Sleep Time: 3/5/2008 7:12:57 AM
    >>>>>> Wake Time: 3/5/2008 5:37:34 PM
    >>>>>>
    >>>>>> Wake Source: Unknown"
    >>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system detected
    >>>>>> that network adapter Local Area Connection was connected to the
    >>>>>> network, and has initiated normal operation.
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>> "Bob F." <bob@NOSPAN.com> wrote in message
    >>>>>> news:52055B79-F315-4C46-986D-CB8AFBFF2D37@microsoft.com...
    >>>>>>> Where did you get the setup information for your internet
    >>>>>>> connection? Did you use a static IP? Maybe it's incorrect and you
    >>>>>>> are encroaching onto someone else's IP space.
    >>>>>>>
    >>>>>>> --
    >>>>>>> BobF.
    >>>>>>> "Dave" <dave@beepbeep.com> wrote in message
    >>>>>>> news:eBrCR47gIHA.4436@TK2MSFTNGP02.phx.gbl...
    >>>>>>>> What shows up in Start - Network?
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>> news:#orAgk7gIHA.2448@TK2MSFTNGP03.phx.gbl...
    >>>>>>>>> My (lone) machine is connected directly to the DSL router with no
    >>>>>>>>> wireless capabilities on the router. Despite this I get the
    >>>>>>>>> following message in the event log:
    >>>>>>>>>
    >>>>>>>>> The browser was unable to promote itself to master browser. The
    >>>>>>>>> computer that currently believes it is the master browser is JAYS.
    >>>>>>>>>
    >>>>>>>>> Once again, my computer is not called JAYS. Friends and family
    >>>>>>>>> are not Vista Security experts. Looking for capable / expert
    >>>>>>>>> advice from this forum.
    >>>>>>>>>
    >>>>>>>>> What are the possible explanations for this???
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> "Malke" <malke@invalid.invalid> wrote in message
    >>>>>>>>> news:O5eVD62gIHA.4692@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>>> Nubie wrote:
    >>>>>>>>>>
    >>>>>>>>>>> What should I be looking for in the Settings?
    >>>>>>>>>>>
    >>>>>>>>>>> ALSO: How would the config of my DSL modem confuse my vista
    >>>>>>>>>>> machine to
    >>>>>>>>>>> think that there is another computer called JAYS on my local
    >>>>>>>>>>> network.
    >>>>>>>>>>
    >>>>>>>>>>>> Nubie;642434 Wrote:
    >>>>>>>>>>>>> Hi
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> I have a single (lone) windows Vista machine connected
    >>>>>>>>>>>>> directly to the
    >>>>>>>>>>>>> internet via a dsl modem. I just viewed the following in my
    >>>>>>>>>>>>> eventlogs:
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> "The browser was unable to promote itself to master browser.
    >>>>>>>>>>>>> The
    >>>>>>>>>>>>> computer
    >>>>>>>>>>>>> that
    >>>>>>>>>>>>> currently believes it is the master browser is JAYS. My
    >>>>>>>>>>>>> machine is NOT
    >>>>>>>>>>>>> called JAYS."
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> What is happening here!!?? If my machine is connected to a DSL
    >>>>>>>>>>>>> modem
    >>>>>>>>>>>>> with
    >>>>>>>>>>>>> no additional
    >>>>>>>>>>>>> machines connected to that modem why is this message appearing
    >>>>>>>>>>>>> ????
    >>>>>>>>>>>>> What is
    >>>>>>>>>>>>> happening here ??
    >>>>>>>>>>
    >>>>>>>>>> It certainly seems as though someone else is on your network. Is
    >>>>>>>>>> this a
    >>>>>>>>>> combination modem/wireless router? If yes, you probably haven't
    >>>>>>>>>> secured
    >>>>>>>>>> your wireless properly and a stranger is using your bandwidth. If
    >>>>>>>>>> you only
    >>>>>>>>>> have a single computer connected directly to a DSL modem by
    >>>>>>>>>> ethernet cable
    >>>>>>>>>> (no wireless router), then call your ISP. Because you don't
    >>>>>>>>>> really know
    >>>>>>>>>> what you're looking at - and I mean no disrespect to you, I'm
    >>>>>>>>>> just being
    >>>>>>>>>> practical - it might be smart for you to have a computer
    >>>>>>>>>> professional come
    >>>>>>>>>> on-site and take a look. This will not be someone from a
    >>>>>>>>>> BigComputerStore/GeekSquad type of place. Get recommendations
    >>>>>>>>>> from friends,
    >>>>>>>>>> family, colleagues.
    >>>>>>>>>>
    >>>>>>>>>> Malke
    >>>>>>>>>> --
    >>>>>>>>>> MS-MVP
    >>>>>>>>>> Elephant Boy Computers
    >>>>>>>>>>
    >>>>>>>>>> Don't Panic!
    >>>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>><!--colorc--><!--/colorc-->
    >><!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     
    Nubie, Mar 14, 2008
    #23
  5. RalfG

    RalfG Guest

    Looks like a bit of a dog's breakfast. :)
    Questionable entries marked with -******************

    You said earlier that the computer was getting a dynamic IP from your ISP
    but the way it is configured below I can't see that happening reliably.
    You've got two conflicting DHCP services active.
    The default Gateway is set to an internet IP but the DHCP server listed is
    the modem/router, which presumable can only supply LAN addresses within its
    own network subnet (192.168.0.x). Your ISP will have it's own dedicated DHCP
    servers which are on internet IPs. That is where the 68.127.175.71 address
    came from. Aside from that the modem's internal DHCP server wouldn't know
    which internet IPs were available and which ones were already being assigned
    to someone else. This could be where your mystery connection is being
    created. Also the subnet mask for your internet IP is set for the
    192.168.0.x subnet rather than for internet which is not okay.

    Your DNS server is set to a local LAN address (192.168.0.1) rather than the
    ISP's DNS servers, which is probably okay if the modem/router has the real
    DNS server addresses and DNS forwarding is enabled. Otherwise these lines
    should be showing two different IPs from your ISP. NetBios is enabled on
    your ethernet TCP/IP adapter but without NAT or firewall protection in the
    modem/router this is not a good idea over an open internet connection.

    It looks like the modem/router's actual LAN IP is 192.168.0.1. That's the
    address you should browse to in IE to access the modem's configuration
    pages. How you need to configure the computer's network settings depends on
    how the modem has been configured but I think at the very least you should
    be disabling the modem's onboard DHCP server if your computer's adapter is
    intended to get an address automatically from your ISP. Setting the router's
    DNS to pass-through mode rather than forwarding isn't absolutely necessary
    but it eliminates the extra rerouting step. In the various DNS Suffix lines
    I'd expect to see entries referencing your ISP's domain name. I suspect the
    tunnel adapters listed below are just redundant.


    "Nubie" <newsgoup_contact@atigen.com> wrote in message
    news:O3ZdjXihIHA.200@TK2MSFTNGP02.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    > Windows IP Configuration
    >
    > Host Name . . . . . . . . . . . . : mypc
    > Primary Dns Suffix . . . . . . . :
    > Node Type . . . . . . . . . . . . : Hybrid
    > IP Routing Enabled. . . . . . . . : No
    > WINS Proxy Enabled. . . . . . . . : No
    > DNS Suffix Search List. . . . . . :
    > domain_not_set.invalid--*******************
    >
    > Ethernet adapter Local Area Connection:
    >
    > Connection-specific DNS Suffix . :
    > domain_not_set.invalid---************************
    > Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
    > Physical Address. . . . . . . . . : 00-16-D3-A2-E7-AD
    > DHCP Enabled. . . . . . . . . . . : Yes
    > Autoconfiguration Enabled . . . . : Yes
    > Link-local IPv6 Address . . . . . :
    > ff80::80f6:625f:f376:8301%6(Preferred)
    > IPv4 Address. . . . . . . . . . . : 68.127.175.71(Preferred)
    > Subnet Mask . . . . . . . . . . . :
    > 255.255.255.0 --*********************
    > Lease Obtained. . . . . . . . . . : Friday, March 14, 2008 12:05:54 PM
    > Lease Expires . . . . . . . . . . : Friday, March 14, 2008 3:41:18 PM
    > Default Gateway . . . . . . . . . : 68.127.175.72
    > DHCP Server . . . . . . . . . . . : 192.168.0.1--*********************
    > DHCPv6 IAID . . . . . . . . . . . : 203332435
    > DNS Servers . . . . . . . . . . . : 192.168.0.1--*********************
    > 192.168.0.1--*********************
    > NetBIOS over Tcpip. . . . . . . . : Enabled
    >
    > Tunnel adapter Local Area Connection* 6:
    >
    > Connection-specific DNS Suffix . : domain_not_set.invalid
    > Description . . . . . . . . . . . : isatap.domain_not_set.invalid
    > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    > DHCP Enabled. . . . . . . . . . . : No
    > Autoconfiguration Enabled . . . . : Yes
    > Link-local IPv6 Address . . . . . :
    > ff80::200:5fff:68.128.185.71%14(Preferred
    > )
    > Default Gateway . . . . . . . . . :
    > DNS Servers . . . . . . . . . . . : 192.168.0.1--******************
    > 192.168.0.1--********************
    > NetBIOS over Tcpip. . . . . . . . : Disabled
    >
    > Tunnel adapter Local Area Connection* 7:
    >
    > Connection-specific DNS Suffix . :
    > Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    > Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    > DHCP Enabled. . . . . . . . . . . : No
    > Autoconfiguration Enabled . . . . : Yes
    > IPv6 Address. . . . . . . . . . . :
    > 2001:0:4337:9f66:18f9:3343:ff80:50f8(Pref
    > erred)
    > Link-local IPv6 Address . . . . . :
    > ff80::38f9:3343:ff80:50f8%12(Preferred)
    > Default Gateway . . . . . . . . . :
    > NetBIOS over Tcpip. . . . . . . . : Disabled
    >
    > Tunnel adapter Local Area Connection* 14:
    >
    > Media State . . . . . . . . . . . : Media disconnected
    > Connection-specific DNS Suffix . :
    > Description . . . . . . . . . . . : 6TO4 Adapter
    > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    > DHCP Enabled. . . . . . . . . . . : No
    > Autoconfiguration Enabled . . . . : Yes
    >
    > Tunnel adapter Local Area Connection* 10:
    >
    > Connection-specific DNS Suffix . : domain_not_set.invalid
    > Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
    > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    > DHCP Enabled. . . . . . . . . . . : No
    > Autoconfiguration Enabled . . . . : Yes
    > Temporary IPv6 Address. . . . . . : 2002:227f:ff27::227f:ff27(Preferred)
    > Default Gateway . . . . . . . . . : 2002:f058:6301::f058:6301
    > DNS Servers . . . . . . . . . . . : 192.168.0.1---*******************
    >
    > 192.168.0.1--*************************
    > NetBIOS over Tcpip. . . . . . . . : Disabled
    >
    >
    >
    >
    > "RalfG" <itsnotme@ladeda.deda> wrote in message
    > news:C5E12624-0EEF-4A6D-84C9-AF9BB6440665@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> Open a command prompt and enter "ipconfig /all", without the quotes. What
    >> do you get?
    >>
    >> Other points in-line below.
    >>
    >> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >> news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> 0016D3A2E7AD is my machines regular (wire) network card. The wireless
    >>> card is disabled in device manager (which presumably rules any wireles
    >>> connection out). 68.127.186.255 is AT&T's network, which is my ISP
    >>> (ARIN lookup below):
    >>>
    >>> AT&T Internet Services SBCIS-SIS80 (NET-68-120-0-0-1)
    >>> 68.120.0.0 - 68.127.255.255
    >>> bras4.pltnca SBC068127176000040211 (NET-68-127-176-0-1)
    >>> 68.127.176.0 - 68.127.191.255
    >>>
    >>> The constantly repeating reconnection notices at 5 minute intervals,
    >>> (with resulting successfully assigned IP addresses), is probably a
    >>> result of the fact that I remove the ethernet cable from my network card
    >>> whenever I step away from my machine.<!--colorc--><!--/colorc-->
    >>
    >> You really shouldn't do that. Only USB is generally safe to hot-plug.
    >> Sooner or later you're luck will run out and one or the other ethernet
    >> devices will fry. That aside, unplugging it doesn't account for those
    >> repeating reconnections. The timing is too consistent, down to the
    >> second.
    >><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>
    >>> The only other remotely possible connection to my PC would have been
    >>> bluetooth, however the wireless card which provides bluetooth
    >>> connectivity is always turned off (at the switch).
    >>>
    >>> This leaves 2 questions
    >>>
    >>> 1) How could there be a master browser called JAYS showing up on my logs
    >>> (given the above).<!--colorc--><!--/colorc-->
    >>
    >> You would both have to be peers connected on the same LAN or directly to
    >> each other (same thing). Any PC on a LAN can be a master browser. I have
    >> one XP PC on mine that always insists on taking that status when it joins
    >> the LAN.
    >><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> and (less importantly)
    >>>
    >>> 2) Why is my machine having a conversation with the outside world (my
    >>> ISP) about its workgroup. My understanding was that a workgroup would
    >>> be something that would be limited to my LAN alone.<!--colorc--><!--/colorc-->
    >>
    >> Let's see what ipconfig shows.
    >><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>
    >>>
    >>>
    >>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>> news:6AD5B7D8-0DFF-4421-8DF9-3FF57637594C@microsoft.com...
    >>>> The anomalous name being in the router was only a suggestion, it's an
    >>>> option in mine that could also be in yours. As far as not finding the
    >>>> LAN DHCP server in the netbios table, this ....
    >>>>
    >>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None The
    >>>> IP
    >>>>>>> address lease 192.168.1.64 for the Network Card with network address
    >>>>>>> 0016D3A2E7AD has been denied by the DHCP server 192.168.0.1 (The
    >>>>>>> DHCP Server sent a DHCPNACK message).
    >>>>
    >>>> says that it exists, at least some of the time, and that your computer
    >>>> tried to use it with an incorrect network address and got booted. This
    >>>> on the other hand....
    >>>>
    >>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>>>> could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>
    >>>> says your computer subsequently tried to connect to a server on the
    >>>> internet, probably your ISP, possibly somewhere else. There's no
    >>>> indication here whether it is the same network adapter making the
    >>>> connection as the one above but we can see from the text that your
    >>>> network adapter in this case also "somehow" had some incorrect
    >>>> information set in its configuration at the time.
    >>>>
    >>>> OTOH these constantly repeating reconnection notices at 5 minute
    >>>> intervals....
    >>>>
    >>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>
    >>>> Are very much like what you can see happening with wireless
    >>>> connections. If I were going to make a guess as to what is going on
    >>>> here I'd say that apart from the ethernet adapter you connect to your
    >>>> own modem with you do have a wireless adapter in that computer, it is
    >>>> always turned on and it is set to automatically connect to any
    >>>> available network. Every so often your PC is piggybacking a ride, or
    >>>> trying to, on poor JAYS wireless network. :)
    >>>>
    >>>>
    >>>>
    >>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>> news:OUZ0QCKhIHA.4740@TK2MSFTNGP05.phx.gbl...
    >>>>>
    >>>>> If JAYS were the name of the modem or in its netbios table, then it
    >>>>> should still be there presumably. (I have not reconfigured the modem
    >>>>> in several months, and at that I time I set it to factory defaults -
    >>>>> so the name JAYS should not be assigned to the modem).
    >>>>>
    >>>>> I checked the mode that the modem is operating. This is as follows:
    >>>>>
    >>>>> PPP is on the modem. (PPP session is initiated from the modem.) - i.e.
    >>>>> Not operating in Bridging mode
    >>>>>
    >>>>> I believe my DHCP server is assigned by the gateway, when I connect
    >>>>> (i.e. no static IP configured on my machine).
    >>>>>
    >>>>> I did a lookup of the netbios name table on my PC which I listed below
    >>>>> (When I tried nbtstat -a 192.168.0.1 for the modem I got "host not
    >>>>> found").
    >>>>>
    >>>>>
    >>>>> NetBIOS Local Name Table
    >>>>>
    >>>>> Name Type Status
    >>>>> ---------------------------------------------
    >>>>> MYPC <00> UNIQUE Registered
    >>>>> WORKGROUP <00> GROUP Registered
    >>>>> MYPC <20> UNIQUE Registered
    >>>>> WORKGROUP <1E> GROUP Registered
    >>>>> WORKGROUP <1D> UNIQUE Registered
    >>>>> ..__MSBROWSE__. <01> GROUP Registered
    >>>>>
    >>>>>
    >>>>>
    >>>>>
    >>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>> news:EBF529EE-1C6A-4D4F-BB48-82EA200A86A9@microsoft.com...
    >>>>>> It looks like your network connection may be misconfigured. From the
    >>>>>> events at timestamp 10:01 and later it appears you have two
    >>>>>> conflicting DHCP services being used. You have a DHCP server at
    >>>>>> 192.168.0.1 which I presume is the DSL Modem with routing
    >>>>>> capabilities enabled. You are also trying to get a DHCP address
    >>>>>> directly from your ISP, probably using IP 68.127.186.255 as the DHCP
    >>>>>> server address. You should use only one or the other. I'd try turning
    >>>>>> off DHCP in the modem first and see how that works out.
    >>>>>>
    >>>>>> The modem can probably be configured in several different operating
    >>>>>> modes. I have no way of knowing what your available options are or
    >>>>>> which mode has been enabled. My own has 4 distinct DSL operating
    >>>>>> modes plus various combinations of routing and firewall features.
    >>>>>> IOW, there are umpteen ways to screw up the connection. :)
    >>>>>>
    >>>>>> Typically there are two common connection modes that might be used.
    >>>>>> One way is to have the modem set in 'bridge" mode, where it only
    >>>>>> makes the hardware connection to the DSL carrier signal. You would
    >>>>>> Windows built in PPPOE "dialer" to log into your ISP from your
    >>>>>> computer. In this configuration the ISP's DHCP server would give
    >>>>>> your computer an internet IP ... i.e.. 68.127.186.115. You would need
    >>>>>> to set up your ISP username and password in the PPPOE dialer to log
    >>>>>> on. Workgroup related settings in the PC would be irrelevant in this
    >>>>>> case as long as the computer can communicate to the modem. The PPPOE
    >>>>>> dialer is a virtual device which becomes the effective internet
    >>>>>> connection. All of the required settings information would be
    >>>>>> supplied by the ISP. Alternatively, a router could be used instead to
    >>>>>> make the connections through the modem when it is in this
    >>>>>> configuration.
    >>>>>>
    >>>>>> In the second configuration your modem could be set to connect to the
    >>>>>> ISP automatically using its own internal firmware. The relevant
    >>>>>> networking settings are made in the modem using its web interface,
    >>>>>> either by you yourself or sometimes this information is
    >>>>>> pre-programmed in the modem by the ISP if they supplied the modem.
    >>>>>> You can normally access the modem's web interface using your browser
    >>>>>> (try typing 192.168.0.1 in the address bar). The modem could be set
    >>>>>> to auto-dial (AKA always-on) or "dial on demand" mode (i.e.. the
    >>>>>> modem connects whenever the PC tries to access the internet and can
    >>>>>> disconnect again after a set timeout period of no activity). In this
    >>>>>> configuration it is the modem which gets the internet IP from your
    >>>>>> ISP and then passes the internet connection to the PC through its LAN
    >>>>>> port at address 192.168.0.1 (or whatever the default is). Routing and
    >>>>>> DHCP may or may not be enabled in the modem, but if they are enabled
    >>>>>> your computer should use 192.168.0.1 as its DHCP server address and
    >>>>>> receive a LAN address from the modem, not an internet IP. Possibly
    >>>>>> 192.168.0.1 should be also entered into the computer's TCP/IP
    >>>>>> settings as the gateway address if DNS pass-through is enabled in the
    >>>>>> modem. Otherwise the ISP's DNS server addresses should be used. If
    >>>>>> DHCP is not enabled in the modem you would enter a fixed LAN address
    >>>>>> into the computer's TCP/IP configuration, in the range 192.168.0.x.
    >>>>>> The modem itself might have an optional workgroup or domain name
    >>>>>> entered into its LAN configuration settings, which is where 'JAYS'
    >>>>>> could be coming from. You can probably change or eliminate that
    >>>>>> yourself.
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>> news:%23ObFDy%23gIHA.5280@TK2MSFTNGP04.phx.gbl...
    >>>>>>> No its a dynamic IP Address assigned by my ISP
    >>>>>>>
    >>>>>>> I have attached all of the event log in the 3 hours around the time
    >>>>>>> of the browser conflict below. Im not sure if this contains any
    >>>>>>> other information which might give a clue as to what is going on.
    >>>>>>>
    >>>>>>> Level Date and Time Source Event ID Task Category
    >>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 12:22:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 12:17:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 12:12:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 12:11:07 PM Service Control Manager 7036 None
    >>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>> Information 3/5/2008 12:10:11 PM Service Control Manager 7036 None
    >>>>>>> The LiveUpdate service entered the running state.
    >>>>>>> Information 3/5/2008 12:07:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 12:02:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 12:00:46 PM EventLog 6013 None The system
    >>>>>>> uptime is 57335 seconds.
    >>>>>>> Information 3/5/2008 11:57:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 11:52:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Error 3/5/2008 11:48:19 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Information 3/5/2008 11:47:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Error 3/5/2008 11:43:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Information 3/5/2008 11:42:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Error 3/5/2008 11:37:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Information 3/5/2008 11:37:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Error 3/5/2008 11:32:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Information 3/5/2008 11:32:41 AM Microsoft-Windows-User-PnP 20003
    >>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>> status: 0.
    >>>>>>> Information 3/5/2008 11:32:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system detected
    >>>>>>> that network adapter Local Area Connection was connected to the
    >>>>>>> network, and has initiated normal operation.
    >>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system detected
    >>>>>>> that network adapter Local Area Connection was connected to the
    >>>>>>> network, and has initiated normal operation.
    >>>>>>> Information 3/5/2008 11:28:17 AM BROWSER 8033 None The browser has
    >>>>>>> forced an election on network
    >>>>>>> DeviceNetBT_Tcpip_{6C1B0769-602C-49AD-95C1-0AD3B66DA864} because a
    >>>>>>> master browser was stopped.
    >>>>>>> Information 3/5/2008 11:24:52 AM Service Control Manager 7036 None
    >>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>> stopped state.
    >>>>>>> Information 3/5/2008 11:24:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 11:19:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 11:14:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 11:09:56 AM Service Control Manager 7036 None
    >>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>> Information 3/5/2008 11:09:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 11:08:55 AM Service Control Manager 7036 None
    >>>>>>> The LiveUpdate service entered the running state.
    >>>>>>> Information 3/5/2008 11:08:22 AM Service Control Manager 7036 None
    >>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>> running state.
    >>>>>>> Information 3/5/2008 11:05:06 AM volsnap 33 None The oldest shadow
    >>>>>>> copy of volume C: was deleted to keep disk space usage for shadow
    >>>>>>> copies of volume C: below the user defined limit.
    >>>>>>> Information 3/5/2008 11:04:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 10:59:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 10:54:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 10:49:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Error 3/5/2008 10:45:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Error 3/5/2008 10:45:09 AM BROWSER 8009 None The browser was unable
    >>>>>>> to promote itself to master browser. The computer that currently
    >>>>>>> believes it is the master browser is JAYS.
    >>>>>>> Information 3/5/2008 10:44:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Error 3/5/2008 10:39:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Information 3/5/2008 10:39:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Error 3/5/2008 10:34:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Information 3/5/2008 10:34:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Error 3/5/2008 10:29:38 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Information 3/5/2008 10:29:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Error 3/5/2008 10:24:28 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Information 3/5/2008 10:24:21 AM Microsoft-Windows-User-PnP 20003
    >>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>> status: 0.
    >>>>>>> Information 3/5/2008 10:24:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system detected
    >>>>>>> that network adapter Local Area Connection was connected to the
    >>>>>>> network, and has initiated normal operation.
    >>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system detected
    >>>>>>> that network adapter Local Area Connection was connected to the
    >>>>>>> network, and has initiated normal operation.
    >>>>>>> Information 3/5/2008 10:18:41 AM Service Control Manager 7036 None
    >>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>> stopped state.
    >>>>>>> Error 3/5/2008 10:17:06 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Information 3/5/2008 10:16:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Error 3/5/2008 10:11:54 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Information 3/5/2008 10:11:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Information 3/5/2008 10:06:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>> network, and it can now connect to other computers.
    >>>>>>> Information 3/5/2008 10:05:43 AM Service Control Manager 7036 None
    >>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>> Information 3/5/2008 10:05:33 AM Service Control Manager 7036 None
    >>>>>>> The LiveUpdate service entered the running state.
    >>>>>>> Information 3/5/2008 10:05:26 AM Service Control Manager 7036 None
    >>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>> Information 3/5/2008 10:02:39 AM Service Control Manager 7036 None
    >>>>>>> The LiveUpdate service entered the running state.
    >>>>>>> Information 3/5/2008 10:02:11 AM Service Control Manager 7036 None
    >>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>> running state.
    >>>>>>> Information 3/5/2008 10:01:36 AM Microsoft-Windows-User-PnP 20003
    >>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>> status: 0.
    >>>>>>> Error 3/5/2008 10:01:30 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>> not allow the name to be claimed by this computer."
    >>>>>>> Information 3/5/2008 10:01:17 AM Microsoft-Windows-User-PnP 20003
    >>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the following
    >>>>>>> status: 0.
    >>>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None
    >>>>>>> The IP address lease 192.168.1.64 for the Network Card with network
    >>>>>>> address 0016D3A2E7AD has been denied by the DHCP server 192.168.0.1
    >>>>>>> (The DHCP Server sent a DHCPNACK message).
    >>>>>>> Warning 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1003 None
    >>>>>>> "The description for Event ID 1003 from source
    >>>>>>> Microsoft-Windows-Dhcp-Client cannot be found. Either the component
    >>>>>>> that raises this event is not installed on your local computer or
    >>>>>>> the installation is corrupted. You can install or repair the
    >>>>>>> component on the local computer.
    >>>>>>>
    >>>>>>> If the event originated on another computer, the display information
    >>>>>>> had to be saved with the event.
    >>>>>>>
    >>>>>>> The following information was included with the event:
    >>>>>>>
    >>>>>>> 0016D3A2E7AD
    >>>>>>> %%2163146757
    >>>>>>>
    >>>>>>> The description string for parameter reference (%1) could not be
    >>>>>>> found
    >>>>>>> "
    >>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system detected
    >>>>>>> that network adapter Local Area Connection was connected to the
    >>>>>>> network, and has initiated normal operation.
    >>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system detected
    >>>>>>> that network adapter Local Area Connection was connected to the
    >>>>>>> network, and has initiated normal operation.
    >>>>>>> Information 3/5/2008 9:57:44 AM Service Control Manager 7036 None
    >>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>> Information 3/5/2008 9:57:37 AM Service Control Manager 7036 None
    >>>>>>> The LiveUpdate service entered the running state.
    >>>>>>> Information 3/5/2008 9:52:42 AM Service Control Manager 7036 None
    >>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>> Information 3/5/2008 9:52:35 AM Service Control Manager 7036 None
    >>>>>>> The LiveUpdate service entered the running state.
    >>>>>>> Information 3/5/2008 9:38:26 AM Service Control Manager 7036 None
    >>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>> stopped state.
    >>>>>>> Information 3/5/2008 9:37:56 AM Microsoft-Windows-User-PnP 20003
    >>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the following
    >>>>>>> status: 0.
    >>>>>>> Information 3/5/2008 9:37:48 AM Service Control Manager 7036 None
    >>>>>>> The Windows Image Acquisition (WIA) service entered the running
    >>>>>>> state.
    >>>>>>> Information 3/5/2008 9:37:39 AM
    >>>>>>> Microsoft-Windows-Power-Troubleshooter 1 None "The system has
    >>>>>>> resumed from sleep.
    >>>>>>>
    >>>>>>> Sleep Time: 3/5/2008 7:12:57 AM
    >>>>>>> Wake Time: 3/5/2008 5:37:34 PM
    >>>>>>>
    >>>>>>> Wake Source: Unknown"
    >>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system detected
    >>>>>>> that network adapter Local Area Connection was connected to the
    >>>>>>> network, and has initiated normal operation.
    >>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system detected
    >>>>>>> that network adapter Local Area Connection was connected to the
    >>>>>>> network, and has initiated normal operation.
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>> "Bob F." <bob@NOSPAN.com> wrote in message
    >>>>>>> news:52055B79-F315-4C46-986D-CB8AFBFF2D37@microsoft.com...
    >>>>>>>> Where did you get the setup information for your internet
    >>>>>>>> connection? Did you use a static IP? Maybe it's incorrect and you
    >>>>>>>> are encroaching onto someone else's IP space.
    >>>>>>>>
    >>>>>>>> --
    >>>>>>>> BobF.
    >>>>>>>> "Dave" <dave@beepbeep.com> wrote in message
    >>>>>>>> news:eBrCR47gIHA.4436@TK2MSFTNGP02.phx.gbl...
    >>>>>>>>> What shows up in Start - Network?
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>>> news:#orAgk7gIHA.2448@TK2MSFTNGP03.phx.gbl...
    >>>>>>>>>> My (lone) machine is connected directly to the DSL router with no
    >>>>>>>>>> wireless capabilities on the router. Despite this I get the
    >>>>>>>>>> following message in the event log:
    >>>>>>>>>>
    >>>>>>>>>> The browser was unable to promote itself to master browser. The
    >>>>>>>>>> computer that currently believes it is the master browser is
    >>>>>>>>>> JAYS.
    >>>>>>>>>>
    >>>>>>>>>> Once again, my computer is not called JAYS. Friends and family
    >>>>>>>>>> are not Vista Security experts. Looking for capable / expert
    >>>>>>>>>> advice from this forum.
    >>>>>>>>>>
    >>>>>>>>>> What are the possible explanations for this???
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>> "Malke" <malke@invalid.invalid> wrote in message
    >>>>>>>>>> news:O5eVD62gIHA.4692@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>>>> Nubie wrote:
    >>>>>>>>>>>
    >>>>>>>>>>>> What should I be looking for in the Settings?
    >>>>>>>>>>>>
    >>>>>>>>>>>> ALSO: How would the config of my DSL modem confuse my vista
    >>>>>>>>>>>> machine to
    >>>>>>>>>>>> think that there is another computer called JAYS on my local
    >>>>>>>>>>>> network.
    >>>>>>>>>>>
    >>>>>>>>>>>>> Nubie;642434 Wrote:
    >>>>>>>>>>>>>> Hi
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> I have a single (lone) windows Vista machine connected
    >>>>>>>>>>>>>> directly to the
    >>>>>>>>>>>>>> internet via a dsl modem. I just viewed the following in my
    >>>>>>>>>>>>>> eventlogs:
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> "The browser was unable to promote itself to master browser.
    >>>>>>>>>>>>>> The
    >>>>>>>>>>>>>> computer
    >>>>>>>>>>>>>> that
    >>>>>>>>>>>>>> currently believes it is the master browser is JAYS. My
    >>>>>>>>>>>>>> machine is NOT
    >>>>>>>>>>>>>> called JAYS."
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> What is happening here!!?? If my machine is connected to a
    >>>>>>>>>>>>>> DSL modem
    >>>>>>>>>>>>>> with
    >>>>>>>>>>>>>> no additional
    >>>>>>>>>>>>>> machines connected to that modem why is this message
    >>>>>>>>>>>>>> appearing ????
    >>>>>>>>>>>>>> What is
    >>>>>>>>>>>>>> happening here ??
    >>>>>>>>>>>
    >>>>>>>>>>> It certainly seems as though someone else is on your network. Is
    >>>>>>>>>>> this a
    >>>>>>>>>>> combination modem/wireless router? If yes, you probably haven't
    >>>>>>>>>>> secured
    >>>>>>>>>>> your wireless properly and a stranger is using your bandwidth.
    >>>>>>>>>>> If you only
    >>>>>>>>>>> have a single computer connected directly to a DSL modem by
    >>>>>>>>>>> ethernet cable
    >>>>>>>>>>> (no wireless router), then call your ISP. Because you don't
    >>>>>>>>>>> really know
    >>>>>>>>>>> what you're looking at - and I mean no disrespect to you, I'm
    >>>>>>>>>>> just being
    >>>>>>>>>>> practical - it might be smart for you to have a computer
    >>>>>>>>>>> professional come
    >>>>>>>>>>> on-site and take a look. This will not be someone from a
    >>>>>>>>>>> BigComputerStore/GeekSquad type of place. Get recommendations
    >>>>>>>>>>> from friends,
    >>>>>>>>>>> family, colleagues.
    >>>>>>>>>>>
    >>>>>>>>>>> Malke
    >>>>>>>>>>> --
    >>>>>>>>>>> MS-MVP
    >>>>>>>>>>> Elephant Boy Computers
    >>>>>>>>>>>
    >>>>>>>>>>> Don't Panic!
    >>>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>><!--colorc--><!--/colorc-->
    >><!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     
    RalfG, Mar 15, 2008
    #24
  6. Bob F.

    Bob F. Guest

    This one looks totally lost. I'd take all your components back to factory
    defaults and start from there again. It'll probably come up all by itself,
    or with minor tweaks.
    --
    BobF.
    "RalfG" <itsnotme@ladeda.deda> wrote in message
    news:C7150467-0DF3-49C9-BFFD-3D3B960F5041@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Looks like a bit of a dog's breakfast. :)
    > Questionable entries marked with -******************
    >
    > You said earlier that the computer was getting a dynamic IP from your ISP
    > but the way it is configured below I can't see that happening reliably.
    > You've got two conflicting DHCP services active.
    > The default Gateway is set to an internet IP but the DHCP server listed is
    > the modem/router, which presumable can only supply LAN addresses within
    > its own network subnet (192.168.0.x). Your ISP will have it's own
    > dedicated DHCP servers which are on internet IPs. That is where the
    > 68.127.175.71 address came from. Aside from that the modem's internal
    > DHCP server wouldn't know which internet IPs were available and which ones
    > were already being assigned to someone else. This could be where your
    > mystery connection is being created. Also the subnet mask for your
    > internet IP is set for the 192.168.0.x subnet rather than for internet
    > which is not okay.
    >
    > Your DNS server is set to a local LAN address (192.168.0.1) rather than
    > the ISP's DNS servers, which is probably okay if the modem/router has the
    > real DNS server addresses and DNS forwarding is enabled. Otherwise these
    > lines should be showing two different IPs from your ISP. NetBios is
    > enabled on your ethernet TCP/IP adapter but without NAT or firewall
    > protection in the modem/router this is not a good idea over an open
    > internet connection.
    >
    > It looks like the modem/router's actual LAN IP is 192.168.0.1. That's the
    > address you should browse to in IE to access the modem's configuration
    > pages. How you need to configure the computer's network settings depends
    > on how the modem has been configured but I think at the very least you
    > should be disabling the modem's onboard DHCP server if your computer's
    > adapter is intended to get an address automatically from your ISP. Setting
    > the router's DNS to pass-through mode rather than forwarding isn't
    > absolutely necessary but it eliminates the extra rerouting step. In the
    > various DNS Suffix lines I'd expect to see entries referencing your ISP's
    > domain name. I suspect the tunnel adapters listed below are just
    > redundant.
    >
    >
    > "Nubie" <newsgoup_contact@atigen.com> wrote in message
    > news:O3ZdjXihIHA.200@TK2MSFTNGP02.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    >>
    >> Windows IP Configuration
    >>
    >> Host Name . . . . . . . . . . . . : mypc
    >> Primary Dns Suffix . . . . . . . :
    >> Node Type . . . . . . . . . . . . : Hybrid
    >> IP Routing Enabled. . . . . . . . : No
    >> WINS Proxy Enabled. . . . . . . . : No
    >> DNS Suffix Search List. . . . . . :
    >> domain_not_set.invalid--*******************
    >>
    >> Ethernet adapter Local Area Connection:
    >>
    >> Connection-specific DNS Suffix . :
    >> domain_not_set.invalid---************************
    >> Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
    >> Physical Address. . . . . . . . . : 00-16-D3-A2-E7-AD
    >> DHCP Enabled. . . . . . . . . . . : Yes
    >> Autoconfiguration Enabled . . . . : Yes
    >> Link-local IPv6 Address . . . . . :
    >> ff80::80f6:625f:f376:8301%6(Preferred)
    >> IPv4 Address. . . . . . . . . . . : 68.127.175.71(Preferred)
    >> Subnet Mask . . . . . . . . . . . :
    >> 255.255.255.0 --*********************
    >> Lease Obtained. . . . . . . . . . : Friday, March 14, 2008 12:05:54 PM
    >> Lease Expires . . . . . . . . . . : Friday, March 14, 2008 3:41:18 PM
    >> Default Gateway . . . . . . . . . : 68.127.175.72
    >> DHCP Server . . . . . . . . . . . : 192.168.0.1--*********************
    >> DHCPv6 IAID . . . . . . . . . . . : 203332435
    >> DNS Servers . . . . . . . . . . . : 192.168.0.1--*********************
    >> 192.168.0.1--*********************
    >> NetBIOS over Tcpip. . . . . . . . : Enabled
    >>
    >> Tunnel adapter Local Area Connection* 6:
    >>
    >> Connection-specific DNS Suffix . : domain_not_set.invalid
    >> Description . . . . . . . . . . . : isatap.domain_not_set.invalid
    >> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >> DHCP Enabled. . . . . . . . . . . : No
    >> Autoconfiguration Enabled . . . . : Yes
    >> Link-local IPv6 Address . . . . . :
    >> ff80::200:5fff:68.128.185.71%14(Preferred
    >> )
    >> Default Gateway . . . . . . . . . :
    >> DNS Servers . . . . . . . . . . . : 192.168.0.1--******************
    >> 192.168.0.1--********************
    >> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>
    >> Tunnel adapter Local Area Connection* 7:
    >>
    >> Connection-specific DNS Suffix . :
    >> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    >> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    >> DHCP Enabled. . . . . . . . . . . : No
    >> Autoconfiguration Enabled . . . . : Yes
    >> IPv6 Address. . . . . . . . . . . :
    >> 2001:0:4337:9f66:18f9:3343:ff80:50f8(Pref
    >> erred)
    >> Link-local IPv6 Address . . . . . :
    >> ff80::38f9:3343:ff80:50f8%12(Preferred)
    >> Default Gateway . . . . . . . . . :
    >> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>
    >> Tunnel adapter Local Area Connection* 14:
    >>
    >> Media State . . . . . . . . . . . : Media disconnected
    >> Connection-specific DNS Suffix . :
    >> Description . . . . . . . . . . . : 6TO4 Adapter
    >> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >> DHCP Enabled. . . . . . . . . . . : No
    >> Autoconfiguration Enabled . . . . : Yes
    >>
    >> Tunnel adapter Local Area Connection* 10:
    >>
    >> Connection-specific DNS Suffix . : domain_not_set.invalid
    >> Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
    >> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >> DHCP Enabled. . . . . . . . . . . : No
    >> Autoconfiguration Enabled . . . . : Yes
    >> Temporary IPv6 Address. . . . . . :
    >> 2002:227f:ff27::227f:ff27(Preferred)
    >> Default Gateway . . . . . . . . . : 2002:f058:6301::f058:6301
    >> DNS Servers . . . . . . . . . . . : 192.168.0.1---*******************
    >>
    >> 192.168.0.1--*************************
    >> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>
    >>
    >>
    >>
    >> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >> news:C5E12624-0EEF-4A6D-84C9-AF9BB6440665@microsoft.com...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> Open a command prompt and enter "ipconfig /all", without the quotes.
    >>> What do you get?
    >>>
    >>> Other points in-line below.
    >>>
    >>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>> news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...
    >>>> 0016D3A2E7AD is my machines regular (wire) network card. The wireless
    >>>> card is disabled in device manager (which presumably rules any wireles
    >>>> connection out). 68.127.186.255 is AT&T's network, which is my ISP
    >>>> (ARIN lookup below):
    >>>>
    >>>> AT&T Internet Services SBCIS-SIS80 (NET-68-120-0-0-1)
    >>>> 68.120.0.0 - 68.127.255.255
    >>>> bras4.pltnca SBC068127176000040211 (NET-68-127-176-0-1)
    >>>> 68.127.176.0 - 68.127.191.255
    >>>>
    >>>> The constantly repeating reconnection notices at 5 minute intervals,
    >>>> (with resulting successfully assigned IP addresses), is probably a
    >>>> result of the fact that I remove the ethernet cable from my network
    >>>> card whenever I step away from my machine.
    >>>
    >>> You really shouldn't do that. Only USB is generally safe to hot-plug.
    >>> Sooner or later you're luck will run out and one or the other ethernet
    >>> devices will fry. That aside, unplugging it doesn't account for those
    >>> repeating reconnections. The timing is too consistent, down to the
    >>> second.
    >>>
    >>>>
    >>>> The only other remotely possible connection to my PC would have been
    >>>> bluetooth, however the wireless card which provides bluetooth
    >>>> connectivity is always turned off (at the switch).
    >>>>
    >>>> This leaves 2 questions
    >>>>
    >>>> 1) How could there be a master browser called JAYS showing up on my
    >>>> logs (given the above).
    >>>
    >>> You would both have to be peers connected on the same LAN or directly to
    >>> each other (same thing). Any PC on a LAN can be a master browser. I have
    >>> one XP PC on mine that always insists on taking that status when it
    >>> joins the LAN.
    >>>
    >>>> and (less importantly)
    >>>>
    >>>> 2) Why is my machine having a conversation with the outside world (my
    >>>> ISP) about its workgroup. My understanding was that a workgroup would
    >>>> be something that would be limited to my LAN alone.
    >>>
    >>> Let's see what ipconfig shows.
    >>>
    >>>>
    >>>>
    >>>>
    >>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>> news:6AD5B7D8-0DFF-4421-8DF9-3FF57637594C@microsoft.com...
    >>>>> The anomalous name being in the router was only a suggestion, it's an
    >>>>> option in mine that could also be in yours. As far as not finding the
    >>>>> LAN DHCP server in the netbios table, this ....
    >>>>>
    >>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None The
    >>>>> IP
    >>>>>>>> address lease 192.168.1.64 for the Network Card with network
    >>>>>>>> address 0016D3A2E7AD has been denied by the DHCP server 192.168.0.1
    >>>>>>>> (The DHCP Server sent a DHCPNACK message).
    >>>>>
    >>>>> says that it exists, at least some of the time, and that your computer
    >>>>> tried to use it with an incorrect network address and got booted. This
    >>>>> on the other hand....
    >>>>>
    >>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>>>>> could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>
    >>>>> says your computer subsequently tried to connect to a server on the
    >>>>> internet, probably your ISP, possibly somewhere else. There's no
    >>>>> indication here whether it is the same network adapter making the
    >>>>> connection as the one above but we can see from the text that your
    >>>>> network adapter in this case also "somehow" had some incorrect
    >>>>> information set in its configuration at the time.
    >>>>>
    >>>>> OTOH these constantly repeating reconnection notices at 5 minute
    >>>>> intervals....
    >>>>>
    >>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>
    >>>>> Are very much like what you can see happening with wireless
    >>>>> connections. If I were going to make a guess as to what is going on
    >>>>> here I'd say that apart from the ethernet adapter you connect to your
    >>>>> own modem with you do have a wireless adapter in that computer, it is
    >>>>> always turned on and it is set to automatically connect to any
    >>>>> available network. Every so often your PC is piggybacking a ride, or
    >>>>> trying to, on poor JAYS wireless network. :)
    >>>>>
    >>>>>
    >>>>>
    >>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>> news:OUZ0QCKhIHA.4740@TK2MSFTNGP05.phx.gbl...
    >>>>>>
    >>>>>> If JAYS were the name of the modem or in its netbios table, then it
    >>>>>> should still be there presumably. (I have not reconfigured the modem
    >>>>>> in several months, and at that I time I set it to factory defaults -
    >>>>>> so the name JAYS should not be assigned to the modem).
    >>>>>>
    >>>>>> I checked the mode that the modem is operating. This is as follows:
    >>>>>>
    >>>>>> PPP is on the modem. (PPP session is initiated from the modem.) -
    >>>>>> i.e. Not operating in Bridging mode
    >>>>>>
    >>>>>> I believe my DHCP server is assigned by the gateway, when I connect
    >>>>>> (i.e. no static IP configured on my machine).
    >>>>>>
    >>>>>> I did a lookup of the netbios name table on my PC which I listed
    >>>>>> below (When I tried nbtstat -a 192.168.0.1 for the modem I got "host
    >>>>>> not found").
    >>>>>>
    >>>>>>
    >>>>>> NetBIOS Local Name Table
    >>>>>>
    >>>>>> Name Type Status
    >>>>>> ---------------------------------------------
    >>>>>> MYPC <00> UNIQUE Registered
    >>>>>> WORKGROUP <00> GROUP Registered
    >>>>>> MYPC <20> UNIQUE Registered
    >>>>>> WORKGROUP <1E> GROUP Registered
    >>>>>> WORKGROUP <1D> UNIQUE Registered
    >>>>>> ..__MSBROWSE__. <01> GROUP Registered
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>>> news:EBF529EE-1C6A-4D4F-BB48-82EA200A86A9@microsoft.com...
    >>>>>>> It looks like your network connection may be misconfigured. From the
    >>>>>>> events at timestamp 10:01 and later it appears you have two
    >>>>>>> conflicting DHCP services being used. You have a DHCP server at
    >>>>>>> 192.168.0.1 which I presume is the DSL Modem with routing
    >>>>>>> capabilities enabled. You are also trying to get a DHCP address
    >>>>>>> directly from your ISP, probably using IP 68.127.186.255 as the DHCP
    >>>>>>> server address. You should use only one or the other. I'd try
    >>>>>>> turning off DHCP in the modem first and see how that works out.
    >>>>>>>
    >>>>>>> The modem can probably be configured in several different operating
    >>>>>>> modes. I have no way of knowing what your available options are or
    >>>>>>> which mode has been enabled. My own has 4 distinct DSL operating
    >>>>>>> modes plus various combinations of routing and firewall features.
    >>>>>>> IOW, there are umpteen ways to screw up the connection. :)
    >>>>>>>
    >>>>>>> Typically there are two common connection modes that might be used.
    >>>>>>> One way is to have the modem set in 'bridge" mode, where it only
    >>>>>>> makes the hardware connection to the DSL carrier signal. You would
    >>>>>>> Windows built in PPPOE "dialer" to log into your ISP from your
    >>>>>>> computer. In this configuration the ISP's DHCP server would give
    >>>>>>> your computer an internet IP ... i.e.. 68.127.186.115. You would
    >>>>>>> need to set up your ISP username and password in the PPPOE dialer to
    >>>>>>> log on. Workgroup related settings in the PC would be irrelevant in
    >>>>>>> this case as long as the computer can communicate to the modem. The
    >>>>>>> PPPOE dialer is a virtual device which becomes the effective
    >>>>>>> internet connection. All of the required settings information would
    >>>>>>> be supplied by the ISP. Alternatively, a router could be used
    >>>>>>> instead to make the connections through the modem when it is in this
    >>>>>>> configuration.
    >>>>>>>
    >>>>>>> In the second configuration your modem could be set to connect to
    >>>>>>> the ISP automatically using its own internal firmware. The relevant
    >>>>>>> networking settings are made in the modem using its web interface,
    >>>>>>> either by you yourself or sometimes this information is
    >>>>>>> pre-programmed in the modem by the ISP if they supplied the modem.
    >>>>>>> You can normally access the modem's web interface using your browser
    >>>>>>> (try typing 192.168.0.1 in the address bar). The modem could be set
    >>>>>>> to auto-dial (AKA always-on) or "dial on demand" mode (i.e.. the
    >>>>>>> modem connects whenever the PC tries to access the internet and can
    >>>>>>> disconnect again after a set timeout period of no activity). In
    >>>>>>> this configuration it is the modem which gets the internet IP from
    >>>>>>> your ISP and then passes the internet connection to the PC through
    >>>>>>> its LAN port at address 192.168.0.1 (or whatever the default is).
    >>>>>>> Routing and DHCP may or may not be enabled in the modem, but if they
    >>>>>>> are enabled your computer should use 192.168.0.1 as its DHCP server
    >>>>>>> address and receive a LAN address from the modem, not an internet
    >>>>>>> IP. Possibly 192.168.0.1 should be also entered into the computer's
    >>>>>>> TCP/IP settings as the gateway address if DNS pass-through is
    >>>>>>> enabled in the modem. Otherwise the ISP's DNS server addresses
    >>>>>>> should be used. If DHCP is not enabled in the modem you would enter
    >>>>>>> a fixed LAN address into the computer's TCP/IP configuration, in the
    >>>>>>> range 192.168.0.x. The modem itself might have an optional workgroup
    >>>>>>> or domain name entered into its LAN configuration settings, which is
    >>>>>>> where 'JAYS' could be coming from. You can probably change or
    >>>>>>> eliminate that yourself.
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>> news:%23ObFDy%23gIHA.5280@TK2MSFTNGP04.phx.gbl...
    >>>>>>>> No its a dynamic IP Address assigned by my ISP
    >>>>>>>>
    >>>>>>>> I have attached all of the event log in the 3 hours around the time
    >>>>>>>> of the browser conflict below. Im not sure if this contains any
    >>>>>>>> other information which might give a clue as to what is going on.
    >>>>>>>>
    >>>>>>>> Level Date and Time Source Event ID Task Category
    >>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:22:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:17:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:12:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:11:07 PM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>> Information 3/5/2008 12:10:11 PM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>> Information 3/5/2008 12:07:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:02:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:00:46 PM EventLog 6013 None The system
    >>>>>>>> uptime is 57335 seconds.
    >>>>>>>> Information 3/5/2008 11:57:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 11:52:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 11:48:19 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 11:47:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 11:43:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 11:42:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 11:37:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 11:37:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 11:32:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 11:32:41 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>>> status: 0.
    >>>>>>>> Information 3/5/2008 11:32:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 11:28:17 AM BROWSER 8033 None The browser has
    >>>>>>>> forced an election on network
    >>>>>>>> DeviceNetBT_Tcpip_{6C1B0769-602C-49AD-95C1-0AD3B66DA864} because
    >>>>>>>> a master browser was stopped.
    >>>>>>>> Information 3/5/2008 11:24:52 AM Service Control Manager 7036 None
    >>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>> stopped state.
    >>>>>>>> Information 3/5/2008 11:24:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 11:19:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 11:14:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 11:09:56 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>> Information 3/5/2008 11:09:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 11:08:55 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>> Information 3/5/2008 11:08:22 AM Service Control Manager 7036 None
    >>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>> running state.
    >>>>>>>> Information 3/5/2008 11:05:06 AM volsnap 33 None The oldest shadow
    >>>>>>>> copy of volume C: was deleted to keep disk space usage for shadow
    >>>>>>>> copies of volume C: below the user defined limit.
    >>>>>>>> Information 3/5/2008 11:04:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 10:59:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 10:54:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 10:49:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:45:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Error 3/5/2008 10:45:09 AM BROWSER 8009 None The browser was unable
    >>>>>>>> to promote itself to master browser. The computer that currently
    >>>>>>>> believes it is the master browser is JAYS.
    >>>>>>>> Information 3/5/2008 10:44:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:39:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:39:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:34:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:34:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:29:38 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:29:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:24:28 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:24:21 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>>> status: 0.
    >>>>>>>> Information 3/5/2008 10:24:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 10:18:41 AM Service Control Manager 7036 None
    >>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>> stopped state.
    >>>>>>>> Error 3/5/2008 10:17:06 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:16:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:11:54 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:11:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:06:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 10:05:43 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>> Information 3/5/2008 10:05:33 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>> Information 3/5/2008 10:05:26 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>> Information 3/5/2008 10:02:39 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>> Information 3/5/2008 10:02:11 AM Service Control Manager 7036 None
    >>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>> running state.
    >>>>>>>> Information 3/5/2008 10:01:36 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>>> status: 0.
    >>>>>>>> Error 3/5/2008 10:01:30 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:01:17 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the following
    >>>>>>>> status: 0.
    >>>>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None
    >>>>>>>> The IP address lease 192.168.1.64 for the Network Card with network
    >>>>>>>> address 0016D3A2E7AD has been denied by the DHCP server 192.168.0.1
    >>>>>>>> (The DHCP Server sent a DHCPNACK message).
    >>>>>>>> Warning 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1003
    >>>>>>>> None "The description for Event ID 1003 from source
    >>>>>>>> Microsoft-Windows-Dhcp-Client cannot be found. Either the component
    >>>>>>>> that raises this event is not installed on your local computer or
    >>>>>>>> the installation is corrupted. You can install or repair the
    >>>>>>>> component on the local computer.
    >>>>>>>>
    >>>>>>>> If the event originated on another computer, the display
    >>>>>>>> information had to be saved with the event.
    >>>>>>>>
    >>>>>>>> The following information was included with the event:
    >>>>>>>>
    >>>>>>>> 0016D3A2E7AD
    >>>>>>>> %%2163146757
    >>>>>>>>
    >>>>>>>> The description string for parameter reference (%1) could not be
    >>>>>>>> found
    >>>>>>>> "
    >>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 9:57:44 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>> Information 3/5/2008 9:57:37 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>> Information 3/5/2008 9:52:42 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>> Information 3/5/2008 9:52:35 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>> Information 3/5/2008 9:38:26 AM Service Control Manager 7036 None
    >>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>> stopped state.
    >>>>>>>> Information 3/5/2008 9:37:56 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the following
    >>>>>>>> status: 0.
    >>>>>>>> Information 3/5/2008 9:37:48 AM Service Control Manager 7036 None
    >>>>>>>> The Windows Image Acquisition (WIA) service entered the running
    >>>>>>>> state.
    >>>>>>>> Information 3/5/2008 9:37:39 AM
    >>>>>>>> Microsoft-Windows-Power-Troubleshooter 1 None "The system has
    >>>>>>>> resumed from sleep.
    >>>>>>>>
    >>>>>>>> Sleep Time: 3/5/2008 7:12:57 AM
    >>>>>>>> Wake Time: 3/5/2008 5:37:34 PM
    >>>>>>>>
    >>>>>>>> Wake Source: Unknown"
    >>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system detected
    >>>>>>>> that network adapter Local Area Connection was connected to the
    >>>>>>>> network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system detected
    >>>>>>>> that network adapter Local Area Connection was connected to the
    >>>>>>>> network, and has initiated normal operation.
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "Bob F." <bob@NOSPAN.com> wrote in message
    >>>>>>>> news:52055B79-F315-4C46-986D-CB8AFBFF2D37@microsoft.com...
    >>>>>>>>> Where did you get the setup information for your internet
    >>>>>>>>> connection? Did you use a static IP? Maybe it's incorrect and you
    >>>>>>>>> are encroaching onto someone else's IP space.
    >>>>>>>>>
    >>>>>>>>> --
    >>>>>>>>> BobF.
    >>>>>>>>> "Dave" <dave@beepbeep.com> wrote in message
    >>>>>>>>> news:eBrCR47gIHA.4436@TK2MSFTNGP02.phx.gbl...
    >>>>>>>>>> What shows up in Start - Network?
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>>>> news:#orAgk7gIHA.2448@TK2MSFTNGP03.phx.gbl...
    >>>>>>>>>>> My (lone) machine is connected directly to the DSL router with
    >>>>>>>>>>> no wireless capabilities on the router. Despite this I get the
    >>>>>>>>>>> following message in the event log:
    >>>>>>>>>>>
    >>>>>>>>>>> The browser was unable to promote itself to master browser. The
    >>>>>>>>>>> computer that currently believes it is the master browser is
    >>>>>>>>>>> JAYS.
    >>>>>>>>>>>
    >>>>>>>>>>> Once again, my computer is not called JAYS. Friends and family
    >>>>>>>>>>> are not Vista Security experts. Looking for capable / expert
    >>>>>>>>>>> advice from this forum.
    >>>>>>>>>>>
    >>>>>>>>>>> What are the possible explanations for this???
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>> "Malke" <malke@invalid.invalid> wrote in message
    >>>>>>>>>>> news:O5eVD62gIHA.4692@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>>>>> Nubie wrote:
    >>>>>>>>>>>>
    >>>>>>>>>>>>> What should I be looking for in the Settings?
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> ALSO: How would the config of my DSL modem confuse my vista
    >>>>>>>>>>>>> machine to
    >>>>>>>>>>>>> think that there is another computer called JAYS on my local
    >>>>>>>>>>>>> network.
    >>>>>>>>>>>>
    >>>>>>>>>>>>>> Nubie;642434 Wrote:
    >>>>>>>>>>>>>>> Hi
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> I have a single (lone) windows Vista machine connected
    >>>>>>>>>>>>>>> directly to the
    >>>>>>>>>>>>>>> internet via a dsl modem. I just viewed the following in my
    >>>>>>>>>>>>>>> eventlogs:
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> "The browser was unable to promote itself to master browser.
    >>>>>>>>>>>>>>> The
    >>>>>>>>>>>>>>> computer
    >>>>>>>>>>>>>>> that
    >>>>>>>>>>>>>>> currently believes it is the master browser is JAYS. My
    >>>>>>>>>>>>>>> machine is NOT
    >>>>>>>>>>>>>>> called JAYS."
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> What is happening here!!?? If my machine is connected to a
    >>>>>>>>>>>>>>> DSL modem
    >>>>>>>>>>>>>>> with
    >>>>>>>>>>>>>>> no additional
    >>>>>>>>>>>>>>> machines connected to that modem why is this message
    >>>>>>>>>>>>>>> appearing ????
    >>>>>>>>>>>>>>> What is
    >>>>>>>>>>>>>>> happening here ??
    >>>>>>>>>>>>
    >>>>>>>>>>>> It certainly seems as though someone else is on your network.
    >>>>>>>>>>>> Is this a
    >>>>>>>>>>>> combination modem/wireless router? If yes, you probably haven't
    >>>>>>>>>>>> secured
    >>>>>>>>>>>> your wireless properly and a stranger is using your bandwidth.
    >>>>>>>>>>>> If you only
    >>>>>>>>>>>> have a single computer connected directly to a DSL modem by
    >>>>>>>>>>>> ethernet cable
    >>>>>>>>>>>> (no wireless router), then call your ISP. Because you don't
    >>>>>>>>>>>> really know
    >>>>>>>>>>>> what you're looking at - and I mean no disrespect to you, I'm
    >>>>>>>>>>>> just being
    >>>>>>>>>>>> practical - it might be smart for you to have a computer
    >>>>>>>>>>>> professional come
    >>>>>>>>>>>> on-site and take a look. This will not be someone from a
    >>>>>>>>>>>> BigComputerStore/GeekSquad type of place. Get recommendations
    >>>>>>>>>>>> from friends,
    >>>>>>>>>>>> family, colleagues.
    >>>>>>>>>>>>
    >>>>>>>>>>>> Malke
    >>>>>>>>>>>> --
    >>>>>>>>>>>> MS-MVP
    >>>>>>>>>>>> Elephant Boy Computers
    >>>>>>>>>>>>
    >>>>>>>>>>>> Don't Panic!
    >>>>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>><!--colorc--><!--/colorc-->
    >><!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     
    Bob F., Mar 15, 2008
    #25
  7. Nubie

    Nubie Guest

    The modem is set up for DNS forwarding, and the DNS IP's are configured on
    the modem. With regards to the NetBios over TCP/IP, I just disabled this
    (thanks for the advice).

    What is confusing me here is your comments regarding the DHCP server on the
    modem. Presumably, any internet IP address the modem gives me has to have
    come from the ISP. The ISP assigned the internet IP to the modem, the modem
    assigns this to me. (Even if I unplugged my machine from the modem for 30
    mins).

    How would the above cause the confusion wrt another machine ('JAYS')
    appearing to be on my network?
    Somehow a NetBIOS message was broadcast, to this other machine on what the
    modem/router believed to be my network. How could this have happened?


    "RalfG" <itsnotme@ladeda.deda> wrote in message
    news:C7150467-0DF3-49C9-BFFD-3D3B960F5041@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Looks like a bit of a dog's breakfast. :)
    > Questionable entries marked with -******************
    >
    > You said earlier that the computer was getting a dynamic IP from your ISP
    > but the way it is configured below I can't see that happening reliably.
    > You've got two conflicting DHCP services active.
    > The default Gateway is set to an internet IP but the DHCP server listed is
    > the modem/router, which presumable can only supply LAN addresses within
    > its own network subnet (192.168.0.x). Your ISP will have it's own
    > dedicated DHCP servers which are on internet IPs. That is where the
    > 68.127.175.71 address came from. Aside from that the modem's internal
    > DHCP server wouldn't know which internet IPs were available and which ones
    > were already being assigned to someone else. This could be where your
    > mystery connection is being created. Also the subnet mask for your
    > internet IP is set for the 192.168.0.x subnet rather than for internet
    > which is not okay.
    >
    > Your DNS server is set to a local LAN address (192.168.0.1) rather than
    > the ISP's DNS servers, which is probably okay if the modem/router has the
    > real DNS server addresses and DNS forwarding is enabled. Otherwise these
    > lines should be showing two different IPs from your ISP. NetBios is
    > enabled on your ethernet TCP/IP adapter but without NAT or firewall
    > protection in the modem/router this is not a good idea over an open
    > internet connection.
    >
    > It looks like the modem/router's actual LAN IP is 192.168.0.1. That's the
    > address you should browse to in IE to access the modem's configuration
    > pages. How you need to configure the computer's network settings depends
    > on how the modem has been configured but I think at the very least you
    > should be disabling the modem's onboard DHCP server if your computer's
    > adapter is intended to get an address automatically from your ISP. Setting
    > the router's DNS to pass-through mode rather than forwarding isn't
    > absolutely necessary but it eliminates the extra rerouting step. In the
    > various DNS Suffix lines I'd expect to see entries referencing your ISP's
    > domain name. I suspect the tunnel adapters listed below are just
    > redundant.
    >
    >
    > "Nubie" <newsgoup_contact@atigen.com> wrote in message
    > news:O3ZdjXihIHA.200@TK2MSFTNGP02.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    >>
    >> Windows IP Configuration
    >>
    >> Host Name . . . . . . . . . . . . : mypc
    >> Primary Dns Suffix . . . . . . . :
    >> Node Type . . . . . . . . . . . . : Hybrid
    >> IP Routing Enabled. . . . . . . . : No
    >> WINS Proxy Enabled. . . . . . . . : No
    >> DNS Suffix Search List. . . . . . :
    >> domain_not_set.invalid--*******************
    >>
    >> Ethernet adapter Local Area Connection:
    >>
    >> Connection-specific DNS Suffix . :
    >> domain_not_set.invalid---************************
    >> Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
    >> Physical Address. . . . . . . . . : 00-16-D3-A2-E7-AD
    >> DHCP Enabled. . . . . . . . . . . : Yes
    >> Autoconfiguration Enabled . . . . : Yes
    >> Link-local IPv6 Address . . . . . :
    >> ff80::80f6:625f:f376:8301%6(Preferred)
    >> IPv4 Address. . . . . . . . . . . : 68.127.175.71(Preferred)
    >> Subnet Mask . . . . . . . . . . . :
    >> 255.255.255.0 --*********************
    >> Lease Obtained. . . . . . . . . . : Friday, March 14, 2008 12:05:54 PM
    >> Lease Expires . . . . . . . . . . : Friday, March 14, 2008 3:41:18 PM
    >> Default Gateway . . . . . . . . . : 68.127.175.72
    >> DHCP Server . . . . . . . . . . . : 192.168.0.1--*********************
    >> DHCPv6 IAID . . . . . . . . . . . : 203332435
    >> DNS Servers . . . . . . . . . . . : 192.168.0.1--*********************
    >> 192.168.0.1--*********************
    >> NetBIOS over Tcpip. . . . . . . . : Enabled
    >>
    >> Tunnel adapter Local Area Connection* 6:
    >>
    >> Connection-specific DNS Suffix . : domain_not_set.invalid
    >> Description . . . . . . . . . . . : isatap.domain_not_set.invalid
    >> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >> DHCP Enabled. . . . . . . . . . . : No
    >> Autoconfiguration Enabled . . . . : Yes
    >> Link-local IPv6 Address . . . . . :
    >> ff80::200:5fff:68.128.185.71%14(Preferred
    >> )
    >> Default Gateway . . . . . . . . . :
    >> DNS Servers . . . . . . . . . . . : 192.168.0.1--******************
    >> 192.168.0.1--********************
    >> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>
    >> Tunnel adapter Local Area Connection* 7:
    >>
    >> Connection-specific DNS Suffix . :
    >> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    >> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    >> DHCP Enabled. . . . . . . . . . . : No
    >> Autoconfiguration Enabled . . . . : Yes
    >> IPv6 Address. . . . . . . . . . . :
    >> 2001:0:4337:9f66:18f9:3343:ff80:50f8(Pref
    >> erred)
    >> Link-local IPv6 Address . . . . . :
    >> ff80::38f9:3343:ff80:50f8%12(Preferred)
    >> Default Gateway . . . . . . . . . :
    >> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>
    >> Tunnel adapter Local Area Connection* 14:
    >>
    >> Media State . . . . . . . . . . . : Media disconnected
    >> Connection-specific DNS Suffix . :
    >> Description . . . . . . . . . . . : 6TO4 Adapter
    >> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >> DHCP Enabled. . . . . . . . . . . : No
    >> Autoconfiguration Enabled . . . . : Yes
    >>
    >> Tunnel adapter Local Area Connection* 10:
    >>
    >> Connection-specific DNS Suffix . : domain_not_set.invalid
    >> Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
    >> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >> DHCP Enabled. . . . . . . . . . . : No
    >> Autoconfiguration Enabled . . . . : Yes
    >> Temporary IPv6 Address. . . . . . :
    >> 2002:227f:ff27::227f:ff27(Preferred)
    >> Default Gateway . . . . . . . . . : 2002:f058:6301::f058:6301
    >> DNS Servers . . . . . . . . . . . : 192.168.0.1---*******************
    >>
    >> 192.168.0.1--*************************
    >> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>
    >>
    >>
    >>
    >> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >> news:C5E12624-0EEF-4A6D-84C9-AF9BB6440665@microsoft.com...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> Open a command prompt and enter "ipconfig /all", without the quotes.
    >>> What do you get?
    >>>
    >>> Other points in-line below.
    >>>
    >>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>> news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...
    >>>> 0016D3A2E7AD is my machines regular (wire) network card. The wireless
    >>>> card is disabled in device manager (which presumably rules any wireles
    >>>> connection out). 68.127.186.255 is AT&T's network, which is my ISP
    >>>> (ARIN lookup below):
    >>>>
    >>>> AT&T Internet Services SBCIS-SIS80 (NET-68-120-0-0-1)
    >>>> 68.120.0.0 - 68.127.255.255
    >>>> bras4.pltnca SBC068127176000040211 (NET-68-127-176-0-1)
    >>>> 68.127.176.0 - 68.127.191.255
    >>>>
    >>>> The constantly repeating reconnection notices at 5 minute intervals,
    >>>> (with resulting successfully assigned IP addresses), is probably a
    >>>> result of the fact that I remove the ethernet cable from my network
    >>>> card whenever I step away from my machine.
    >>>
    >>> You really shouldn't do that. Only USB is generally safe to hot-plug.
    >>> Sooner or later you're luck will run out and one or the other ethernet
    >>> devices will fry. That aside, unplugging it doesn't account for those
    >>> repeating reconnections. The timing is too consistent, down to the
    >>> second.
    >>>
    >>>>
    >>>> The only other remotely possible connection to my PC would have been
    >>>> bluetooth, however the wireless card which provides bluetooth
    >>>> connectivity is always turned off (at the switch).
    >>>>
    >>>> This leaves 2 questions
    >>>>
    >>>> 1) How could there be a master browser called JAYS showing up on my
    >>>> logs (given the above).
    >>>
    >>> You would both have to be peers connected on the same LAN or directly to
    >>> each other (same thing). Any PC on a LAN can be a master browser. I have
    >>> one XP PC on mine that always insists on taking that status when it
    >>> joins the LAN.
    >>>
    >>>> and (less importantly)
    >>>>
    >>>> 2) Why is my machine having a conversation with the outside world (my
    >>>> ISP) about its workgroup. My understanding was that a workgroup would
    >>>> be something that would be limited to my LAN alone.
    >>>
    >>> Let's see what ipconfig shows.
    >>>
    >>>>
    >>>>
    >>>>
    >>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>> news:6AD5B7D8-0DFF-4421-8DF9-3FF57637594C@microsoft.com...
    >>>>> The anomalous name being in the router was only a suggestion, it's an
    >>>>> option in mine that could also be in yours. As far as not finding the
    >>>>> LAN DHCP server in the netbios table, this ....
    >>>>>
    >>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None The
    >>>>> IP
    >>>>>>>> address lease 192.168.1.64 for the Network Card with network
    >>>>>>>> address 0016D3A2E7AD has been denied by the DHCP server 192.168.0.1
    >>>>>>>> (The DHCP Server sent a DHCPNACK message).
    >>>>>
    >>>>> says that it exists, at least some of the time, and that your computer
    >>>>> tried to use it with an incorrect network address and got booted. This
    >>>>> on the other hand....
    >>>>>
    >>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP :1d""
    >>>>>>>> could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>
    >>>>> says your computer subsequently tried to connect to a server on the
    >>>>> internet, probably your ISP, possibly somewhere else. There's no
    >>>>> indication here whether it is the same network adapter making the
    >>>>> connection as the one above but we can see from the text that your
    >>>>> network adapter in this case also "somehow" had some incorrect
    >>>>> information set in its configuration at the time.
    >>>>>
    >>>>> OTOH these constantly repeating reconnection notices at 5 minute
    >>>>> intervals....
    >>>>>
    >>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>
    >>>>> Are very much like what you can see happening with wireless
    >>>>> connections. If I were going to make a guess as to what is going on
    >>>>> here I'd say that apart from the ethernet adapter you connect to your
    >>>>> own modem with you do have a wireless adapter in that computer, it is
    >>>>> always turned on and it is set to automatically connect to any
    >>>>> available network. Every so often your PC is piggybacking a ride, or
    >>>>> trying to, on poor JAYS wireless network. :)
    >>>>>
    >>>>>
    >>>>>
    >>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>> news:OUZ0QCKhIHA.4740@TK2MSFTNGP05.phx.gbl...
    >>>>>>
    >>>>>> If JAYS were the name of the modem or in its netbios table, then it
    >>>>>> should still be there presumably. (I have not reconfigured the modem
    >>>>>> in several months, and at that I time I set it to factory defaults -
    >>>>>> so the name JAYS should not be assigned to the modem).
    >>>>>>
    >>>>>> I checked the mode that the modem is operating. This is as follows:
    >>>>>>
    >>>>>> PPP is on the modem. (PPP session is initiated from the modem.) -
    >>>>>> i.e. Not operating in Bridging mode
    >>>>>>
    >>>>>> I believe my DHCP server is assigned by the gateway, when I connect
    >>>>>> (i.e. no static IP configured on my machine).
    >>>>>>
    >>>>>> I did a lookup of the netbios name table on my PC which I listed
    >>>>>> below (When I tried nbtstat -a 192.168.0.1 for the modem I got "host
    >>>>>> not found").
    >>>>>>
    >>>>>>
    >>>>>> NetBIOS Local Name Table
    >>>>>>
    >>>>>> Name Type Status
    >>>>>> ---------------------------------------------
    >>>>>> MYPC <00> UNIQUE Registered
    >>>>>> WORKGROUP <00> GROUP Registered
    >>>>>> MYPC <20> UNIQUE Registered
    >>>>>> WORKGROUP <1E> GROUP Registered
    >>>>>> WORKGROUP <1D> UNIQUE Registered
    >>>>>> ..__MSBROWSE__. <01> GROUP Registered
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>>> news:EBF529EE-1C6A-4D4F-BB48-82EA200A86A9@microsoft.com...
    >>>>>>> It looks like your network connection may be misconfigured. From the
    >>>>>>> events at timestamp 10:01 and later it appears you have two
    >>>>>>> conflicting DHCP services being used. You have a DHCP server at
    >>>>>>> 192.168.0.1 which I presume is the DSL Modem with routing
    >>>>>>> capabilities enabled. You are also trying to get a DHCP address
    >>>>>>> directly from your ISP, probably using IP 68.127.186.255 as the DHCP
    >>>>>>> server address. You should use only one or the other. I'd try
    >>>>>>> turning off DHCP in the modem first and see how that works out.
    >>>>>>>
    >>>>>>> The modem can probably be configured in several different operating
    >>>>>>> modes. I have no way of knowing what your available options are or
    >>>>>>> which mode has been enabled. My own has 4 distinct DSL operating
    >>>>>>> modes plus various combinations of routing and firewall features.
    >>>>>>> IOW, there are umpteen ways to screw up the connection. :)
    >>>>>>>
    >>>>>>> Typically there are two common connection modes that might be used.
    >>>>>>> One way is to have the modem set in 'bridge" mode, where it only
    >>>>>>> makes the hardware connection to the DSL carrier signal. You would
    >>>>>>> Windows built in PPPOE "dialer" to log into your ISP from your
    >>>>>>> computer. In this configuration the ISP's DHCP server would give
    >>>>>>> your computer an internet IP ... i.e.. 68.127.186.115. You would
    >>>>>>> need to set up your ISP username and password in the PPPOE dialer to
    >>>>>>> log on. Workgroup related settings in the PC would be irrelevant in
    >>>>>>> this case as long as the computer can communicate to the modem. The
    >>>>>>> PPPOE dialer is a virtual device which becomes the effective
    >>>>>>> internet connection. All of the required settings information would
    >>>>>>> be supplied by the ISP. Alternatively, a router could be used
    >>>>>>> instead to make the connections through the modem when it is in this
    >>>>>>> configuration.
    >>>>>>>
    >>>>>>> In the second configuration your modem could be set to connect to
    >>>>>>> the ISP automatically using its own internal firmware. The relevant
    >>>>>>> networking settings are made in the modem using its web interface,
    >>>>>>> either by you yourself or sometimes this information is
    >>>>>>> pre-programmed in the modem by the ISP if they supplied the modem.
    >>>>>>> You can normally access the modem's web interface using your browser
    >>>>>>> (try typing 192.168.0.1 in the address bar). The modem could be set
    >>>>>>> to auto-dial (AKA always-on) or "dial on demand" mode (i.e.. the
    >>>>>>> modem connects whenever the PC tries to access the internet and can
    >>>>>>> disconnect again after a set timeout period of no activity). In
    >>>>>>> this configuration it is the modem which gets the internet IP from
    >>>>>>> your ISP and then passes the internet connection to the PC through
    >>>>>>> its LAN port at address 192.168.0.1 (or whatever the default is).
    >>>>>>> Routing and DHCP may or may not be enabled in the modem, but if they
    >>>>>>> are enabled your computer should use 192.168.0.1 as its DHCP server
    >>>>>>> address and receive a LAN address from the modem, not an internet
    >>>>>>> IP. Possibly 192.168.0.1 should be also entered into the computer's
    >>>>>>> TCP/IP settings as the gateway address if DNS pass-through is
    >>>>>>> enabled in the modem. Otherwise the ISP's DNS server addresses
    >>>>>>> should be used. If DHCP is not enabled in the modem you would enter
    >>>>>>> a fixed LAN address into the computer's TCP/IP configuration, in the
    >>>>>>> range 192.168.0.x. The modem itself might have an optional workgroup
    >>>>>>> or domain name entered into its LAN configuration settings, which is
    >>>>>>> where 'JAYS' could be coming from. You can probably change or
    >>>>>>> eliminate that yourself.
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>> news:%23ObFDy%23gIHA.5280@TK2MSFTNGP04.phx.gbl...
    >>>>>>>> No its a dynamic IP Address assigned by my ISP
    >>>>>>>>
    >>>>>>>> I have attached all of the event log in the 3 hours around the time
    >>>>>>>> of the browser conflict below. Im not sure if this contains any
    >>>>>>>> other information which might give a clue as to what is going on.
    >>>>>>>>
    >>>>>>>> Level Date and Time Source Event ID Task Category
    >>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:22:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:17:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:12:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:11:07 PM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>> Information 3/5/2008 12:10:11 PM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>> Information 3/5/2008 12:07:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:02:30 PM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 12:00:46 PM EventLog 6013 None The system
    >>>>>>>> uptime is 57335 seconds.
    >>>>>>>> Information 3/5/2008 11:57:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 11:52:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 11:48:19 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 11:47:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 11:43:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 11:42:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 11:37:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 11:37:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 11:32:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 11:32:41 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>>> status: 0.
    >>>>>>>> Information 3/5/2008 11:32:30 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 11:28:17 AM BROWSER 8033 None The browser has
    >>>>>>>> forced an election on network
    >>>>>>>> DeviceNetBT_Tcpip_{6C1B0769-602C-49AD-95C1-0AD3B66DA864} because
    >>>>>>>> a master browser was stopped.
    >>>>>>>> Information 3/5/2008 11:24:52 AM Service Control Manager 7036 None
    >>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>> stopped state.
    >>>>>>>> Information 3/5/2008 11:24:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 11:19:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 11:14:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 11:09:56 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>> Information 3/5/2008 11:09:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 11:08:55 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>> Information 3/5/2008 11:08:22 AM Service Control Manager 7036 None
    >>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>> running state.
    >>>>>>>> Information 3/5/2008 11:05:06 AM volsnap 33 None The oldest shadow
    >>>>>>>> copy of volume C: was deleted to keep disk space usage for shadow
    >>>>>>>> copies of volume C: below the user defined limit.
    >>>>>>>> Information 3/5/2008 11:04:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 10:59:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 10:54:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 10:49:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:45:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Error 3/5/2008 10:45:09 AM BROWSER 8009 None The browser was unable
    >>>>>>>> to promote itself to master browser. The computer that currently
    >>>>>>>> believes it is the master browser is JAYS.
    >>>>>>>> Information 3/5/2008 10:44:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:39:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:39:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:34:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:34:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:29:38 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:29:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:24:28 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:24:21 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>>> status: 0.
    >>>>>>>> Information 3/5/2008 10:24:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 10:18:41 AM Service Control Manager 7036 None
    >>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>> stopped state.
    >>>>>>>> Error 3/5/2008 10:17:06 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:16:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:11:54 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:11:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:06:09 AM Microsoft-Windows-Dhcp-Client 1103
    >>>>>>>> None Your computer was successfully assigned an address from the
    >>>>>>>> network, and it can now connect to other computers.
    >>>>>>>> Information 3/5/2008 10:05:43 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>> Information 3/5/2008 10:05:33 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>> Information 3/5/2008 10:05:26 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>> Information 3/5/2008 10:02:39 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>> Information 3/5/2008 10:02:11 AM Service Control Manager 7036 None
    >>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>> running state.
    >>>>>>>> Information 3/5/2008 10:01:36 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>>> status: 0.
    >>>>>>>> Error 3/5/2008 10:01:30 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255 did
    >>>>>>>> not allow the name to be claimed by this computer."
    >>>>>>>> Information 3/5/2008 10:01:17 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the following
    >>>>>>>> status: 0.
    >>>>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None
    >>>>>>>> The IP address lease 192.168.1.64 for the Network Card with network
    >>>>>>>> address 0016D3A2E7AD has been denied by the DHCP server 192.168.0.1
    >>>>>>>> (The DHCP Server sent a DHCPNACK message).
    >>>>>>>> Warning 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1003
    >>>>>>>> None "The description for Event ID 1003 from source
    >>>>>>>> Microsoft-Windows-Dhcp-Client cannot be found. Either the component
    >>>>>>>> that raises this event is not installed on your local computer or
    >>>>>>>> the installation is corrupted. You can install or repair the
    >>>>>>>> component on the local computer.
    >>>>>>>>
    >>>>>>>> If the event originated on another computer, the display
    >>>>>>>> information had to be saved with the event.
    >>>>>>>>
    >>>>>>>> The following information was included with the event:
    >>>>>>>>
    >>>>>>>> 0016D3A2E7AD
    >>>>>>>> %%2163146757
    >>>>>>>>
    >>>>>>>> The description string for parameter reference (%1) could not be
    >>>>>>>> found
    >>>>>>>> "
    >>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 9:57:44 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>> Information 3/5/2008 9:57:37 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>> Information 3/5/2008 9:52:42 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>> Information 3/5/2008 9:52:35 AM Service Control Manager 7036 None
    >>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>> Information 3/5/2008 9:38:26 AM Service Control Manager 7036 None
    >>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>> stopped state.
    >>>>>>>> Information 3/5/2008 9:37:56 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the following
    >>>>>>>> status: 0.
    >>>>>>>> Information 3/5/2008 9:37:48 AM Service Control Manager 7036 None
    >>>>>>>> The Windows Image Acquisition (WIA) service entered the running
    >>>>>>>> state.
    >>>>>>>> Information 3/5/2008 9:37:39 AM
    >>>>>>>> Microsoft-Windows-Power-Troubleshooter 1 None "The system has
    >>>>>>>> resumed from sleep.
    >>>>>>>>
    >>>>>>>> Sleep Time: 3/5/2008 7:12:57 AM
    >>>>>>>> Wake Time: 3/5/2008 5:37:34 PM
    >>>>>>>>
    >>>>>>>> Wake Source: Unknown"
    >>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system detected
    >>>>>>>> that network adapter Local Area Connection was connected to the
    >>>>>>>> network, and has initiated normal operation.
    >>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system detected
    >>>>>>>> that network adapter Local Area Connection was connected to the
    >>>>>>>> network, and has initiated normal operation.
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "Bob F." <bob@NOSPAN.com> wrote in message
    >>>>>>>> news:52055B79-F315-4C46-986D-CB8AFBFF2D37@microsoft.com...
    >>>>>>>>> Where did you get the setup information for your internet
    >>>>>>>>> connection? Did you use a static IP? Maybe it's incorrect and you
    >>>>>>>>> are encroaching onto someone else's IP space.
    >>>>>>>>>
    >>>>>>>>> --
    >>>>>>>>> BobF.
    >>>>>>>>> "Dave" <dave@beepbeep.com> wrote in message
    >>>>>>>>> news:eBrCR47gIHA.4436@TK2MSFTNGP02.phx.gbl...
    >>>>>>>>>> What shows up in Start - Network?
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>>>> news:#orAgk7gIHA.2448@TK2MSFTNGP03.phx.gbl...
    >>>>>>>>>>> My (lone) machine is connected directly to the DSL router with
    >>>>>>>>>>> no wireless capabilities on the router. Despite this I get the
    >>>>>>>>>>> following message in the event log:
    >>>>>>>>>>>
    >>>>>>>>>>> The browser was unable to promote itself to master browser. The
    >>>>>>>>>>> computer that currently believes it is the master browser is
    >>>>>>>>>>> JAYS.
    >>>>>>>>>>>
    >>>>>>>>>>> Once again, my computer is not called JAYS. Friends and family
    >>>>>>>>>>> are not Vista Security experts. Looking for capable / expert
    >>>>>>>>>>> advice from this forum.
    >>>>>>>>>>>
    >>>>>>>>>>> What are the possible explanations for this???
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>> "Malke" <malke@invalid.invalid> wrote in message
    >>>>>>>>>>> news:O5eVD62gIHA.4692@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>>>>> Nubie wrote:
    >>>>>>>>>>>>
    >>>>>>>>>>>>> What should I be looking for in the Settings?
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> ALSO: How would the config of my DSL modem confuse my vista
    >>>>>>>>>>>>> machine to
    >>>>>>>>>>>>> think that there is another computer called JAYS on my local
    >>>>>>>>>>>>> network.
    >>>>>>>>>>>>
    >>>>>>>>>>>>>> Nubie;642434 Wrote:
    >>>>>>>>>>>>>>> Hi
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> I have a single (lone) windows Vista machine connected
    >>>>>>>>>>>>>>> directly to the
    >>>>>>>>>>>>>>> internet via a dsl modem. I just viewed the following in my
    >>>>>>>>>>>>>>> eventlogs:
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> "The browser was unable to promote itself to master browser.
    >>>>>>>>>>>>>>> The
    >>>>>>>>>>>>>>> computer
    >>>>>>>>>>>>>>> that
    >>>>>>>>>>>>>>> currently believes it is the master browser is JAYS. My
    >>>>>>>>>>>>>>> machine is NOT
    >>>>>>>>>>>>>>> called JAYS."
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> What is happening here!!?? If my machine is connected to a
    >>>>>>>>>>>>>>> DSL modem
    >>>>>>>>>>>>>>> with
    >>>>>>>>>>>>>>> no additional
    >>>>>>>>>>>>>>> machines connected to that modem why is this message
    >>>>>>>>>>>>>>> appearing ????
    >>>>>>>>>>>>>>> What is
    >>>>>>>>>>>>>>> happening here ??
    >>>>>>>>>>>>
    >>>>>>>>>>>> It certainly seems as though someone else is on your network.
    >>>>>>>>>>>> Is this a
    >>>>>>>>>>>> combination modem/wireless router? If yes, you probably haven't
    >>>>>>>>>>>> secured
    >>>>>>>>>>>> your wireless properly and a stranger is using your bandwidth.
    >>>>>>>>>>>> If you only
    >>>>>>>>>>>> have a single computer connected directly to a DSL modem by
    >>>>>>>>>>>> ethernet cable
    >>>>>>>>>>>> (no wireless router), then call your ISP. Because you don't
    >>>>>>>>>>>> really know
    >>>>>>>>>>>> what you're looking at - and I mean no disrespect to you, I'm
    >>>>>>>>>>>> just being
    >>>>>>>>>>>> practical - it might be smart for you to have a computer
    >>>>>>>>>>>> professional come
    >>>>>>>>>>>> on-site and take a look. This will not be someone from a
    >>>>>>>>>>>> BigComputerStore/GeekSquad type of place. Get recommendations
    >>>>>>>>>>>> from friends,
    >>>>>>>>>>>> family, colleagues.
    >>>>>>>>>>>>
    >>>>>>>>>>>> Malke
    >>>>>>>>>>>> --
    >>>>>>>>>>>> MS-MVP
    >>>>>>>>>>>> Elephant Boy Computers
    >>>>>>>>>>>>
    >>>>>>>>>>>> Don't Panic!
    >>>>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>><!--colorc--><!--/colorc-->
    >><!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     
    Nubie, Mar 15, 2008
    #26
  8. Bob F.

    Bob F. Guest

    RalfG,
    From where did you get your settings instructions?

    --
    BobF.
    "Nubie" <newsgoup_contact@atigen.com> wrote in message
    news:eFDACeuhIHA.4140@TK2MSFTNGP04.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > The modem is set up for DNS forwarding, and the DNS IP's are configured on
    > the modem. With regards to the NetBios over TCP/IP, I just disabled this
    > (thanks for the advice).
    >
    > What is confusing me here is your comments regarding the DHCP server on
    > the modem. Presumably, any internet IP address the modem gives me has to
    > have come from the ISP. The ISP assigned the internet IP to the modem,
    > the modem assigns this to me. (Even if I unplugged my machine from the
    > modem for 30 mins).
    >
    > How would the above cause the confusion wrt another machine ('JAYS')
    > appearing to be on my network?
    > Somehow a NetBIOS message was broadcast, to this other machine on what the
    > modem/router believed to be my network. How could this have happened?
    >
    >
    > "RalfG" <itsnotme@ladeda.deda> wrote in message
    > news:C7150467-0DF3-49C9-BFFD-3D3B960F5041@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> Looks like a bit of a dog's breakfast. :)
    >> Questionable entries marked with -******************
    >>
    >> You said earlier that the computer was getting a dynamic IP from your ISP
    >> but the way it is configured below I can't see that happening reliably.
    >> You've got two conflicting DHCP services active.
    >> The default Gateway is set to an internet IP but the DHCP server listed
    >> is the modem/router, which presumable can only supply LAN addresses
    >> within its own network subnet (192.168.0.x). Your ISP will have it's own
    >> dedicated DHCP servers which are on internet IPs. That is where the
    >> 68.127.175.71 address came from. Aside from that the modem's internal
    >> DHCP server wouldn't know which internet IPs were available and which
    >> ones were already being assigned to someone else. This could be where
    >> your mystery connection is being created. Also the subnet mask for your
    >> internet IP is set for the 192.168.0.x subnet rather than for internet
    >> which is not okay.
    >>
    >> Your DNS server is set to a local LAN address (192.168.0.1) rather than
    >> the ISP's DNS servers, which is probably okay if the modem/router has the
    >> real DNS server addresses and DNS forwarding is enabled. Otherwise these
    >> lines should be showing two different IPs from your ISP. NetBios is
    >> enabled on your ethernet TCP/IP adapter but without NAT or firewall
    >> protection in the modem/router this is not a good idea over an open
    >> internet connection.
    >>
    >> It looks like the modem/router's actual LAN IP is 192.168.0.1. That's the
    >> address you should browse to in IE to access the modem's configuration
    >> pages. How you need to configure the computer's network settings depends
    >> on how the modem has been configured but I think at the very least you
    >> should be disabling the modem's onboard DHCP server if your computer's
    >> adapter is intended to get an address automatically from your ISP.
    >> Setting the router's DNS to pass-through mode rather than forwarding
    >> isn't absolutely necessary but it eliminates the extra rerouting step. In
    >> the various DNS Suffix lines I'd expect to see entries referencing your
    >> ISP's domain name. I suspect the tunnel adapters listed below are just
    >> redundant.
    >>
    >>
    >> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >> news:O3ZdjXihIHA.200@TK2MSFTNGP02.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>
    >>> Windows IP Configuration
    >>>
    >>> Host Name . . . . . . . . . . . . : mypc
    >>> Primary Dns Suffix . . . . . . . :
    >>> Node Type . . . . . . . . . . . . : Hybrid
    >>> IP Routing Enabled. . . . . . . . : No
    >>> WINS Proxy Enabled. . . . . . . . : No
    >>> DNS Suffix Search List. . . . . . :
    >>> domain_not_set.invalid--*******************
    >>>
    >>> Ethernet adapter Local Area Connection:
    >>>
    >>> Connection-specific DNS Suffix . :
    >>> domain_not_set.invalid---************************
    >>> Description . . . . . . . . . . . : NVIDIA nForce Networking
    >>> Controller
    >>> Physical Address. . . . . . . . . : 00-16-D3-A2-E7-AD
    >>> DHCP Enabled. . . . . . . . . . . : Yes
    >>> Autoconfiguration Enabled . . . . : Yes
    >>> Link-local IPv6 Address . . . . . :
    >>> ff80::80f6:625f:f376:8301%6(Preferred)
    >>> IPv4 Address. . . . . . . . . . . : 68.127.175.71(Preferred)
    >>> Subnet Mask . . . . . . . . . . . :
    >>> 255.255.255.0 --*********************
    >>> Lease Obtained. . . . . . . . . . : Friday, March 14, 2008 12:05:54 PM
    >>> Lease Expires . . . . . . . . . . : Friday, March 14, 2008 3:41:18 PM
    >>> Default Gateway . . . . . . . . . : 68.127.175.72
    >>> DHCP Server . . . . . . . . . . . : 192.168.0.1--*********************
    >>> DHCPv6 IAID . . . . . . . . . . . : 203332435
    >>> DNS Servers . . . . . . . . . . . : 192.168.0.1--*********************
    >>> 192.168.0.1--*********************
    >>> NetBIOS over Tcpip. . . . . . . . : Enabled
    >>>
    >>> Tunnel adapter Local Area Connection* 6:
    >>>
    >>> Connection-specific DNS Suffix . : domain_not_set.invalid
    >>> Description . . . . . . . . . . . : isatap.domain_not_set.invalid
    >>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>> DHCP Enabled. . . . . . . . . . . : No
    >>> Autoconfiguration Enabled . . . . : Yes
    >>> Link-local IPv6 Address . . . . . :
    >>> ff80::200:5fff:68.128.185.71%14(Preferred
    >>> )
    >>> Default Gateway . . . . . . . . . :
    >>> DNS Servers . . . . . . . . . . . : 192.168.0.1--******************
    >>> 192.168.0.1--********************
    >>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>
    >>> Tunnel adapter Local Area Connection* 7:
    >>>
    >>> Connection-specific DNS Suffix . :
    >>> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    >>> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    >>> DHCP Enabled. . . . . . . . . . . : No
    >>> Autoconfiguration Enabled . . . . : Yes
    >>> IPv6 Address. . . . . . . . . . . :
    >>> 2001:0:4337:9f66:18f9:3343:ff80:50f8(Pref
    >>> erred)
    >>> Link-local IPv6 Address . . . . . :
    >>> ff80::38f9:3343:ff80:50f8%12(Preferred)
    >>> Default Gateway . . . . . . . . . :
    >>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>
    >>> Tunnel adapter Local Area Connection* 14:
    >>>
    >>> Media State . . . . . . . . . . . : Media disconnected
    >>> Connection-specific DNS Suffix . :
    >>> Description . . . . . . . . . . . : 6TO4 Adapter
    >>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>> DHCP Enabled. . . . . . . . . . . : No
    >>> Autoconfiguration Enabled . . . . : Yes
    >>>
    >>> Tunnel adapter Local Area Connection* 10:
    >>>
    >>> Connection-specific DNS Suffix . : domain_not_set.invalid
    >>> Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
    >>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>> DHCP Enabled. . . . . . . . . . . : No
    >>> Autoconfiguration Enabled . . . . : Yes
    >>> Temporary IPv6 Address. . . . . . :
    >>> 2002:227f:ff27::227f:ff27(Preferred)
    >>> Default Gateway . . . . . . . . . : 2002:f058:6301::f058:6301
    >>> DNS Servers . . . . . . . . . . . : 192.168.0.1---*******************
    >>>
    >>> 192.168.0.1--*************************
    >>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>
    >>>
    >>>
    >>>
    >>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>> news:C5E12624-0EEF-4A6D-84C9-AF9BB6440665@microsoft.com...
    >>>> Open a command prompt and enter "ipconfig /all", without the quotes.
    >>>> What do you get?
    >>>>
    >>>> Other points in-line below.
    >>>>
    >>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>> news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...
    >>>>> 0016D3A2E7AD is my machines regular (wire) network card. The wireless
    >>>>> card is disabled in device manager (which presumably rules any wireles
    >>>>> connection out). 68.127.186.255 is AT&T's network, which is my ISP
    >>>>> (ARIN lookup below):
    >>>>>
    >>>>> AT&T Internet Services SBCIS-SIS80 (NET-68-120-0-0-1)
    >>>>> 68.120.0.0 - 68.127.255.255
    >>>>> bras4.pltnca SBC068127176000040211 (NET-68-127-176-0-1)
    >>>>> 68.127.176.0 - 68.127.191.255
    >>>>>
    >>>>> The constantly repeating reconnection notices at 5 minute intervals,
    >>>>> (with resulting successfully assigned IP addresses), is probably a
    >>>>> result of the fact that I remove the ethernet cable from my network
    >>>>> card whenever I step away from my machine.
    >>>>
    >>>> You really shouldn't do that. Only USB is generally safe to hot-plug.
    >>>> Sooner or later you're luck will run out and one or the other ethernet
    >>>> devices will fry. That aside, unplugging it doesn't account for those
    >>>> repeating reconnections. The timing is too consistent, down to the
    >>>> second.
    >>>>
    >>>>>
    >>>>> The only other remotely possible connection to my PC would have been
    >>>>> bluetooth, however the wireless card which provides bluetooth
    >>>>> connectivity is always turned off (at the switch).
    >>>>>
    >>>>> This leaves 2 questions
    >>>>>
    >>>>> 1) How could there be a master browser called JAYS showing up on my
    >>>>> logs (given the above).
    >>>>
    >>>> You would both have to be peers connected on the same LAN or directly
    >>>> to each other (same thing). Any PC on a LAN can be a master browser. I
    >>>> have one XP PC on mine that always insists on taking that status when
    >>>> it joins the LAN.
    >>>>
    >>>>> and (less importantly)
    >>>>>
    >>>>> 2) Why is my machine having a conversation with the outside world (my
    >>>>> ISP) about its workgroup. My understanding was that a workgroup would
    >>>>> be something that would be limited to my LAN alone.
    >>>>
    >>>> Let's see what ipconfig shows.
    >>>>
    >>>>>
    >>>>>
    >>>>>
    >>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>> news:6AD5B7D8-0DFF-4421-8DF9-3FF57637594C@microsoft.com...
    >>>>>> The anomalous name being in the router was only a suggestion, it's an
    >>>>>> option in mine that could also be in yours. As far as not finding the
    >>>>>> LAN DHCP server in the netbios table, this ....
    >>>>>>
    >>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None
    >>>>>> The IP
    >>>>>>>>> address lease 192.168.1.64 for the Network Card with network
    >>>>>>>>> address 0016D3A2E7AD has been denied by the DHCP server
    >>>>>>>>> 192.168.0.1 (The DHCP Server sent a DHCPNACK message).
    >>>>>>
    >>>>>> says that it exists, at least some of the time, and that your
    >>>>>> computer tried to use it with an incorrect network address and got
    >>>>>> booted. This on the other hand....
    >>>>>>
    >>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d""
    >>>>>>>>> could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>
    >>>>>> says your computer subsequently tried to connect to a server on the
    >>>>>> internet, probably your ISP, possibly somewhere else. There's no
    >>>>>> indication here whether it is the same network adapter making the
    >>>>>> connection as the one above but we can see from the text that your
    >>>>>> network adapter in this case also "somehow" had some incorrect
    >>>>>> information set in its configuration at the time.
    >>>>>>
    >>>>>> OTOH these constantly repeating reconnection notices at 5 minute
    >>>>>> intervals....
    >>>>>>
    >>>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>
    >>>>>> Are very much like what you can see happening with wireless
    >>>>>> connections. If I were going to make a guess as to what is going on
    >>>>>> here I'd say that apart from the ethernet adapter you connect to your
    >>>>>> own modem with you do have a wireless adapter in that computer, it is
    >>>>>> always turned on and it is set to automatically connect to any
    >>>>>> available network. Every so often your PC is piggybacking a ride, or
    >>>>>> trying to, on poor JAYS wireless network. :)
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>> news:OUZ0QCKhIHA.4740@TK2MSFTNGP05.phx.gbl...
    >>>>>>>
    >>>>>>> If JAYS were the name of the modem or in its netbios table, then it
    >>>>>>> should still be there presumably. (I have not reconfigured the
    >>>>>>> modem in several months, and at that I time I set it to factory
    >>>>>>> defaults - so the name JAYS should not be assigned to the modem).
    >>>>>>>
    >>>>>>> I checked the mode that the modem is operating. This is as follows:
    >>>>>>>
    >>>>>>> PPP is on the modem. (PPP session is initiated from the modem.) -
    >>>>>>> i.e. Not operating in Bridging mode
    >>>>>>>
    >>>>>>> I believe my DHCP server is assigned by the gateway, when I connect
    >>>>>>> (i.e. no static IP configured on my machine).
    >>>>>>>
    >>>>>>> I did a lookup of the netbios name table on my PC which I listed
    >>>>>>> below (When I tried nbtstat -a 192.168.0.1 for the modem I got "host
    >>>>>>> not found").
    >>>>>>>
    >>>>>>>
    >>>>>>> NetBIOS Local Name Table
    >>>>>>>
    >>>>>>> Name Type Status
    >>>>>>> ---------------------------------------------
    >>>>>>> MYPC <00> UNIQUE Registered
    >>>>>>> WORKGROUP <00> GROUP Registered
    >>>>>>> MYPC <20> UNIQUE Registered
    >>>>>>> WORKGROUP <1E> GROUP Registered
    >>>>>>> WORKGROUP <1D> UNIQUE Registered
    >>>>>>> ..__MSBROWSE__. <01> GROUP Registered
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>>>> news:EBF529EE-1C6A-4D4F-BB48-82EA200A86A9@microsoft.com...
    >>>>>>>> It looks like your network connection may be misconfigured. From
    >>>>>>>> the events at timestamp 10:01 and later it appears you have two
    >>>>>>>> conflicting DHCP services being used. You have a DHCP server at
    >>>>>>>> 192.168.0.1 which I presume is the DSL Modem with routing
    >>>>>>>> capabilities enabled. You are also trying to get a DHCP address
    >>>>>>>> directly from your ISP, probably using IP 68.127.186.255 as the
    >>>>>>>> DHCP server address. You should use only one or the other. I'd try
    >>>>>>>> turning off DHCP in the modem first and see how that works out.
    >>>>>>>>
    >>>>>>>> The modem can probably be configured in several different
    >>>>>>>> operating modes. I have no way of knowing what your available
    >>>>>>>> options are or which mode has been enabled. My own has 4 distinct
    >>>>>>>> DSL operating modes plus various combinations of routing and
    >>>>>>>> firewall features. IOW, there are umpteen ways to screw up the
    >>>>>>>> connection. :)
    >>>>>>>>
    >>>>>>>> Typically there are two common connection modes that might be used.
    >>>>>>>> One way is to have the modem set in 'bridge" mode, where it only
    >>>>>>>> makes the hardware connection to the DSL carrier signal. You would
    >>>>>>>> Windows built in PPPOE "dialer" to log into your ISP from your
    >>>>>>>> computer. In this configuration the ISP's DHCP server would give
    >>>>>>>> your computer an internet IP ... i.e.. 68.127.186.115. You would
    >>>>>>>> need to set up your ISP username and password in the PPPOE dialer
    >>>>>>>> to log on. Workgroup related settings in the PC would be irrelevant
    >>>>>>>> in this case as long as the computer can communicate to the modem.
    >>>>>>>> The PPPOE dialer is a virtual device which becomes the effective
    >>>>>>>> internet connection. All of the required settings information would
    >>>>>>>> be supplied by the ISP. Alternatively, a router could be used
    >>>>>>>> instead to make the connections through the modem when it is in
    >>>>>>>> this configuration.
    >>>>>>>>
    >>>>>>>> In the second configuration your modem could be set to connect to
    >>>>>>>> the ISP automatically using its own internal firmware. The relevant
    >>>>>>>> networking settings are made in the modem using its web interface,
    >>>>>>>> either by you yourself or sometimes this information is
    >>>>>>>> pre-programmed in the modem by the ISP if they supplied the modem.
    >>>>>>>> You can normally access the modem's web interface using your
    >>>>>>>> browser (try typing 192.168.0.1 in the address bar). The modem
    >>>>>>>> could be set to auto-dial (AKA always-on) or "dial on demand" mode
    >>>>>>>> (i.e.. the modem connects whenever the PC tries to access the
    >>>>>>>> internet and can disconnect again after a set timeout period of no
    >>>>>>>> activity). In this configuration it is the modem which gets the
    >>>>>>>> internet IP from your ISP and then passes the internet connection
    >>>>>>>> to the PC through its LAN port at address 192.168.0.1 (or whatever
    >>>>>>>> the default is). Routing and DHCP may or may not be enabled in the
    >>>>>>>> modem, but if they are enabled your computer should use 192.168.0.1
    >>>>>>>> as its DHCP server address and receive a LAN address from the
    >>>>>>>> modem, not an internet IP. Possibly 192.168.0.1 should be also
    >>>>>>>> entered into the computer's TCP/IP settings as the gateway address
    >>>>>>>> if DNS pass-through is enabled in the modem. Otherwise the ISP's
    >>>>>>>> DNS server addresses should be used. If DHCP is not enabled in the
    >>>>>>>> modem you would enter a fixed LAN address into the computer's
    >>>>>>>> TCP/IP configuration, in the range 192.168.0.x. The modem itself
    >>>>>>>> might have an optional workgroup or domain name entered into its
    >>>>>>>> LAN configuration settings, which is where 'JAYS' could be coming
    >>>>>>>> from. You can probably change or eliminate that yourself.
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>> news:%23ObFDy%23gIHA.5280@TK2MSFTNGP04.phx.gbl...
    >>>>>>>>> No its a dynamic IP Address assigned by my ISP
    >>>>>>>>>
    >>>>>>>>> I have attached all of the event log in the 3 hours around the
    >>>>>>>>> time of the browser conflict below. Im not sure if this contains
    >>>>>>>>> any other information which might give a clue as to what is going
    >>>>>>>>> on.
    >>>>>>>>>
    >>>>>>>>> Level Date and Time Source Event ID Task Category
    >>>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:22:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:17:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:12:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:11:07 PM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>> Information 3/5/2008 12:10:11 PM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>> Information 3/5/2008 12:07:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:02:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:00:46 PM EventLog 6013 None The system
    >>>>>>>>> uptime is 57335 seconds.
    >>>>>>>>> Information 3/5/2008 11:57:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 11:52:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 11:48:19 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 11:47:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 11:43:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 11:42:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 11:37:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 11:37:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 11:32:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 11:32:41 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>>>> status: 0.
    >>>>>>>>> Information 3/5/2008 11:32:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 11:28:17 AM BROWSER 8033 None The browser has
    >>>>>>>>> forced an election on network
    >>>>>>>>> DeviceNetBT_Tcpip_{6C1B0769-602C-49AD-95C1-0AD3B66DA864} because
    >>>>>>>>> a master browser was stopped.
    >>>>>>>>> Information 3/5/2008 11:24:52 AM Service Control Manager 7036 None
    >>>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>>> stopped state.
    >>>>>>>>> Information 3/5/2008 11:24:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 11:19:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 11:14:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 11:09:56 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>> Information 3/5/2008 11:09:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 11:08:55 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>> Information 3/5/2008 11:08:22 AM Service Control Manager 7036 None
    >>>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>>> running state.
    >>>>>>>>> Information 3/5/2008 11:05:06 AM volsnap 33 None The oldest shadow
    >>>>>>>>> copy of volume C: was deleted to keep disk space usage for shadow
    >>>>>>>>> copies of volume C: below the user defined limit.
    >>>>>>>>> Information 3/5/2008 11:04:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 10:59:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 10:54:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 10:49:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:45:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Error 3/5/2008 10:45:09 AM BROWSER 8009 None The browser was
    >>>>>>>>> unable to promote itself to master browser. The computer that
    >>>>>>>>> currently believes it is the master browser is JAYS.
    >>>>>>>>> Information 3/5/2008 10:44:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:39:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:39:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:34:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:34:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:29:38 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:29:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:24:28 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:24:21 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>>>> status: 0.
    >>>>>>>>> Information 3/5/2008 10:24:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 10:18:41 AM Service Control Manager 7036 None
    >>>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>>> stopped state.
    >>>>>>>>> Error 3/5/2008 10:17:06 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:16:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:11:54 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:11:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:06:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 10:05:43 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>> Information 3/5/2008 10:05:33 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>> Information 3/5/2008 10:05:26 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>> Information 3/5/2008 10:02:39 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>> Information 3/5/2008 10:02:11 AM Service Control Manager 7036 None
    >>>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>>> running state.
    >>>>>>>>> Information 3/5/2008 10:01:36 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>>>> status: 0.
    >>>>>>>>> Error 3/5/2008 10:01:30 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:01:17 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the following
    >>>>>>>>> status: 0.
    >>>>>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None
    >>>>>>>>> The IP address lease 192.168.1.64 for the Network Card with
    >>>>>>>>> network address 0016D3A2E7AD has been denied by the DHCP server
    >>>>>>>>> 192.168.0.1 (The DHCP Server sent a DHCPNACK message).
    >>>>>>>>> Warning 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1003
    >>>>>>>>> None "The description for Event ID 1003 from source
    >>>>>>>>> Microsoft-Windows-Dhcp-Client cannot be found. Either the
    >>>>>>>>> component that raises this event is not installed on your local
    >>>>>>>>> computer or the installation is corrupted. You can install or
    >>>>>>>>> repair the component on the local computer.
    >>>>>>>>>
    >>>>>>>>> If the event originated on another computer, the display
    >>>>>>>>> information had to be saved with the event.
    >>>>>>>>>
    >>>>>>>>> The following information was included with the event:
    >>>>>>>>>
    >>>>>>>>> 0016D3A2E7AD
    >>>>>>>>> %%2163146757
    >>>>>>>>>
    >>>>>>>>> The description string for parameter reference (%1) could not be
    >>>>>>>>> found
    >>>>>>>>> "
    >>>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 9:57:44 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>> Information 3/5/2008 9:57:37 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>> Information 3/5/2008 9:52:42 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>> Information 3/5/2008 9:52:35 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>> Information 3/5/2008 9:38:26 AM Service Control Manager 7036 None
    >>>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>>> stopped state.
    >>>>>>>>> Information 3/5/2008 9:37:56 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the following
    >>>>>>>>> status: 0.
    >>>>>>>>> Information 3/5/2008 9:37:48 AM Service Control Manager 7036 None
    >>>>>>>>> The Windows Image Acquisition (WIA) service entered the running
    >>>>>>>>> state.
    >>>>>>>>> Information 3/5/2008 9:37:39 AM
    >>>>>>>>> Microsoft-Windows-Power-Troubleshooter 1 None "The system has
    >>>>>>>>> resumed from sleep.
    >>>>>>>>>
    >>>>>>>>> Sleep Time: 3/5/2008 7:12:57 AM
    >>>>>>>>> Wake Time: 3/5/2008 5:37:34 PM
    >>>>>>>>>
    >>>>>>>>> Wake Source: Unknown"
    >>>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> "Bob F." <bob@NOSPAN.com> wrote in message
    >>>>>>>>> news:52055B79-F315-4C46-986D-CB8AFBFF2D37@microsoft.com...
    >>>>>>>>>> Where did you get the setup information for your internet
    >>>>>>>>>> connection? Did you use a static IP? Maybe it's incorrect and
    >>>>>>>>>> you are encroaching onto someone else's IP space.
    >>>>>>>>>>
    >>>>>>>>>> --
    >>>>>>>>>> BobF.
    >>>>>>>>>> "Dave" <dave@beepbeep.com> wrote in message
    >>>>>>>>>> news:eBrCR47gIHA.4436@TK2MSFTNGP02.phx.gbl...
    >>>>>>>>>>> What shows up in Start - Network?
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>>>>> news:#orAgk7gIHA.2448@TK2MSFTNGP03.phx.gbl...
    >>>>>>>>>>>> My (lone) machine is connected directly to the DSL router with
    >>>>>>>>>>>> no wireless capabilities on the router. Despite this I get the
    >>>>>>>>>>>> following message in the event log:
    >>>>>>>>>>>>
    >>>>>>>>>>>> The browser was unable to promote itself to master browser.
    >>>>>>>>>>>> The computer that currently believes it is the master browser
    >>>>>>>>>>>> is JAYS.
    >>>>>>>>>>>>
    >>>>>>>>>>>> Once again, my computer is not called JAYS. Friends and family
    >>>>>>>>>>>> are not Vista Security experts. Looking for capable / expert
    >>>>>>>>>>>> advice from this forum.
    >>>>>>>>>>>>
    >>>>>>>>>>>> What are the possible explanations for this???
    >>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>> "Malke" <malke@invalid.invalid> wrote in message
    >>>>>>>>>>>> news:O5eVD62gIHA.4692@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>>>>>> Nubie wrote:
    >>>>>>>>>>>>>
    >>>>>>>>>>>>>> What should I be looking for in the Settings?
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> ALSO: How would the config of my DSL modem confuse my vista
    >>>>>>>>>>>>>> machine to
    >>>>>>>>>>>>>> think that there is another computer called JAYS on my local
    >>>>>>>>>>>>>> network.
    >>>>>>>>>>>>>
    >>>>>>>>>>>>>>> Nubie;642434 Wrote:
    >>>>>>>>>>>>>>>> Hi
    >>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>> I have a single (lone) windows Vista machine connected
    >>>>>>>>>>>>>>>> directly to the
    >>>>>>>>>>>>>>>> internet via a dsl modem. I just viewed the following in my
    >>>>>>>>>>>>>>>> eventlogs:
    >>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>> "The browser was unable to promote itself to master
    >>>>>>>>>>>>>>>> browser. The
    >>>>>>>>>>>>>>>> computer
    >>>>>>>>>>>>>>>> that
    >>>>>>>>>>>>>>>> currently believes it is the master browser is JAYS. My
    >>>>>>>>>>>>>>>> machine is NOT
    >>>>>>>>>>>>>>>> called JAYS."
    >>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>> What is happening here!!?? If my machine is connected to a
    >>>>>>>>>>>>>>>> DSL modem
    >>>>>>>>>>>>>>>> with
    >>>>>>>>>>>>>>>> no additional
    >>>>>>>>>>>>>>>> machines connected to that modem why is this message
    >>>>>>>>>>>>>>>> appearing ????
    >>>>>>>>>>>>>>>> What is
    >>>>>>>>>>>>>>>> happening here ??
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> It certainly seems as though someone else is on your network.
    >>>>>>>>>>>>> Is this a
    >>>>>>>>>>>>> combination modem/wireless router? If yes, you probably
    >>>>>>>>>>>>> haven't secured
    >>>>>>>>>>>>> your wireless properly and a stranger is using your bandwidth.
    >>>>>>>>>>>>> If you only
    >>>>>>>>>>>>> have a single computer connected directly to a DSL modem by
    >>>>>>>>>>>>> ethernet cable
    >>>>>>>>>>>>> (no wireless router), then call your ISP. Because you don't
    >>>>>>>>>>>>> really know
    >>>>>>>>>>>>> what you're looking at - and I mean no disrespect to you, I'm
    >>>>>>>>>>>>> just being
    >>>>>>>>>>>>> practical - it might be smart for you to have a computer
    >>>>>>>>>>>>> professional come
    >>>>>>>>>>>>> on-site and take a look. This will not be someone from a
    >>>>>>>>>>>>> BigComputerStore/GeekSquad type of place. Get recommendations
    >>>>>>>>>>>>> from friends,
    >>>>>>>>>>>>> family, colleagues.
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> Malke
    >>>>>>>>>>>>> --
    >>>>>>>>>>>>> MS-MVP
    >>>>>>>>>>>>> Elephant Boy Computers
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> Don't Panic!
    >>>>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>><!--colorc--><!--/colorc-->
    >><!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     
    Bob F., Mar 15, 2008
    #27
  9. RalfG

    RalfG Guest

    Anything specific?
    Just based on my own configs, present and past ,with various hardware and
    Windows OS's. Trying to be as generic as possible under the circumstances.

    "Bob F." <bob@NOSPAN.com> wrote in message
    news:uOy1ZiuhIHA.3788@TK2MSFTNGP03.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > RalfG,
    > From where did you get your settings instructions?
    >
    > --
    > BobF.
    > "Nubie" <newsgoup_contact@atigen.com> wrote in message
    > news:eFDACeuhIHA.4140@TK2MSFTNGP04.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> The modem is set up for DNS forwarding, and the DNS IP's are configured
    >> on the modem. With regards to the NetBios over TCP/IP, I just disabled
    >> this (thanks for the advice).
    >>
    >> What is confusing me here is your comments regarding the DHCP server on
    >> the modem. Presumably, any internet IP address the modem gives me has to
    >> have come from the ISP. The ISP assigned the internet IP to the modem,
    >> the modem assigns this to me. (Even if I unplugged my machine from the
    >> modem for 30 mins).
    >>
    >> How would the above cause the confusion wrt another machine ('JAYS')
    >> appearing to be on my network?
    >> Somehow a NetBIOS message was broadcast, to this other machine on what
    >> the modem/router believed to be my network. How could this have
    >> happened?
    >>
    >>
    >> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >> news:C7150467-0DF3-49C9-BFFD-3D3B960F5041@microsoft.com...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> Looks like a bit of a dog's breakfast. :)
    >>> Questionable entries marked with -******************
    >>>
    >>> You said earlier that the computer was getting a dynamic IP from your
    >>> ISP but the way it is configured below I can't see that happening
    >>> reliably. You've got two conflicting DHCP services active.
    >>> The default Gateway is set to an internet IP but the DHCP server listed
    >>> is the modem/router, which presumable can only supply LAN addresses
    >>> within its own network subnet (192.168.0.x). Your ISP will have it's own
    >>> dedicated DHCP servers which are on internet IPs. That is where the
    >>> 68.127.175.71 address came from. Aside from that the modem's internal
    >>> DHCP server wouldn't know which internet IPs were available and which
    >>> ones were already being assigned to someone else. This could be where
    >>> your mystery connection is being created. Also the subnet mask for your
    >>> internet IP is set for the 192.168.0.x subnet rather than for internet
    >>> which is not okay.
    >>>
    >>> Your DNS server is set to a local LAN address (192.168.0.1) rather than
    >>> the ISP's DNS servers, which is probably okay if the modem/router has
    >>> the real DNS server addresses and DNS forwarding is enabled. Otherwise
    >>> these lines should be showing two different IPs from your ISP. NetBios
    >>> is enabled on your ethernet TCP/IP adapter but without NAT or firewall
    >>> protection in the modem/router this is not a good idea over an open
    >>> internet connection.
    >>>
    >>> It looks like the modem/router's actual LAN IP is 192.168.0.1. That's
    >>> the address you should browse to in IE to access the modem's
    >>> configuration pages. How you need to configure the computer's network
    >>> settings depends on how the modem has been configured but I think at the
    >>> very least you should be disabling the modem's onboard DHCP server if
    >>> your computer's adapter is intended to get an address automatically from
    >>> your ISP. Setting the router's DNS to pass-through mode rather than
    >>> forwarding isn't absolutely necessary but it eliminates the extra
    >>> rerouting step. In the various DNS Suffix lines I'd expect to see
    >>> entries referencing your ISP's domain name. I suspect the tunnel
    >>> adapters listed below are just redundant.
    >>>
    >>>
    >>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>> news:O3ZdjXihIHA.200@TK2MSFTNGP02.phx.gbl...
    >>>>
    >>>> Windows IP Configuration
    >>>>
    >>>> Host Name . . . . . . . . . . . . : mypc
    >>>> Primary Dns Suffix . . . . . . . :
    >>>> Node Type . . . . . . . . . . . . : Hybrid
    >>>> IP Routing Enabled. . . . . . . . : No
    >>>> WINS Proxy Enabled. . . . . . . . : No
    >>>> DNS Suffix Search List. . . . . . :
    >>>> domain_not_set.invalid--*******************
    >>>>
    >>>> Ethernet adapter Local Area Connection:
    >>>>
    >>>> Connection-specific DNS Suffix . :
    >>>> domain_not_set.invalid---************************
    >>>> Description . . . . . . . . . . . : NVIDIA nForce Networking
    >>>> Controller
    >>>> Physical Address. . . . . . . . . : 00-16-D3-A2-E7-AD
    >>>> DHCP Enabled. . . . . . . . . . . : Yes
    >>>> Autoconfiguration Enabled . . . . : Yes
    >>>> Link-local IPv6 Address . . . . . :
    >>>> ff80::80f6:625f:f376:8301%6(Preferred)
    >>>> IPv4 Address. . . . . . . . . . . : 68.127.175.71(Preferred)
    >>>> Subnet Mask . . . . . . . . . . . :
    >>>> 255.255.255.0 --*********************
    >>>> Lease Obtained. . . . . . . . . . : Friday, March 14, 2008 12:05:54
    >>>> PM
    >>>> Lease Expires . . . . . . . . . . : Friday, March 14, 2008 3:41:18 PM
    >>>> Default Gateway . . . . . . . . . : 68.127.175.72
    >>>> DHCP Server . . . . . . . . . . . :
    >>>> 192.168.0.1--*********************
    >>>> DHCPv6 IAID . . . . . . . . . . . : 203332435
    >>>> DNS Servers . . . . . . . . . . . :
    >>>> 192.168.0.1--*********************
    >>>>
    >>>> 192.168.0.1--*********************
    >>>> NetBIOS over Tcpip. . . . . . . . : Enabled
    >>>>
    >>>> Tunnel adapter Local Area Connection* 6:
    >>>>
    >>>> Connection-specific DNS Suffix . : domain_not_set.invalid
    >>>> Description . . . . . . . . . . . : isatap.domain_not_set.invalid
    >>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>>> DHCP Enabled. . . . . . . . . . . : No
    >>>> Autoconfiguration Enabled . . . . : Yes
    >>>> Link-local IPv6 Address . . . . . :
    >>>> ff80::200:5fff:68.128.185.71%14(Preferred
    >>>> )
    >>>> Default Gateway . . . . . . . . . :
    >>>> DNS Servers . . . . . . . . . . . : 192.168.0.1--******************
    >>>> 192.168.0.1--********************
    >>>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>>
    >>>> Tunnel adapter Local Area Connection* 7:
    >>>>
    >>>> Connection-specific DNS Suffix . :
    >>>> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    >>>> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    >>>> DHCP Enabled. . . . . . . . . . . : No
    >>>> Autoconfiguration Enabled . . . . : Yes
    >>>> IPv6 Address. . . . . . . . . . . :
    >>>> 2001:0:4337:9f66:18f9:3343:ff80:50f8(Pref
    >>>> erred)
    >>>> Link-local IPv6 Address . . . . . :
    >>>> ff80::38f9:3343:ff80:50f8%12(Preferred)
    >>>> Default Gateway . . . . . . . . . :
    >>>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>>
    >>>> Tunnel adapter Local Area Connection* 14:
    >>>>
    >>>> Media State . . . . . . . . . . . : Media disconnected
    >>>> Connection-specific DNS Suffix . :
    >>>> Description . . . . . . . . . . . : 6TO4 Adapter
    >>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>>> DHCP Enabled. . . . . . . . . . . : No
    >>>> Autoconfiguration Enabled . . . . : Yes
    >>>>
    >>>> Tunnel adapter Local Area Connection* 10:
    >>>>
    >>>> Connection-specific DNS Suffix . : domain_not_set.invalid
    >>>> Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
    >>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>>> DHCP Enabled. . . . . . . . . . . : No
    >>>> Autoconfiguration Enabled . . . . : Yes
    >>>> Temporary IPv6 Address. . . . . . :
    >>>> 2002:227f:ff27::227f:ff27(Preferred)
    >>>> Default Gateway . . . . . . . . . : 2002:f058:6301::f058:6301
    >>>> DNS Servers . . . . . . . . . . . : 192.168.0.1---*******************
    >>>>
    >>>> 192.168.0.1--*************************
    >>>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>>
    >>>>
    >>>>
    >>>>
    >>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>> news:C5E12624-0EEF-4A6D-84C9-AF9BB6440665@microsoft.com...
    >>>>> Open a command prompt and enter "ipconfig /all", without the quotes.
    >>>>> What do you get?
    >>>>>
    >>>>> Other points in-line below.
    >>>>>
    >>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>> news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...
    >>>>>> 0016D3A2E7AD is my machines regular (wire) network card. The
    >>>>>> wireless card is disabled in device manager (which presumably rules
    >>>>>> any wireles connection out). 68.127.186.255 is AT&T's network, which
    >>>>>> is my ISP (ARIN lookup below):
    >>>>>>
    >>>>>> AT&T Internet Services SBCIS-SIS80 (NET-68-120-0-0-1)
    >>>>>> 68.120.0.0 - 68.127.255.255
    >>>>>> bras4.pltnca SBC068127176000040211 (NET-68-127-176-0-1)
    >>>>>> 68.127.176.0 - 68.127.191.255
    >>>>>>
    >>>>>> The constantly repeating reconnection notices at 5 minute intervals,
    >>>>>> (with resulting successfully assigned IP addresses), is probably a
    >>>>>> result of the fact that I remove the ethernet cable from my network
    >>>>>> card whenever I step away from my machine.
    >>>>>
    >>>>> You really shouldn't do that. Only USB is generally safe to hot-plug.
    >>>>> Sooner or later you're luck will run out and one or the other ethernet
    >>>>> devices will fry. That aside, unplugging it doesn't account for those
    >>>>> repeating reconnections. The timing is too consistent, down to the
    >>>>> second.
    >>>>>
    >>>>>>
    >>>>>> The only other remotely possible connection to my PC would have been
    >>>>>> bluetooth, however the wireless card which provides bluetooth
    >>>>>> connectivity is always turned off (at the switch).
    >>>>>>
    >>>>>> This leaves 2 questions
    >>>>>>
    >>>>>> 1) How could there be a master browser called JAYS showing up on my
    >>>>>> logs (given the above).
    >>>>>
    >>>>> You would both have to be peers connected on the same LAN or directly
    >>>>> to each other (same thing). Any PC on a LAN can be a master browser. I
    >>>>> have one XP PC on mine that always insists on taking that status when
    >>>>> it joins the LAN.
    >>>>>
    >>>>>> and (less importantly)
    >>>>>>
    >>>>>> 2) Why is my machine having a conversation with the outside world (my
    >>>>>> ISP) about its workgroup. My understanding was that a workgroup
    >>>>>> would be something that would be limited to my LAN alone.
    >>>>>
    >>>>> Let's see what ipconfig shows.
    >>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>>> news:6AD5B7D8-0DFF-4421-8DF9-3FF57637594C@microsoft.com...
    >>>>>>> The anomalous name being in the router was only a suggestion, it's
    >>>>>>> an option in mine that could also be in yours. As far as not finding
    >>>>>>> the LAN DHCP server in the netbios table, this ....
    >>>>>>>
    >>>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None
    >>>>>>> The IP
    >>>>>>>>>> address lease 192.168.1.64 for the Network Card with network
    >>>>>>>>>> address 0016D3A2E7AD has been denied by the DHCP server
    >>>>>>>>>> 192.168.0.1 (The DHCP Server sent a DHCPNACK message).
    >>>>>>>
    >>>>>>> says that it exists, at least some of the time, and that your
    >>>>>>> computer tried to use it with an incorrect network address and got
    >>>>>>> booted. This on the other hand....
    >>>>>>>
    >>>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>> :1d""
    >>>>>>>>>> could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>
    >>>>>>> says your computer subsequently tried to connect to a server on the
    >>>>>>> internet, probably your ISP, possibly somewhere else. There's no
    >>>>>>> indication here whether it is the same network adapter making the
    >>>>>>> connection as the one above but we can see from the text that your
    >>>>>>> network adapter in this case also "somehow" had some incorrect
    >>>>>>> information set in its configuration at the time.
    >>>>>>>
    >>>>>>> OTOH these constantly repeating reconnection notices at 5 minute
    >>>>>>> intervals....
    >>>>>>>
    >>>>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>
    >>>>>>> Are very much like what you can see happening with wireless
    >>>>>>> connections. If I were going to make a guess as to what is going on
    >>>>>>> here I'd say that apart from the ethernet adapter you connect to
    >>>>>>> your own modem with you do have a wireless adapter in that computer,
    >>>>>>> it is always turned on and it is set to automatically connect to any
    >>>>>>> available network. Every so often your PC is piggybacking a ride, or
    >>>>>>> trying to, on poor JAYS wireless network. :)
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>> news:OUZ0QCKhIHA.4740@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>
    >>>>>>>> If JAYS were the name of the modem or in its netbios table, then it
    >>>>>>>> should still be there presumably. (I have not reconfigured the
    >>>>>>>> modem in several months, and at that I time I set it to factory
    >>>>>>>> defaults - so the name JAYS should not be assigned to the modem).
    >>>>>>>>
    >>>>>>>> I checked the mode that the modem is operating. This is as
    >>>>>>>> follows:
    >>>>>>>>
    >>>>>>>> PPP is on the modem. (PPP session is initiated from the modem.) -
    >>>>>>>> i.e. Not operating in Bridging mode
    >>>>>>>>
    >>>>>>>> I believe my DHCP server is assigned by the gateway, when I connect
    >>>>>>>> (i.e. no static IP configured on my machine).
    >>>>>>>>
    >>>>>>>> I did a lookup of the netbios name table on my PC which I listed
    >>>>>>>> below (When I tried nbtstat -a 192.168.0.1 for the modem I got
    >>>>>>>> "host not found").
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> NetBIOS Local Name Table
    >>>>>>>>
    >>>>>>>> Name Type Status
    >>>>>>>> ---------------------------------------------
    >>>>>>>> MYPC <00> UNIQUE Registered
    >>>>>>>> WORKGROUP <00> GROUP Registered
    >>>>>>>> MYPC <20> UNIQUE Registered
    >>>>>>>> WORKGROUP <1E> GROUP Registered
    >>>>>>>> WORKGROUP <1D> UNIQUE Registered
    >>>>>>>> ..__MSBROWSE__. <01> GROUP Registered
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>>>>> news:EBF529EE-1C6A-4D4F-BB48-82EA200A86A9@microsoft.com...
    >>>>>>>>> It looks like your network connection may be misconfigured. From
    >>>>>>>>> the events at timestamp 10:01 and later it appears you have two
    >>>>>>>>> conflicting DHCP services being used. You have a DHCP server at
    >>>>>>>>> 192.168.0.1 which I presume is the DSL Modem with routing
    >>>>>>>>> capabilities enabled. You are also trying to get a DHCP address
    >>>>>>>>> directly from your ISP, probably using IP 68.127.186.255 as the
    >>>>>>>>> DHCP server address. You should use only one or the other. I'd try
    >>>>>>>>> turning off DHCP in the modem first and see how that works out.
    >>>>>>>>>
    >>>>>>>>> The modem can probably be configured in several different
    >>>>>>>>> operating modes. I have no way of knowing what your available
    >>>>>>>>> options are or which mode has been enabled. My own has 4 distinct
    >>>>>>>>> DSL operating modes plus various combinations of routing and
    >>>>>>>>> firewall features. IOW, there are umpteen ways to screw up the
    >>>>>>>>> connection. :)
    >>>>>>>>>
    >>>>>>>>> Typically there are two common connection modes that might be
    >>>>>>>>> used. One way is to have the modem set in 'bridge" mode, where it
    >>>>>>>>> only makes the hardware connection to the DSL carrier signal. You
    >>>>>>>>> would Windows built in PPPOE "dialer" to log into your ISP from
    >>>>>>>>> your computer. In this configuration the ISP's DHCP server would
    >>>>>>>>> give your computer an internet IP ... i.e.. 68.127.186.115. You
    >>>>>>>>> would need to set up your ISP username and password in the PPPOE
    >>>>>>>>> dialer to log on. Workgroup related settings in the PC would be
    >>>>>>>>> irrelevant in this case as long as the computer can communicate to
    >>>>>>>>> the modem. The PPPOE dialer is a virtual device which becomes the
    >>>>>>>>> effective internet connection. All of the required settings
    >>>>>>>>> information would be supplied by the ISP. Alternatively, a router
    >>>>>>>>> could be used instead to make the connections through the modem
    >>>>>>>>> when it is in this configuration.
    >>>>>>>>>
    >>>>>>>>> In the second configuration your modem could be set to connect to
    >>>>>>>>> the ISP automatically using its own internal firmware. The
    >>>>>>>>> relevant networking settings are made in the modem using its web
    >>>>>>>>> interface, either by you yourself or sometimes this information is
    >>>>>>>>> pre-programmed in the modem by the ISP if they supplied the modem.
    >>>>>>>>> You can normally access the modem's web interface using your
    >>>>>>>>> browser (try typing 192.168.0.1 in the address bar). The modem
    >>>>>>>>> could be set to auto-dial (AKA always-on) or "dial on demand"
    >>>>>>>>> mode (i.e.. the modem connects whenever the PC tries to access the
    >>>>>>>>> internet and can disconnect again after a set timeout period of no
    >>>>>>>>> activity). In this configuration it is the modem which gets the
    >>>>>>>>> internet IP from your ISP and then passes the internet connection
    >>>>>>>>> to the PC through its LAN port at address 192.168.0.1 (or whatever
    >>>>>>>>> the default is). Routing and DHCP may or may not be enabled in the
    >>>>>>>>> modem, but if they are enabled your computer should use
    >>>>>>>>> 192.168.0.1 as its DHCP server address and receive a LAN address
    >>>>>>>>> from the modem, not an internet IP. Possibly 192.168.0.1 should be
    >>>>>>>>> also entered into the computer's TCP/IP settings as the gateway
    >>>>>>>>> address if DNS pass-through is enabled in the modem. Otherwise the
    >>>>>>>>> ISP's DNS server addresses should be used. If DHCP is not enabled
    >>>>>>>>> in the modem you would enter a fixed LAN address into the
    >>>>>>>>> computer's TCP/IP configuration, in the range 192.168.0.x. The
    >>>>>>>>> modem itself might have an optional workgroup or domain name
    >>>>>>>>> entered into its LAN configuration settings, which is where 'JAYS'
    >>>>>>>>> could be coming from. You can probably change or eliminate that
    >>>>>>>>> yourself.
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>>> news:%23ObFDy%23gIHA.5280@TK2MSFTNGP04.phx.gbl...
    >>>>>>>>>> No its a dynamic IP Address assigned by my ISP
    >>>>>>>>>>
    >>>>>>>>>> I have attached all of the event log in the 3 hours around the
    >>>>>>>>>> time of the browser conflict below. Im not sure if this contains
    >>>>>>>>>> any other information which might give a clue as to what is going
    >>>>>>>>>> on.
    >>>>>>>>>>
    >>>>>>>>>> Level Date and Time Source Event ID Task Category
    >>>>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 12:22:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 12:17:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 12:12:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 12:11:07 PM Service Control Manager 7036
    >>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>> Information 3/5/2008 12:10:11 PM Service Control Manager 7036
    >>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>> Information 3/5/2008 12:07:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 12:02:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 12:00:46 PM EventLog 6013 None The system
    >>>>>>>>>> uptime is 57335 seconds.
    >>>>>>>>>> Information 3/5/2008 11:57:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 11:52:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Error 3/5/2008 11:48:19 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Information 3/5/2008 11:47:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Error 3/5/2008 11:43:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Information 3/5/2008 11:42:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Error 3/5/2008 11:37:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Information 3/5/2008 11:37:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Error 3/5/2008 11:32:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Information 3/5/2008 11:32:41 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the
    >>>>>>>>>> following status: 0.
    >>>>>>>>>> Information 3/5/2008 11:32:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>>> Information 3/5/2008 11:28:17 AM BROWSER 8033 None The browser
    >>>>>>>>>> has forced an election on network
    >>>>>>>>>> DeviceNetBT_Tcpip_{6C1B0769-602C-49AD-95C1-0AD3B66DA864}
    >>>>>>>>>> because a master browser was stopped.
    >>>>>>>>>> Information 3/5/2008 11:24:52 AM Service Control Manager 7036
    >>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service entered
    >>>>>>>>>> the stopped state.
    >>>>>>>>>> Information 3/5/2008 11:24:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 11:19:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 11:14:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 11:09:56 AM Service Control Manager 7036
    >>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>> Information 3/5/2008 11:09:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 11:08:55 AM Service Control Manager 7036
    >>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>> Information 3/5/2008 11:08:22 AM Service Control Manager 7036
    >>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service entered
    >>>>>>>>>> the running state.
    >>>>>>>>>> Information 3/5/2008 11:05:06 AM volsnap 33 None The oldest
    >>>>>>>>>> shadow copy of volume C: was deleted to keep disk space usage for
    >>>>>>>>>> shadow copies of volume C: below the user defined limit.
    >>>>>>>>>> Information 3/5/2008 11:04:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 10:59:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 10:54:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 10:49:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Error 3/5/2008 10:45:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Error 3/5/2008 10:45:09 AM BROWSER 8009 None The browser was
    >>>>>>>>>> unable to promote itself to master browser. The computer that
    >>>>>>>>>> currently believes it is the master browser is JAYS.
    >>>>>>>>>> Information 3/5/2008 10:44:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Error 3/5/2008 10:39:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Information 3/5/2008 10:39:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Error 3/5/2008 10:34:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Information 3/5/2008 10:34:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Error 3/5/2008 10:29:38 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Information 3/5/2008 10:29:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Error 3/5/2008 10:24:28 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Information 3/5/2008 10:24:21 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the
    >>>>>>>>>> following status: 0.
    >>>>>>>>>> Information 3/5/2008 10:24:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>>> Information 3/5/2008 10:18:41 AM Service Control Manager 7036
    >>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service entered
    >>>>>>>>>> the stopped state.
    >>>>>>>>>> Error 3/5/2008 10:17:06 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Information 3/5/2008 10:16:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Error 3/5/2008 10:11:54 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Information 3/5/2008 10:11:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Information 3/5/2008 10:06:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>>> Information 3/5/2008 10:05:43 AM Service Control Manager 7036
    >>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>> Information 3/5/2008 10:05:33 AM Service Control Manager 7036
    >>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>> Information 3/5/2008 10:05:26 AM Service Control Manager 7036
    >>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>> Information 3/5/2008 10:02:39 AM Service Control Manager 7036
    >>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>> Information 3/5/2008 10:02:11 AM Service Control Manager 7036
    >>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service entered
    >>>>>>>>>> the running state.
    >>>>>>>>>> Information 3/5/2008 10:01:36 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the
    >>>>>>>>>> following status: 0.
    >>>>>>>>>> Error 3/5/2008 10:01:30 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>> Information 3/5/2008 10:01:17 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the
    >>>>>>>>>> following status: 0.
    >>>>>>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002
    >>>>>>>>>> None The IP address lease 192.168.1.64 for the Network Card with
    >>>>>>>>>> network address 0016D3A2E7AD has been denied by the DHCP server
    >>>>>>>>>> 192.168.0.1 (The DHCP Server sent a DHCPNACK message).
    >>>>>>>>>> Warning 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1003
    >>>>>>>>>> None "The description for Event ID 1003 from source
    >>>>>>>>>> Microsoft-Windows-Dhcp-Client cannot be found. Either the
    >>>>>>>>>> component that raises this event is not installed on your local
    >>>>>>>>>> computer or the installation is corrupted. You can install or
    >>>>>>>>>> repair the component on the local computer.
    >>>>>>>>>>
    >>>>>>>>>> If the event originated on another computer, the display
    >>>>>>>>>> information had to be saved with the event.
    >>>>>>>>>>
    >>>>>>>>>> The following information was included with the event:
    >>>>>>>>>>
    >>>>>>>>>> 0016D3A2E7AD
    >>>>>>>>>> %%2163146757
    >>>>>>>>>>
    >>>>>>>>>> The description string for parameter reference (%1) could not be
    >>>>>>>>>> found
    >>>>>>>>>> "
    >>>>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>>> Information 3/5/2008 9:57:44 AM Service Control Manager 7036 None
    >>>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>>> Information 3/5/2008 9:57:37 AM Service Control Manager 7036 None
    >>>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>>> Information 3/5/2008 9:52:42 AM Service Control Manager 7036 None
    >>>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>>> Information 3/5/2008 9:52:35 AM Service Control Manager 7036 None
    >>>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>>> Information 3/5/2008 9:38:26 AM Service Control Manager 7036 None
    >>>>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>>>> stopped state.
    >>>>>>>>>> Information 3/5/2008 9:37:56 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the
    >>>>>>>>>> following status: 0.
    >>>>>>>>>> Information 3/5/2008 9:37:48 AM Service Control Manager 7036 None
    >>>>>>>>>> The Windows Image Acquisition (WIA) service entered the running
    >>>>>>>>>> state.
    >>>>>>>>>> Information 3/5/2008 9:37:39 AM
    >>>>>>>>>> Microsoft-Windows-Power-Troubleshooter 1 None "The system has
    >>>>>>>>>> resumed from sleep.
    >>>>>>>>>>
    >>>>>>>>>> Sleep Time: 3/5/2008 7:12:57 AM
    >>>>>>>>>> Wake Time: 3/5/2008 5:37:34 PM
    >>>>>>>>>>
    >>>>>>>>>> Wake Source: Unknown"
    >>>>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system
    >>>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system
    >>>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>> "Bob F." <bob@NOSPAN.com> wrote in message
    >>>>>>>>>> news:52055B79-F315-4C46-986D-CB8AFBFF2D37@microsoft.com...
    >>>>>>>>>>> Where did you get the setup information for your internet
    >>>>>>>>>>> connection? Did you use a static IP? Maybe it's incorrect and
    >>>>>>>>>>> you are encroaching onto someone else's IP space.
    >>>>>>>>>>>
    >>>>>>>>>>> --
    >>>>>>>>>>> BobF.
    >>>>>>>>>>> "Dave" <dave@beepbeep.com> wrote in message
    >>>>>>>>>>> news:eBrCR47gIHA.4436@TK2MSFTNGP02.phx.gbl...
    >>>>>>>>>>>> What shows up in Start - Network?
    >>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>>>>>> news:#orAgk7gIHA.2448@TK2MSFTNGP03.phx.gbl...
    >>>>>>>>>>>>> My (lone) machine is connected directly to the DSL router with
    >>>>>>>>>>>>> no wireless capabilities on the router. Despite this I get
    >>>>>>>>>>>>> the following message in the event log:
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> The browser was unable to promote itself to master browser.
    >>>>>>>>>>>>> The computer that currently believes it is the master browser
    >>>>>>>>>>>>> is JAYS.
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> Once again, my computer is not called JAYS. Friends and
    >>>>>>>>>>>>> family are not Vista Security experts. Looking for capable /
    >>>>>>>>>>>>> expert advice from this forum.
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> What are the possible explanations for this???
    >>>>>>>>>>>>>
    >>>>>>>>>>>>>
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> "Malke" <malke@invalid.invalid> wrote in message
    >>>>>>>>>>>>> news:O5eVD62gIHA.4692@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>>>>>>> Nubie wrote:
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> What should I be looking for in the Settings?
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> ALSO: How would the config of my DSL modem confuse my vista
    >>>>>>>>>>>>>>> machine to
    >>>>>>>>>>>>>>> think that there is another computer called JAYS on my local
    >>>>>>>>>>>>>>> network.
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>> Nubie;642434 Wrote:
    >>>>>>>>>>>>>>>>> Hi
    >>>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>> I have a single (lone) windows Vista machine connected
    >>>>>>>>>>>>>>>>> directly to the
    >>>>>>>>>>>>>>>>> internet via a dsl modem. I just viewed the following in
    >>>>>>>>>>>>>>>>> my eventlogs:
    >>>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>> "The browser was unable to promote itself to master
    >>>>>>>>>>>>>>>>> browser. The
    >>>>>>>>>>>>>>>>> computer
    >>>>>>>>>>>>>>>>> that
    >>>>>>>>>>>>>>>>> currently believes it is the master browser is JAYS. My
    >>>>>>>>>>>>>>>>> machine is NOT
    >>>>>>>>>>>>>>>>> called JAYS."
    >>>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>> What is happening here!!?? If my machine is connected to a
    >>>>>>>>>>>>>>>>> DSL modem
    >>>>>>>>>>>>>>>>> with
    >>>>>>>>>>>>>>>>> no additional
    >>>>>>>>>>>>>>>>> machines connected to that modem why is this message
    >>>>>>>>>>>>>>>>> appearing ????
    >>>>>>>>>>>>>>>>> What is
    >>>>>>>>>>>>>>>>> happening here ??
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> It certainly seems as though someone else is on your network.
    >>>>>>>>>>>>>> Is this a
    >>>>>>>>>>>>>> combination modem/wireless router? If yes, you probably
    >>>>>>>>>>>>>> haven't secured
    >>>>>>>>>>>>>> your wireless properly and a stranger is using your
    >>>>>>>>>>>>>> bandwidth. If you only
    >>>>>>>>>>>>>> have a single computer connected directly to a DSL modem by
    >>>>>>>>>>>>>> ethernet cable
    >>>>>>>>>>>>>> (no wireless router), then call your ISP. Because you don't
    >>>>>>>>>>>>>> really know
    >>>>>>>>>>>>>> what you're looking at - and I mean no disrespect to you, I'm
    >>>>>>>>>>>>>> just being
    >>>>>>>>>>>>>> practical - it might be smart for you to have a computer
    >>>>>>>>>>>>>> professional come
    >>>>>>>>>>>>>> on-site and take a look. This will not be someone from a
    >>>>>>>>>>>>>> BigComputerStore/GeekSquad type of place. Get recommendations
    >>>>>>>>>>>>>> from friends,
    >>>>>>>>>>>>>> family, colleagues.
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> Malke
    >>>>>>>>>>>>>> --
    >>>>>>>>>>>>>> MS-MVP
    >>>>>>>>>>>>>> Elephant Boy Computers
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> Don't Panic!
    >>>>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>><!--colorc--><!--/colorc-->
    >><!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     
    RalfG, Mar 15, 2008
    #28
  10. Bob F.

    Bob F. Guest

    Well, I am afraid to say, you can't just do that. Network provider have
    and architecture that they follow that dictate how you should set up you
    modem and router (if you have one). Some have static IPs (but are fading
    out fast). Some want the IP to go to you modem and pass through, others
    expect your modem/router DNS to be turned on and a (NAT) translation to
    occur and you have your local DNS on. And other things. You can't mix the
    settings rules they set up and it's hard to predict what they want unless
    it's a known carrier with some of the very common setup we all know by now.
    This is probably why JAYS is showing up. So you said you sent a query into
    your provider. I'd suggest calling them. Tell them it is an initial setup
    and you need directions. BTW your modem is on their approved list. Is it
    not.? I am also surprised you can not get to their help/setup page, from
    another computer maybe. The setup info has got to be there for you. You
    are not alone. Please check with them.

    --
    BobF.
    "RalfG" <itsnotme@ladeda.deda> wrote in message
    news:BF84F798-CE74-408B-BE52-F5D7C90E889B@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Anything specific?
    > Just based on my own configs, present and past ,with various hardware and
    > Windows OS's. Trying to be as generic as possible under the circumstances.
    >
    > "Bob F." <bob@NOSPAN.com> wrote in message
    > news:uOy1ZiuhIHA.3788@TK2MSFTNGP03.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> RalfG,
    >> From where did you get your settings instructions?
    >>
    >> --
    >> BobF.
    >> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >> news:eFDACeuhIHA.4140@TK2MSFTNGP04.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> The modem is set up for DNS forwarding, and the DNS IP's are configured
    >>> on the modem. With regards to the NetBios over TCP/IP, I just disabled
    >>> this (thanks for the advice).
    >>>
    >>> What is confusing me here is your comments regarding the DHCP server on
    >>> the modem. Presumably, any internet IP address the modem gives me has
    >>> to have come from the ISP. The ISP assigned the internet IP to the
    >>> modem, the modem assigns this to me. (Even if I unplugged my machine
    >>> from the modem for 30 mins).
    >>>
    >>> How would the above cause the confusion wrt another machine ('JAYS')
    >>> appearing to be on my network?
    >>> Somehow a NetBIOS message was broadcast, to this other machine on what
    >>> the modem/router believed to be my network. How could this have
    >>> happened?
    >>>
    >>>
    >>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>> news:C7150467-0DF3-49C9-BFFD-3D3B960F5041@microsoft.com...
    >>>> Looks like a bit of a dog's breakfast. :)
    >>>> Questionable entries marked with -******************
    >>>>
    >>>> You said earlier that the computer was getting a dynamic IP from your
    >>>> ISP but the way it is configured below I can't see that happening
    >>>> reliably. You've got two conflicting DHCP services active.
    >>>> The default Gateway is set to an internet IP but the DHCP server listed
    >>>> is the modem/router, which presumable can only supply LAN addresses
    >>>> within its own network subnet (192.168.0.x). Your ISP will have it's
    >>>> own dedicated DHCP servers which are on internet IPs. That is where the
    >>>> 68.127.175.71 address came from. Aside from that the modem's internal
    >>>> DHCP server wouldn't know which internet IPs were available and which
    >>>> ones were already being assigned to someone else. This could be where
    >>>> your mystery connection is being created. Also the subnet mask for your
    >>>> internet IP is set for the 192.168.0.x subnet rather than for internet
    >>>> which is not okay.
    >>>>
    >>>> Your DNS server is set to a local LAN address (192.168.0.1) rather than
    >>>> the ISP's DNS servers, which is probably okay if the modem/router has
    >>>> the real DNS server addresses and DNS forwarding is enabled. Otherwise
    >>>> these lines should be showing two different IPs from your ISP. NetBios
    >>>> is enabled on your ethernet TCP/IP adapter but without NAT or firewall
    >>>> protection in the modem/router this is not a good idea over an open
    >>>> internet connection.
    >>>>
    >>>> It looks like the modem/router's actual LAN IP is 192.168.0.1. That's
    >>>> the address you should browse to in IE to access the modem's
    >>>> configuration pages. How you need to configure the computer's network
    >>>> settings depends on how the modem has been configured but I think at
    >>>> the very least you should be disabling the modem's onboard DHCP server
    >>>> if your computer's adapter is intended to get an address automatically
    >>>> from your ISP. Setting the router's DNS to pass-through mode rather
    >>>> than forwarding isn't absolutely necessary but it eliminates the extra
    >>>> rerouting step. In the various DNS Suffix lines I'd expect to see
    >>>> entries referencing your ISP's domain name. I suspect the tunnel
    >>>> adapters listed below are just redundant.
    >>>>
    >>>>
    >>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>> news:O3ZdjXihIHA.200@TK2MSFTNGP02.phx.gbl...
    >>>>>
    >>>>> Windows IP Configuration
    >>>>>
    >>>>> Host Name . . . . . . . . . . . . : mypc
    >>>>> Primary Dns Suffix . . . . . . . :
    >>>>> Node Type . . . . . . . . . . . . : Hybrid
    >>>>> IP Routing Enabled. . . . . . . . : No
    >>>>> WINS Proxy Enabled. . . . . . . . : No
    >>>>> DNS Suffix Search List. . . . . . :
    >>>>> domain_not_set.invalid--*******************
    >>>>>
    >>>>> Ethernet adapter Local Area Connection:
    >>>>>
    >>>>> Connection-specific DNS Suffix . :
    >>>>> domain_not_set.invalid---************************
    >>>>> Description . . . . . . . . . . . : NVIDIA nForce Networking
    >>>>> Controller
    >>>>> Physical Address. . . . . . . . . : 00-16-D3-A2-E7-AD
    >>>>> DHCP Enabled. . . . . . . . . . . : Yes
    >>>>> Autoconfiguration Enabled . . . . : Yes
    >>>>> Link-local IPv6 Address . . . . . :
    >>>>> ff80::80f6:625f:f376:8301%6(Preferred)
    >>>>> IPv4 Address. . . . . . . . . . . : 68.127.175.71(Preferred)
    >>>>> Subnet Mask . . . . . . . . . . . :
    >>>>> 255.255.255.0 --*********************
    >>>>> Lease Obtained. . . . . . . . . . : Friday, March 14, 2008 12:05:54
    >>>>> PM
    >>>>> Lease Expires . . . . . . . . . . : Friday, March 14, 2008 3:41:18
    >>>>> PM
    >>>>> Default Gateway . . . . . . . . . : 68.127.175.72
    >>>>> DHCP Server . . . . . . . . . . . :
    >>>>> 192.168.0.1--*********************
    >>>>> DHCPv6 IAID . . . . . . . . . . . : 203332435
    >>>>> DNS Servers . . . . . . . . . . . :
    >>>>> 192.168.0.1--*********************
    >>>>>
    >>>>> 192.168.0.1--*********************
    >>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
    >>>>>
    >>>>> Tunnel adapter Local Area Connection* 6:
    >>>>>
    >>>>> Connection-specific DNS Suffix . : domain_not_set.invalid
    >>>>> Description . . . . . . . . . . . : isatap.domain_not_set.invalid
    >>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>>>> DHCP Enabled. . . . . . . . . . . : No
    >>>>> Autoconfiguration Enabled . . . . : Yes
    >>>>> Link-local IPv6 Address . . . . . :
    >>>>> ff80::200:5fff:68.128.185.71%14(Preferred
    >>>>> )
    >>>>> Default Gateway . . . . . . . . . :
    >>>>> DNS Servers . . . . . . . . . . . : 192.168.0.1--******************
    >>>>>
    >>>>> 192.168.0.1--********************
    >>>>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>>>
    >>>>> Tunnel adapter Local Area Connection* 7:
    >>>>>
    >>>>> Connection-specific DNS Suffix . :
    >>>>> Description . . . . . . . . . . . : Teredo Tunneling
    >>>>> Pseudo-Interface
    >>>>> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    >>>>> DHCP Enabled. . . . . . . . . . . : No
    >>>>> Autoconfiguration Enabled . . . . : Yes
    >>>>> IPv6 Address. . . . . . . . . . . :
    >>>>> 2001:0:4337:9f66:18f9:3343:ff80:50f8(Pref
    >>>>> erred)
    >>>>> Link-local IPv6 Address . . . . . :
    >>>>> ff80::38f9:3343:ff80:50f8%12(Preferred)
    >>>>> Default Gateway . . . . . . . . . :
    >>>>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>>>
    >>>>> Tunnel adapter Local Area Connection* 14:
    >>>>>
    >>>>> Media State . . . . . . . . . . . : Media disconnected
    >>>>> Connection-specific DNS Suffix . :
    >>>>> Description . . . . . . . . . . . : 6TO4 Adapter
    >>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>>>> DHCP Enabled. . . . . . . . . . . : No
    >>>>> Autoconfiguration Enabled . . . . : Yes
    >>>>>
    >>>>> Tunnel adapter Local Area Connection* 10:
    >>>>>
    >>>>> Connection-specific DNS Suffix . : domain_not_set.invalid
    >>>>> Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
    >>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>>>> DHCP Enabled. . . . . . . . . . . : No
    >>>>> Autoconfiguration Enabled . . . . : Yes
    >>>>> Temporary IPv6 Address. . . . . . :
    >>>>> 2002:227f:ff27::227f:ff27(Preferred)
    >>>>> Default Gateway . . . . . . . . . : 2002:f058:6301::f058:6301
    >>>>> DNS Servers . . . . . . . . . . . :
    >>>>> 192.168.0.1---*******************
    >>>>>
    >>>>> 192.168.0.1--*************************
    >>>>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>>>
    >>>>>
    >>>>>
    >>>>>
    >>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>> news:C5E12624-0EEF-4A6D-84C9-AF9BB6440665@microsoft.com...
    >>>>>> Open a command prompt and enter "ipconfig /all", without the quotes.
    >>>>>> What do you get?
    >>>>>>
    >>>>>> Other points in-line below.
    >>>>>>
    >>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>> news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...
    >>>>>>> 0016D3A2E7AD is my machines regular (wire) network card. The
    >>>>>>> wireless card is disabled in device manager (which presumably rules
    >>>>>>> any wireles connection out). 68.127.186.255 is AT&T's network,
    >>>>>>> which is my ISP (ARIN lookup below):
    >>>>>>>
    >>>>>>> AT&T Internet Services SBCIS-SIS80 (NET-68-120-0-0-1)
    >>>>>>> 68.120.0.0 - 68.127.255.255
    >>>>>>> bras4.pltnca SBC068127176000040211 (NET-68-127-176-0-1)
    >>>>>>> 68.127.176.0 - 68.127.191.255
    >>>>>>>
    >>>>>>> The constantly repeating reconnection notices at 5 minute intervals,
    >>>>>>> (with resulting successfully assigned IP addresses), is probably a
    >>>>>>> result of the fact that I remove the ethernet cable from my network
    >>>>>>> card whenever I step away from my machine.
    >>>>>>
    >>>>>> You really shouldn't do that. Only USB is generally safe to hot-plug.
    >>>>>> Sooner or later you're luck will run out and one or the other
    >>>>>> ethernet devices will fry. That aside, unplugging it doesn't account
    >>>>>> for those repeating reconnections. The timing is too consistent, down
    >>>>>> to the second.
    >>>>>>
    >>>>>>>
    >>>>>>> The only other remotely possible connection to my PC would have been
    >>>>>>> bluetooth, however the wireless card which provides bluetooth
    >>>>>>> connectivity is always turned off (at the switch).
    >>>>>>>
    >>>>>>> This leaves 2 questions
    >>>>>>>
    >>>>>>> 1) How could there be a master browser called JAYS showing up on my
    >>>>>>> logs (given the above).
    >>>>>>
    >>>>>> You would both have to be peers connected on the same LAN or directly
    >>>>>> to each other (same thing). Any PC on a LAN can be a master browser.
    >>>>>> I have one XP PC on mine that always insists on taking that status
    >>>>>> when it joins the LAN.
    >>>>>>
    >>>>>>> and (less importantly)
    >>>>>>>
    >>>>>>> 2) Why is my machine having a conversation with the outside world
    >>>>>>> (my ISP) about its workgroup. My understanding was that a workgroup
    >>>>>>> would be something that would be limited to my LAN alone.
    >>>>>>
    >>>>>> Let's see what ipconfig shows.
    >>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>>>> news:6AD5B7D8-0DFF-4421-8DF9-3FF57637594C@microsoft.com...
    >>>>>>>> The anomalous name being in the router was only a suggestion, it's
    >>>>>>>> an option in mine that could also be in yours. As far as not
    >>>>>>>> finding the LAN DHCP server in the netbios table, this ....
    >>>>>>>>
    >>>>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None
    >>>>>>>> The IP
    >>>>>>>>>>> address lease 192.168.1.64 for the Network Card with network
    >>>>>>>>>>> address 0016D3A2E7AD has been denied by the DHCP server
    >>>>>>>>>>> 192.168.0.1 (The DHCP Server sent a DHCPNACK message).
    >>>>>>>>
    >>>>>>>> says that it exists, at least some of the time, and that your
    >>>>>>>> computer tried to use it with an incorrect network address and got
    >>>>>>>> booted. This on the other hand....
    >>>>>>>>
    >>>>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>> :1d""
    >>>>>>>>>>> could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>
    >>>>>>>> says your computer subsequently tried to connect to a server on the
    >>>>>>>> internet, probably your ISP, possibly somewhere else. There's no
    >>>>>>>> indication here whether it is the same network adapter making the
    >>>>>>>> connection as the one above but we can see from the text that your
    >>>>>>>> network adapter in this case also "somehow" had some incorrect
    >>>>>>>> information set in its configuration at the time.
    >>>>>>>>
    >>>>>>>> OTOH these constantly repeating reconnection notices at 5 minute
    >>>>>>>> intervals....
    >>>>>>>>
    >>>>>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>
    >>>>>>>> Are very much like what you can see happening with wireless
    >>>>>>>> connections. If I were going to make a guess as to what is going on
    >>>>>>>> here I'd say that apart from the ethernet adapter you connect to
    >>>>>>>> your own modem with you do have a wireless adapter in that
    >>>>>>>> computer, it is always turned on and it is set to automatically
    >>>>>>>> connect to any available network. Every so often your PC is
    >>>>>>>> piggybacking a ride, or trying to, on poor JAYS wireless network.
    >>>>>>>> :)
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>> news:OUZ0QCKhIHA.4740@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>>
    >>>>>>>>> If JAYS were the name of the modem or in its netbios table, then
    >>>>>>>>> it should still be there presumably. (I have not reconfigured the
    >>>>>>>>> modem in several months, and at that I time I set it to factory
    >>>>>>>>> defaults - so the name JAYS should not be assigned to the modem).
    >>>>>>>>>
    >>>>>>>>> I checked the mode that the modem is operating. This is as
    >>>>>>>>> follows:
    >>>>>>>>>
    >>>>>>>>> PPP is on the modem. (PPP session is initiated from the modem.) -
    >>>>>>>>> i.e. Not operating in Bridging mode
    >>>>>>>>>
    >>>>>>>>> I believe my DHCP server is assigned by the gateway, when I
    >>>>>>>>> connect (i.e. no static IP configured on my machine).
    >>>>>>>>>
    >>>>>>>>> I did a lookup of the netbios name table on my PC which I listed
    >>>>>>>>> below (When I tried nbtstat -a 192.168.0.1 for the modem I got
    >>>>>>>>> "host not found").
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> NetBIOS Local Name Table
    >>>>>>>>>
    >>>>>>>>> Name Type Status
    >>>>>>>>> ---------------------------------------------
    >>>>>>>>> MYPC <00> UNIQUE Registered
    >>>>>>>>> WORKGROUP <00> GROUP Registered
    >>>>>>>>> MYPC <20> UNIQUE Registered
    >>>>>>>>> WORKGROUP <1E> GROUP Registered
    >>>>>>>>> WORKGROUP <1D> UNIQUE Registered
    >>>>>>>>> ..__MSBROWSE__. <01> GROUP Registered
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>>>>>> news:EBF529EE-1C6A-4D4F-BB48-82EA200A86A9@microsoft.com...
    >>>>>>>>>> It looks like your network connection may be misconfigured. From
    >>>>>>>>>> the events at timestamp 10:01 and later it appears you have two
    >>>>>>>>>> conflicting DHCP services being used. You have a DHCP server at
    >>>>>>>>>> 192.168.0.1 which I presume is the DSL Modem with routing
    >>>>>>>>>> capabilities enabled. You are also trying to get a DHCP address
    >>>>>>>>>> directly from your ISP, probably using IP 68.127.186.255 as the
    >>>>>>>>>> DHCP server address. You should use only one or the other. I'd
    >>>>>>>>>> try turning off DHCP in the modem first and see how that works
    >>>>>>>>>> out.
    >>>>>>>>>>
    >>>>>>>>>> The modem can probably be configured in several different
    >>>>>>>>>> operating modes. I have no way of knowing what your available
    >>>>>>>>>> options are or which mode has been enabled. My own has 4 distinct
    >>>>>>>>>> DSL operating modes plus various combinations of routing and
    >>>>>>>>>> firewall features. IOW, there are umpteen ways to screw up the
    >>>>>>>>>> connection. :)
    >>>>>>>>>>
    >>>>>>>>>> Typically there are two common connection modes that might be
    >>>>>>>>>> used. One way is to have the modem set in 'bridge" mode, where it
    >>>>>>>>>> only makes the hardware connection to the DSL carrier signal. You
    >>>>>>>>>> would Windows built in PPPOE "dialer" to log into your ISP from
    >>>>>>>>>> your computer. In this configuration the ISP's DHCP server would
    >>>>>>>>>> give your computer an internet IP ... i.e.. 68.127.186.115. You
    >>>>>>>>>> would need to set up your ISP username and password in the PPPOE
    >>>>>>>>>> dialer to log on. Workgroup related settings in the PC would be
    >>>>>>>>>> irrelevant in this case as long as the computer can communicate
    >>>>>>>>>> to the modem. The PPPOE dialer is a virtual device which becomes
    >>>>>>>>>> the effective internet connection. All of the required settings
    >>>>>>>>>> information would be supplied by the ISP. Alternatively, a router
    >>>>>>>>>> could be used instead to make the connections through the modem
    >>>>>>>>>> when it is in this configuration.
    >>>>>>>>>>
    >>>>>>>>>> In the second configuration your modem could be set to connect to
    >>>>>>>>>> the ISP automatically using its own internal firmware. The
    >>>>>>>>>> relevant networking settings are made in the modem using its web
    >>>>>>>>>> interface, either by you yourself or sometimes this information
    >>>>>>>>>> is pre-programmed in the modem by the ISP if they supplied the
    >>>>>>>>>> modem. You can normally access the modem's web interface using
    >>>>>>>>>> your browser (try typing 192.168.0.1 in the address bar). The
    >>>>>>>>>> modem could be set to auto-dial (AKA always-on) or "dial on
    >>>>>>>>>> demand" mode (i.e.. the modem connects whenever the PC tries to
    >>>>>>>>>> access the internet and can disconnect again after a set timeout
    >>>>>>>>>> period of no activity). In this configuration it is the modem
    >>>>>>>>>> which gets the internet IP from your ISP and then passes the
    >>>>>>>>>> internet connection to the PC through its LAN port at address
    >>>>>>>>>> 192.168.0.1 (or whatever the default is). Routing and DHCP may or
    >>>>>>>>>> may not be enabled in the modem, but if they are enabled your
    >>>>>>>>>> computer should use 192.168.0.1 as its DHCP server address and
    >>>>>>>>>> receive a LAN address from the modem, not an internet IP.
    >>>>>>>>>> Possibly 192.168.0.1 should be also entered into the computer's
    >>>>>>>>>> TCP/IP settings as the gateway address if DNS pass-through is
    >>>>>>>>>> enabled in the modem. Otherwise the ISP's DNS server addresses
    >>>>>>>>>> should be used. If DHCP is not enabled in the modem you would
    >>>>>>>>>> enter a fixed LAN address into the computer's TCP/IP
    >>>>>>>>>> configuration, in the range 192.168.0.x. The modem itself might
    >>>>>>>>>> have an optional workgroup or domain name entered into its LAN
    >>>>>>>>>> configuration settings, which is where 'JAYS' could be coming
    >>>>>>>>>> from. You can probably change or eliminate that yourself.
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>>>> news:%23ObFDy%23gIHA.5280@TK2MSFTNGP04.phx.gbl...
    >>>>>>>>>>> No its a dynamic IP Address assigned by my ISP
    >>>>>>>>>>>
    >>>>>>>>>>> I have attached all of the event log in the 3 hours around the
    >>>>>>>>>>> time of the browser conflict below. Im not sure if this
    >>>>>>>>>>> contains any other information which might give a clue as to
    >>>>>>>>>>> what is going on.
    >>>>>>>>>>>
    >>>>>>>>>>> Level Date and Time Source Event ID Task Category
    >>>>>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 12:22:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 12:17:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 12:12:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 12:11:07 PM Service Control Manager 7036
    >>>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>>> Information 3/5/2008 12:10:11 PM Service Control Manager 7036
    >>>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>>> Information 3/5/2008 12:07:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 12:02:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 12:00:46 PM EventLog 6013 None The system
    >>>>>>>>>>> uptime is 57335 seconds.
    >>>>>>>>>>> Information 3/5/2008 11:57:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 11:52:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Error 3/5/2008 11:48:19 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Information 3/5/2008 11:47:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Error 3/5/2008 11:43:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Information 3/5/2008 11:42:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Error 3/5/2008 11:37:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Information 3/5/2008 11:37:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Error 3/5/2008 11:32:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Information 3/5/2008 11:32:41 AM Microsoft-Windows-User-PnP
    >>>>>>>>>>> 20003 None Driver Management has concluded the process to add
    >>>>>>>>>>> Service tunnel for Device Instance ID ROOT*6TO4MP001 with the
    >>>>>>>>>>> following status: 0.
    >>>>>>>>>>> Information 3/5/2008 11:32:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>> Information 3/5/2008 11:28:17 AM BROWSER 8033 None The browser
    >>>>>>>>>>> has forced an election on network
    >>>>>>>>>>> DeviceNetBT_Tcpip_{6C1B0769-602C-49AD-95C1-0AD3B66DA864}
    >>>>>>>>>>> because a master browser was stopped.
    >>>>>>>>>>> Information 3/5/2008 11:24:52 AM Service Control Manager 7036
    >>>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service
    >>>>>>>>>>> entered the stopped state.
    >>>>>>>>>>> Information 3/5/2008 11:24:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 11:19:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 11:14:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 11:09:56 AM Service Control Manager 7036
    >>>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>>> Information 3/5/2008 11:09:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 11:08:55 AM Service Control Manager 7036
    >>>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>>> Information 3/5/2008 11:08:22 AM Service Control Manager 7036
    >>>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service
    >>>>>>>>>>> entered the running state.
    >>>>>>>>>>> Information 3/5/2008 11:05:06 AM volsnap 33 None The oldest
    >>>>>>>>>>> shadow copy of volume C: was deleted to keep disk space usage
    >>>>>>>>>>> for shadow copies of volume C: below the user defined limit.
    >>>>>>>>>>> Information 3/5/2008 11:04:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 10:59:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 10:54:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 10:49:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Error 3/5/2008 10:45:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Error 3/5/2008 10:45:09 AM BROWSER 8009 None The browser was
    >>>>>>>>>>> unable to promote itself to master browser. The computer that
    >>>>>>>>>>> currently believes it is the master browser is JAYS.
    >>>>>>>>>>> Information 3/5/2008 10:44:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Error 3/5/2008 10:39:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Information 3/5/2008 10:39:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Error 3/5/2008 10:34:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Information 3/5/2008 10:34:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Error 3/5/2008 10:29:38 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Information 3/5/2008 10:29:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Error 3/5/2008 10:24:28 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Information 3/5/2008 10:24:21 AM Microsoft-Windows-User-PnP
    >>>>>>>>>>> 20003 None Driver Management has concluded the process to add
    >>>>>>>>>>> Service tunnel for Device Instance ID ROOT*6TO4MP001 with the
    >>>>>>>>>>> following status: 0.
    >>>>>>>>>>> Information 3/5/2008 10:24:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>> Information 3/5/2008 10:18:41 AM Service Control Manager 7036
    >>>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service
    >>>>>>>>>>> entered the stopped state.
    >>>>>>>>>>> Error 3/5/2008 10:17:06 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Information 3/5/2008 10:16:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Error 3/5/2008 10:11:54 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Information 3/5/2008 10:11:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Information 3/5/2008 10:06:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>> Information 3/5/2008 10:05:43 AM Service Control Manager 7036
    >>>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>>> Information 3/5/2008 10:05:33 AM Service Control Manager 7036
    >>>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>>> Information 3/5/2008 10:05:26 AM Service Control Manager 7036
    >>>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>>> Information 3/5/2008 10:02:39 AM Service Control Manager 7036
    >>>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>>> Information 3/5/2008 10:02:11 AM Service Control Manager 7036
    >>>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service
    >>>>>>>>>>> entered the running state.
    >>>>>>>>>>> Information 3/5/2008 10:01:36 AM Microsoft-Windows-User-PnP
    >>>>>>>>>>> 20003 None Driver Management has concluded the process to add
    >>>>>>>>>>> Service tunnel for Device Instance ID ROOT*6TO4MP001 with the
    >>>>>>>>>>> following status: 0.
    >>>>>>>>>>> Error 3/5/2008 10:01:30 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>>> Information 3/5/2008 10:01:17 AM Microsoft-Windows-User-PnP
    >>>>>>>>>>> 20003 None Driver Management has concluded the process to add
    >>>>>>>>>>> Service tunnel for Device Instance ID ROOT*ISATAP002 with the
    >>>>>>>>>>> following status: 0.
    >>>>>>>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002
    >>>>>>>>>>> None The IP address lease 192.168.1.64 for the Network Card with
    >>>>>>>>>>> network address 0016D3A2E7AD has been denied by the DHCP server
    >>>>>>>>>>> 192.168.0.1 (The DHCP Server sent a DHCPNACK message).
    >>>>>>>>>>> Warning 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1003
    >>>>>>>>>>> None "The description for Event ID 1003 from source
    >>>>>>>>>>> Microsoft-Windows-Dhcp-Client cannot be found. Either the
    >>>>>>>>>>> component that raises this event is not installed on your local
    >>>>>>>>>>> computer or the installation is corrupted. You can install or
    >>>>>>>>>>> repair the component on the local computer.
    >>>>>>>>>>>
    >>>>>>>>>>> If the event originated on another computer, the display
    >>>>>>>>>>> information had to be saved with the event.
    >>>>>>>>>>>
    >>>>>>>>>>> The following information was included with the event:
    >>>>>>>>>>>
    >>>>>>>>>>> 0016D3A2E7AD
    >>>>>>>>>>> %%2163146757
    >>>>>>>>>>>
    >>>>>>>>>>> The description string for parameter reference (%1) could not be
    >>>>>>>>>>> found
    >>>>>>>>>>> "
    >>>>>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>> Information 3/5/2008 9:57:44 AM Service Control Manager 7036
    >>>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>>> Information 3/5/2008 9:57:37 AM Service Control Manager 7036
    >>>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>>> Information 3/5/2008 9:52:42 AM Service Control Manager 7036
    >>>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>>> Information 3/5/2008 9:52:35 AM Service Control Manager 7036
    >>>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>>> Information 3/5/2008 9:38:26 AM Service Control Manager 7036
    >>>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service
    >>>>>>>>>>> entered the stopped state.
    >>>>>>>>>>> Information 3/5/2008 9:37:56 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the
    >>>>>>>>>>> following status: 0.
    >>>>>>>>>>> Information 3/5/2008 9:37:48 AM Service Control Manager 7036
    >>>>>>>>>>> None The Windows Image Acquisition (WIA) service entered the
    >>>>>>>>>>> running state.
    >>>>>>>>>>> Information 3/5/2008 9:37:39 AM
    >>>>>>>>>>> Microsoft-Windows-Power-Troubleshooter 1 None "The system has
    >>>>>>>>>>> resumed from sleep.
    >>>>>>>>>>>
    >>>>>>>>>>> Sleep Time: 3/5/2008 7:12:57 AM
    >>>>>>>>>>> Wake Time: 3/5/2008 5:37:34 PM
    >>>>>>>>>>>
    >>>>>>>>>>> Wake Source: Unknown"
    >>>>>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system
    >>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system
    >>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>> "Bob F." <bob@NOSPAN.com> wrote in message
    >>>>>>>>>>> news:52055B79-F315-4C46-986D-CB8AFBFF2D37@microsoft.com...
    >>>>>>>>>>>> Where did you get the setup information for your internet
    >>>>>>>>>>>> connection? Did you use a static IP? Maybe it's incorrect and
    >>>>>>>>>>>> you are encroaching onto someone else's IP space.
    >>>>>>>>>>>>
    >>>>>>>>>>>> --
    >>>>>>>>>>>> BobF.
    >>>>>>>>>>>> "Dave" <dave@beepbeep.com> wrote in message
    >>>>>>>>>>>> news:eBrCR47gIHA.4436@TK2MSFTNGP02.phx.gbl...
    >>>>>>>>>>>>> What shows up in Start - Network?
    >>>>>>>>>>>>>
    >>>>>>>>>>>>>
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>>>>>>> news:#orAgk7gIHA.2448@TK2MSFTNGP03.phx.gbl...
    >>>>>>>>>>>>>> My (lone) machine is connected directly to the DSL router
    >>>>>>>>>>>>>> with no wireless capabilities on the router. Despite this I
    >>>>>>>>>>>>>> get the following message in the event log:
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> The browser was unable to promote itself to master browser.
    >>>>>>>>>>>>>> The computer that currently believes it is the master browser
    >>>>>>>>>>>>>> is JAYS.
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> Once again, my computer is not called JAYS. Friends and
    >>>>>>>>>>>>>> family are not Vista Security experts. Looking for capable /
    >>>>>>>>>>>>>> expert advice from this forum.
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> What are the possible explanations for this???
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> "Malke" <malke@invalid.invalid> wrote in message
    >>>>>>>>>>>>>> news:O5eVD62gIHA.4692@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>>>>>>>> Nubie wrote:
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>> What should I be looking for in the Settings?
    >>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>> ALSO: How would the config of my DSL modem confuse my vista
    >>>>>>>>>>>>>>>> machine to
    >>>>>>>>>>>>>>>> think that there is another computer called JAYS on my
    >>>>>>>>>>>>>>>> local network.
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>> Nubie;642434 Wrote:
    >>>>>>>>>>>>>>>>>> Hi
    >>>>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>>> I have a single (lone) windows Vista machine connected
    >>>>>>>>>>>>>>>>>> directly to the
    >>>>>>>>>>>>>>>>>> internet via a dsl modem. I just viewed the following in
    >>>>>>>>>>>>>>>>>> my eventlogs:
    >>>>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>>> "The browser was unable to promote itself to master
    >>>>>>>>>>>>>>>>>> browser. The
    >>>>>>>>>>>>>>>>>> computer
    >>>>>>>>>>>>>>>>>> that
    >>>>>>>>>>>>>>>>>> currently believes it is the master browser is JAYS. My
    >>>>>>>>>>>>>>>>>> machine is NOT
    >>>>>>>>>>>>>>>>>> called JAYS."
    >>>>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>>> What is happening here!!?? If my machine is connected to
    >>>>>>>>>>>>>>>>>> a DSL modem
    >>>>>>>>>>>>>>>>>> with
    >>>>>>>>>>>>>>>>>> no additional
    >>>>>>>>>>>>>>>>>> machines connected to that modem why is this message
    >>>>>>>>>>>>>>>>>> appearing ????
    >>>>>>>>>>>>>>>>>> What is
    >>>>>>>>>>>>>>>>>> happening here ??
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> It certainly seems as though someone else is on your
    >>>>>>>>>>>>>>> network. Is this a
    >>>>>>>>>>>>>>> combination modem/wireless router? If yes, you probably
    >>>>>>>>>>>>>>> haven't secured
    >>>>>>>>>>>>>>> your wireless properly and a stranger is using your
    >>>>>>>>>>>>>>> bandwidth. If you only
    >>>>>>>>>>>>>>> have a single computer connected directly to a DSL modem by
    >>>>>>>>>>>>>>> ethernet cable
    >>>>>>>>>>>>>>> (no wireless router), then call your ISP. Because you don't
    >>>>>>>>>>>>>>> really know
    >>>>>>>>>>>>>>> what you're looking at - and I mean no disrespect to you,
    >>>>>>>>>>>>>>> I'm just being
    >>>>>>>>>>>>>>> practical - it might be smart for you to have a computer
    >>>>>>>>>>>>>>> professional come
    >>>>>>>>>>>>>>> on-site and take a look. This will not be someone from a
    >>>>>>>>>>>>>>> BigComputerStore/GeekSquad type of place. Get
    >>>>>>>>>>>>>>> recommendations from friends,
    >>>>>>>>>>>>>>> family, colleagues.
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> Malke
    >>>>>>>>>>>>>>> --
    >>>>>>>>>>>>>>> MS-MVP
    >>>>>>>>>>>>>>> Elephant Boy Computers
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> Don't Panic!
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>><!--colorc--><!--/colorc-->
    >><!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     
    Bob F., Mar 15, 2008
    #29
  11. RalfG

    RalfG Guest

    Replying inline.

    "Nubie" <newsgoup_contact@atigen.com> wrote in message
    news:eFDACeuhIHA.4140@TK2MSFTNGP04.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > The modem is set up for DNS forwarding, and the DNS IP's are configured on
    > the modem. With regards to the NetBios over TCP/IP, I just disabled this
    > (thanks for the advice).<!--colorc--><!--/colorc-->
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > What is confusing me here is your comments regarding the DHCP server on
    > the modem. Presumably, any internet IP address the modem gives me has to
    > have come from the ISP. The ISP assigned the internet IP to the modem,
    > the modem assigns this to me. (Even if I unplugged my machine from the
    > modem for 30 mins).<!--colorc--><!--/colorc-->

    I've been having second thoughts about this configuration issue. I tried to
    imitate your settings on the PC but couldn't manually change the gateway in
    Vista when automatic configuration is enabled. It threw into doubt my
    premise that your DSL configuration should be basically similar to mine
    despite the different hardware. There are other ways it could be done, with
    or without routing. I think at this point it would fruitless to go on
    without knowing the details of your ISP's connection specs, the make and
    model of your modem and possibly its firmware revision (standard retail
    version or custom firmware for the ISP).
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > How would the above cause the confusion wrt another machine ('JAYS')
    > appearing to be on my network
    > Somehow a NetBIOS message was broadcast, to this other machine on what the
    > modem/router believed to be my network. How could this have happened?<!--colorc--><!--/colorc-->

    I'm only speculating. Your system was set with Netbios enabled on the
    internet connection, making it accessible from the internet if anyone knew
    to find it, or by accident. The speculation is that every so often DHCP
    reconfigures the ethernet connection with a LAN address (we saw that in the
    logs you posted) while there happened to be a live connection to someone
    else who also has Netbios exposed to the internet. The two computers try to
    connect to each other on the accidentally "spoofed" Lan connection. Unless
    the connection to JAYS keeps reappearing from time to time I'm leaning
    towards considering it a fluke occurrence.


    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    > "RalfG" <itsnotme@ladeda.deda> wrote in message
    > news:C7150467-0DF3-49C9-BFFD-3D3B960F5041@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> Looks like a bit of a dog's breakfast. :)
    >> Questionable entries marked with -******************
    >>
    >> You said earlier that the computer was getting a dynamic IP from your ISP
    >> but the way it is configured below I can't see that happening reliably.
    >> You've got two conflicting DHCP services active.
    >> The default Gateway is set to an internet IP but the DHCP server listed
    >> is the modem/router, which presumable can only supply LAN addresses
    >> within its own network subnet (192.168.0.x). Your ISP will have it's own
    >> dedicated DHCP servers which are on internet IPs. That is where the
    >> 68.127.175.71 address came from. Aside from that the modem's internal
    >> DHCP server wouldn't know which internet IPs were available and which
    >> ones were already being assigned to someone else. This could be where
    >> your mystery connection is being created. Also the subnet mask for your
    >> internet IP is set for the 192.168.0.x subnet rather than for internet
    >> which is not okay.
    >>
    >> Your DNS server is set to a local LAN address (192.168.0.1) rather than
    >> the ISP's DNS servers, which is probably okay if the modem/router has the
    >> real DNS server addresses and DNS forwarding is enabled. Otherwise these
    >> lines should be showing two different IPs from your ISP. NetBios is
    >> enabled on your ethernet TCP/IP adapter but without NAT or firewall
    >> protection in the modem/router this is not a good idea over an open
    >> internet connection.
    >>
    >> It looks like the modem/router's actual LAN IP is 192.168.0.1. That's the
    >> address you should browse to in IE to access the modem's configuration
    >> pages. How you need to configure the computer's network settings depends
    >> on how the modem has been configured but I think at the very least you
    >> should be disabling the modem's onboard DHCP server if your computer's
    >> adapter is intended to get an address automatically from your ISP.
    >> Setting the router's DNS to pass-through mode rather than forwarding
    >> isn't absolutely necessary but it eliminates the extra rerouting step. In
    >> the various DNS Suffix lines I'd expect to see entries referencing your
    >> ISP's domain name. I suspect the tunnel adapters listed below are just
    >> redundant.
    >>
    >>
    >> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >> news:O3ZdjXihIHA.200@TK2MSFTNGP02.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>
    >>> Windows IP Configuration
    >>>
    >>> Host Name . . . . . . . . . . . . : mypc
    >>> Primary Dns Suffix . . . . . . . :
    >>> Node Type . . . . . . . . . . . . : Hybrid
    >>> IP Routing Enabled. . . . . . . . : No
    >>> WINS Proxy Enabled. . . . . . . . : No
    >>> DNS Suffix Search List. . . . . . :
    >>> domain_not_set.invalid--*******************
    >>>
    >>> Ethernet adapter Local Area Connection:
    >>>
    >>> Connection-specific DNS Suffix . :
    >>> domain_not_set.invalid---************************
    >>> Description . . . . . . . . . . . : NVIDIA nForce Networking
    >>> Controller
    >>> Physical Address. . . . . . . . . : 00-16-D3-A2-E7-AD
    >>> DHCP Enabled. . . . . . . . . . . : Yes
    >>> Autoconfiguration Enabled . . . . : Yes
    >>> Link-local IPv6 Address . . . . . :
    >>> ff80::80f6:625f:f376:8301%6(Preferred)
    >>> IPv4 Address. . . . . . . . . . . : 68.127.175.71(Preferred)
    >>> Subnet Mask . . . . . . . . . . . :
    >>> 255.255.255.0 --*********************
    >>> Lease Obtained. . . . . . . . . . : Friday, March 14, 2008 12:05:54 PM
    >>> Lease Expires . . . . . . . . . . : Friday, March 14, 2008 3:41:18 PM
    >>> Default Gateway . . . . . . . . . : 68.127.175.72
    >>> DHCP Server . . . . . . . . . . . : 192.168.0.1--*********************
    >>> DHCPv6 IAID . . . . . . . . . . . : 203332435
    >>> DNS Servers . . . . . . . . . . . : 192.168.0.1--*********************
    >>> 192.168.0.1--*********************
    >>> NetBIOS over Tcpip. . . . . . . . : Enabled
    >>>
    >>> Tunnel adapter Local Area Connection* 6:
    >>>
    >>> Connection-specific DNS Suffix . : domain_not_set.invalid
    >>> Description . . . . . . . . . . . : isatap.domain_not_set.invalid
    >>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>> DHCP Enabled. . . . . . . . . . . : No
    >>> Autoconfiguration Enabled . . . . : Yes
    >>> Link-local IPv6 Address . . . . . :
    >>> ff80::200:5fff:68.128.185.71%14(Preferred
    >>> )
    >>> Default Gateway . . . . . . . . . :
    >>> DNS Servers . . . . . . . . . . . : 192.168.0.1--******************
    >>> 192.168.0.1--********************
    >>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>
    >>> Tunnel adapter Local Area Connection* 7:
    >>>
    >>> Connection-specific DNS Suffix . :
    >>> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    >>> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    >>> DHCP Enabled. . . . . . . . . . . : No
    >>> Autoconfiguration Enabled . . . . : Yes
    >>> IPv6 Address. . . . . . . . . . . :
    >>> 2001:0:4337:9f66:18f9:3343:ff80:50f8(Pref
    >>> erred)
    >>> Link-local IPv6 Address . . . . . :
    >>> ff80::38f9:3343:ff80:50f8%12(Preferred)
    >>> Default Gateway . . . . . . . . . :
    >>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>
    >>> Tunnel adapter Local Area Connection* 14:
    >>>
    >>> Media State . . . . . . . . . . . : Media disconnected
    >>> Connection-specific DNS Suffix . :
    >>> Description . . . . . . . . . . . : 6TO4 Adapter
    >>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>> DHCP Enabled. . . . . . . . . . . : No
    >>> Autoconfiguration Enabled . . . . : Yes
    >>>
    >>> Tunnel adapter Local Area Connection* 10:
    >>>
    >>> Connection-specific DNS Suffix . : domain_not_set.invalid
    >>> Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
    >>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>> DHCP Enabled. . . . . . . . . . . : No
    >>> Autoconfiguration Enabled . . . . : Yes
    >>> Temporary IPv6 Address. . . . . . :
    >>> 2002:227f:ff27::227f:ff27(Preferred)
    >>> Default Gateway . . . . . . . . . : 2002:f058:6301::f058:6301
    >>> DNS Servers . . . . . . . . . . . : 192.168.0.1---*******************
    >>>
    >>> 192.168.0.1--*************************
    >>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>
    >>>
    >>>
    >>>
    >>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>> news:C5E12624-0EEF-4A6D-84C9-AF9BB6440665@microsoft.com...
    >>>> Open a command prompt and enter "ipconfig /all", without the quotes.
    >>>> What do you get?
    >>>>
    >>>> Other points in-line below.
    >>>>
    >>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>> news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...
    >>>>> 0016D3A2E7AD is my machines regular (wire) network card. The wireless
    >>>>> card is disabled in device manager (which presumably rules any wireles
    >>>>> connection out). 68.127.186.255 is AT&T's network, which is my ISP
    >>>>> (ARIN lookup below):
    >>>>>
    >>>>> AT&T Internet Services SBCIS-SIS80 (NET-68-120-0-0-1)
    >>>>> 68.120.0.0 - 68.127.255.255
    >>>>> bras4.pltnca SBC068127176000040211 (NET-68-127-176-0-1)
    >>>>> 68.127.176.0 - 68.127.191.255
    >>>>>
    >>>>> The constantly repeating reconnection notices at 5 minute intervals,
    >>>>> (with resulting successfully assigned IP addresses), is probably a
    >>>>> result of the fact that I remove the ethernet cable from my network
    >>>>> card whenever I step away from my machine.
    >>>>
    >>>> You really shouldn't do that. Only USB is generally safe to hot-plug.
    >>>> Sooner or later you're luck will run out and one or the other ethernet
    >>>> devices will fry. That aside, unplugging it doesn't account for those
    >>>> repeating reconnections. The timing is too consistent, down to the
    >>>> second.
    >>>>
    >>>>>
    >>>>> The only other remotely possible connection to my PC would have been
    >>>>> bluetooth, however the wireless card which provides bluetooth
    >>>>> connectivity is always turned off (at the switch).
    >>>>>
    >>>>> This leaves 2 questions
    >>>>>
    >>>>> 1) How could there be a master browser called JAYS showing up on my
    >>>>> logs (given the above).
    >>>>
    >>>> You would both have to be peers connected on the same LAN or directly
    >>>> to each other (same thing). Any PC on a LAN can be a master browser. I
    >>>> have one XP PC on mine that always insists on taking that status when
    >>>> it joins the LAN.
    >>>>
    >>>>> and (less importantly)
    >>>>>
    >>>>> 2) Why is my machine having a conversation with the outside world (my
    >>>>> ISP) about its workgroup. My understanding was that a workgroup would
    >>>>> be something that would be limited to my LAN alone.
    >>>>
    >>>> Let's see what ipconfig shows.
    >>>>
    >>>>>
    >>>>>
    >>>>>
    >>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>> news:6AD5B7D8-0DFF-4421-8DF9-3FF57637594C@microsoft.com...
    >>>>>> The anomalous name being in the router was only a suggestion, it's an
    >>>>>> option in mine that could also be in yours. As far as not finding the
    >>>>>> LAN DHCP server in the netbios table, this ....
    >>>>>>
    >>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None
    >>>>>> The IP
    >>>>>>>>> address lease 192.168.1.64 for the Network Card with network
    >>>>>>>>> address 0016D3A2E7AD has been denied by the DHCP server
    >>>>>>>>> 192.168.0.1 (The DHCP Server sent a DHCPNACK message).
    >>>>>>
    >>>>>> says that it exists, at least some of the time, and that your
    >>>>>> computer tried to use it with an incorrect network address and got
    >>>>>> booted. This on the other hand....
    >>>>>>
    >>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>> :1d""
    >>>>>>>>> could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>
    >>>>>> says your computer subsequently tried to connect to a server on the
    >>>>>> internet, probably your ISP, possibly somewhere else. There's no
    >>>>>> indication here whether it is the same network adapter making the
    >>>>>> connection as the one above but we can see from the text that your
    >>>>>> network adapter in this case also "somehow" had some incorrect
    >>>>>> information set in its configuration at the time.
    >>>>>>
    >>>>>> OTOH these constantly repeating reconnection notices at 5 minute
    >>>>>> intervals....
    >>>>>>
    >>>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>
    >>>>>> Are very much like what you can see happening with wireless
    >>>>>> connections. If I were going to make a guess as to what is going on
    >>>>>> here I'd say that apart from the ethernet adapter you connect to your
    >>>>>> own modem with you do have a wireless adapter in that computer, it is
    >>>>>> always turned on and it is set to automatically connect to any
    >>>>>> available network. Every so often your PC is piggybacking a ride, or
    >>>>>> trying to, on poor JAYS wireless network. :)
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>> news:OUZ0QCKhIHA.4740@TK2MSFTNGP05.phx.gbl...
    >>>>>>>
    >>>>>>> If JAYS were the name of the modem or in its netbios table, then it
    >>>>>>> should still be there presumably. (I have not reconfigured the
    >>>>>>> modem in several months, and at that I time I set it to factory
    >>>>>>> defaults - so the name JAYS should not be assigned to the modem).
    >>>>>>>
    >>>>>>> I checked the mode that the modem is operating. This is as follows:
    >>>>>>>
    >>>>>>> PPP is on the modem. (PPP session is initiated from the modem.) -
    >>>>>>> i.e. Not operating in Bridging mode
    >>>>>>>
    >>>>>>> I believe my DHCP server is assigned by the gateway, when I connect
    >>>>>>> (i.e. no static IP configured on my machine).
    >>>>>>>
    >>>>>>> I did a lookup of the netbios name table on my PC which I listed
    >>>>>>> below (When I tried nbtstat -a 192.168.0.1 for the modem I got "host
    >>>>>>> not found").
    >>>>>>>
    >>>>>>>
    >>>>>>> NetBIOS Local Name Table
    >>>>>>>
    >>>>>>> Name Type Status
    >>>>>>> ---------------------------------------------
    >>>>>>> MYPC <00> UNIQUE Registered
    >>>>>>> WORKGROUP <00> GROUP Registered
    >>>>>>> MYPC <20> UNIQUE Registered
    >>>>>>> WORKGROUP <1E> GROUP Registered
    >>>>>>> WORKGROUP <1D> UNIQUE Registered
    >>>>>>> ..__MSBROWSE__. <01> GROUP Registered
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>>>> news:EBF529EE-1C6A-4D4F-BB48-82EA200A86A9@microsoft.com...
    >>>>>>>> It looks like your network connection may be misconfigured. From
    >>>>>>>> the events at timestamp 10:01 and later it appears you have two
    >>>>>>>> conflicting DHCP services being used. You have a DHCP server at
    >>>>>>>> 192.168.0.1 which I presume is the DSL Modem with routing
    >>>>>>>> capabilities enabled. You are also trying to get a DHCP address
    >>>>>>>> directly from your ISP, probably using IP 68.127.186.255 as the
    >>>>>>>> DHCP server address. You should use only one or the other. I'd try
    >>>>>>>> turning off DHCP in the modem first and see how that works out.
    >>>>>>>>
    >>>>>>>> The modem can probably be configured in several different
    >>>>>>>> operating modes. I have no way of knowing what your available
    >>>>>>>> options are or which mode has been enabled. My own has 4 distinct
    >>>>>>>> DSL operating modes plus various combinations of routing and
    >>>>>>>> firewall features. IOW, there are umpteen ways to screw up the
    >>>>>>>> connection. :)
    >>>>>>>>
    >>>>>>>> Typically there are two common connection modes that might be used.
    >>>>>>>> One way is to have the modem set in 'bridge" mode, where it only
    >>>>>>>> makes the hardware connection to the DSL carrier signal. You would
    >>>>>>>> Windows built in PPPOE "dialer" to log into your ISP from your
    >>>>>>>> computer. In this configuration the ISP's DHCP server would give
    >>>>>>>> your computer an internet IP ... i.e.. 68.127.186.115. You would
    >>>>>>>> need to set up your ISP username and password in the PPPOE dialer
    >>>>>>>> to log on. Workgroup related settings in the PC would be irrelevant
    >>>>>>>> in this case as long as the computer can communicate to the modem.
    >>>>>>>> The PPPOE dialer is a virtual device which becomes the effective
    >>>>>>>> internet connection. All of the required settings information would
    >>>>>>>> be supplied by the ISP. Alternatively, a router could be used
    >>>>>>>> instead to make the connections through the modem when it is in
    >>>>>>>> this configuration.
    >>>>>>>>
    >>>>>>>> In the second configuration your modem could be set to connect to
    >>>>>>>> the ISP automatically using its own internal firmware. The relevant
    >>>>>>>> networking settings are made in the modem using its web interface,
    >>>>>>>> either by you yourself or sometimes this information is
    >>>>>>>> pre-programmed in the modem by the ISP if they supplied the modem.
    >>>>>>>> You can normally access the modem's web interface using your
    >>>>>>>> browser (try typing 192.168.0.1 in the address bar). The modem
    >>>>>>>> could be set to auto-dial (AKA always-on) or "dial on demand" mode
    >>>>>>>> (i.e.. the modem connects whenever the PC tries to access the
    >>>>>>>> internet and can disconnect again after a set timeout period of no
    >>>>>>>> activity). In this configuration it is the modem which gets the
    >>>>>>>> internet IP from your ISP and then passes the internet connection
    >>>>>>>> to the PC through its LAN port at address 192.168.0.1 (or whatever
    >>>>>>>> the default is). Routing and DHCP may or may not be enabled in the
    >>>>>>>> modem, but if they are enabled your computer should use 192.168.0.1
    >>>>>>>> as its DHCP server address and receive a LAN address from the
    >>>>>>>> modem, not an internet IP. Possibly 192.168.0.1 should be also
    >>>>>>>> entered into the computer's TCP/IP settings as the gateway address
    >>>>>>>> if DNS pass-through is enabled in the modem. Otherwise the ISP's
    >>>>>>>> DNS server addresses should be used. If DHCP is not enabled in the
    >>>>>>>> modem you would enter a fixed LAN address into the computer's
    >>>>>>>> TCP/IP configuration, in the range 192.168.0.x. The modem itself
    >>>>>>>> might have an optional workgroup or domain name entered into its
    >>>>>>>> LAN configuration settings, which is where 'JAYS' could be coming
    >>>>>>>> from. You can probably change or eliminate that yourself.
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>> news:%23ObFDy%23gIHA.5280@TK2MSFTNGP04.phx.gbl...
    >>>>>>>>> No its a dynamic IP Address assigned by my ISP
    >>>>>>>>>
    >>>>>>>>> I have attached all of the event log in the 3 hours around the
    >>>>>>>>> time of the browser conflict below. Im not sure if this contains
    >>>>>>>>> any other information which might give a clue as to what is going
    >>>>>>>>> on.
    >>>>>>>>>
    >>>>>>>>> Level Date and Time Source Event ID Task Category
    >>>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:22:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:17:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:12:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:11:07 PM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>> Information 3/5/2008 12:10:11 PM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>> Information 3/5/2008 12:07:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:02:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 12:00:46 PM EventLog 6013 None The system
    >>>>>>>>> uptime is 57335 seconds.
    >>>>>>>>> Information 3/5/2008 11:57:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 11:52:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 11:48:19 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 11:47:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 11:43:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 11:42:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 11:37:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 11:37:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 11:32:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 11:32:41 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>>>> status: 0.
    >>>>>>>>> Information 3/5/2008 11:32:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 11:28:17 AM BROWSER 8033 None The browser has
    >>>>>>>>> forced an election on network
    >>>>>>>>> DeviceNetBT_Tcpip_{6C1B0769-602C-49AD-95C1-0AD3B66DA864} because
    >>>>>>>>> a master browser was stopped.
    >>>>>>>>> Information 3/5/2008 11:24:52 AM Service Control Manager 7036 None
    >>>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>>> stopped state.
    >>>>>>>>> Information 3/5/2008 11:24:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 11:19:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 11:14:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 11:09:56 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>> Information 3/5/2008 11:09:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 11:08:55 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>> Information 3/5/2008 11:08:22 AM Service Control Manager 7036 None
    >>>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>>> running state.
    >>>>>>>>> Information 3/5/2008 11:05:06 AM volsnap 33 None The oldest shadow
    >>>>>>>>> copy of volume C: was deleted to keep disk space usage for shadow
    >>>>>>>>> copies of volume C: below the user defined limit.
    >>>>>>>>> Information 3/5/2008 11:04:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 10:59:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 10:54:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 10:49:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:45:09 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Error 3/5/2008 10:45:09 AM BROWSER 8009 None The browser was
    >>>>>>>>> unable to promote itself to master browser. The computer that
    >>>>>>>>> currently believes it is the master browser is JAYS.
    >>>>>>>>> Information 3/5/2008 10:44:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:39:59 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:39:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:34:49 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:34:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:29:38 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:29:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:24:28 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:24:21 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>>>> status: 0.
    >>>>>>>>> Information 3/5/2008 10:24:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 10:18:41 AM Service Control Manager 7036 None
    >>>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>>> stopped state.
    >>>>>>>>> Error 3/5/2008 10:17:06 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:16:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:11:54 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:11:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:06:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>> 1103 None Your computer was successfully assigned an address from
    >>>>>>>>> the network, and it can now connect to other computers.
    >>>>>>>>> Information 3/5/2008 10:05:43 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>> Information 3/5/2008 10:05:33 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>> Information 3/5/2008 10:05:26 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>> Information 3/5/2008 10:02:39 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>> Information 3/5/2008 10:02:11 AM Service Control Manager 7036 None
    >>>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>>> running state.
    >>>>>>>>> Information 3/5/2008 10:01:36 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>> tunnel for Device Instance ID ROOT*6TO4MP001 with the following
    >>>>>>>>> status: 0.
    >>>>>>>>> Error 3/5/2008 10:01:30 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d"" could not be registered on the interface with IP address
    >>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>> Information 3/5/2008 10:01:17 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the following
    >>>>>>>>> status: 0.
    >>>>>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None
    >>>>>>>>> The IP address lease 192.168.1.64 for the Network Card with
    >>>>>>>>> network address 0016D3A2E7AD has been denied by the DHCP server
    >>>>>>>>> 192.168.0.1 (The DHCP Server sent a DHCPNACK message).
    >>>>>>>>> Warning 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1003
    >>>>>>>>> None "The description for Event ID 1003 from source
    >>>>>>>>> Microsoft-Windows-Dhcp-Client cannot be found. Either the
    >>>>>>>>> component that raises this event is not installed on your local
    >>>>>>>>> computer or the installation is corrupted. You can install or
    >>>>>>>>> repair the component on the local computer.
    >>>>>>>>>
    >>>>>>>>> If the event originated on another computer, the display
    >>>>>>>>> information had to be saved with the event.
    >>>>>>>>>
    >>>>>>>>> The following information was included with the event:
    >>>>>>>>>
    >>>>>>>>> 0016D3A2E7AD
    >>>>>>>>> %%2163146757
    >>>>>>>>>
    >>>>>>>>> The description string for parameter reference (%1) could not be
    >>>>>>>>> found
    >>>>>>>>> "
    >>>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 9:57:44 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>> Information 3/5/2008 9:57:37 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>> Information 3/5/2008 9:52:42 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the stopped state.
    >>>>>>>>> Information 3/5/2008 9:52:35 AM Service Control Manager 7036 None
    >>>>>>>>> The LiveUpdate service entered the running state.
    >>>>>>>>> Information 3/5/2008 9:38:26 AM Service Control Manager 7036 None
    >>>>>>>>> The WinHTTP Web Proxy Auto-Discovery Service service entered the
    >>>>>>>>> stopped state.
    >>>>>>>>> Information 3/5/2008 9:37:56 AM Microsoft-Windows-User-PnP 20003
    >>>>>>>>> None Driver Management has concluded the process to add Service
    >>>>>>>>> tunnel for Device Instance ID ROOT*ISATAP002 with the following
    >>>>>>>>> status: 0.
    >>>>>>>>> Information 3/5/2008 9:37:48 AM Service Control Manager 7036 None
    >>>>>>>>> The Windows Image Acquisition (WIA) service entered the running
    >>>>>>>>> state.
    >>>>>>>>> Information 3/5/2008 9:37:39 AM
    >>>>>>>>> Microsoft-Windows-Power-Troubleshooter 1 None "The system has
    >>>>>>>>> resumed from sleep.
    >>>>>>>>>
    >>>>>>>>> Sleep Time: 3/5/2008 7:12:57 AM
    >>>>>>>>> Wake Time: 3/5/2008 5:37:34 PM
    >>>>>>>>>
    >>>>>>>>> Wake Source: Unknown"
    >>>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system
    >>>>>>>>> detected that network adapter Local Area Connection was connected
    >>>>>>>>> to the network, and has initiated normal operation.
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> "Bob F." <bob@NOSPAN.com> wrote in message
    >>>>>>>>> news:52055B79-F315-4C46-986D-CB8AFBFF2D37@microsoft.com...
    >>>>>>>>>> Where did you get the setup information for your internet
    >>>>>>>>>> connection? Did you use a static IP? Maybe it's incorrect and
    >>>>>>>>>> you are encroaching onto someone else's IP space.
    >>>>>>>>>>
    >>>>>>>>>> --
    >>>>>>>>>> BobF.
    >>>>>>>>>> "Dave" <dave@beepbeep.com> wrote in message
    >>>>>>>>>> news:eBrCR47gIHA.4436@TK2MSFTNGP02.phx.gbl...
    >>>>>>>>>>> What shows up in Start - Network?
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>>>>> news:#orAgk7gIHA.2448@TK2MSFTNGP03.phx.gbl...
    >>>>>>>>>>>> My (lone) machine is connected directly to the DSL router with
    >>>>>>>>>>>> no wireless capabilities on the router. Despite this I get the
    >>>>>>>>>>>> following message in the event log:
    >>>>>>>>>>>>
    >>>>>>>>>>>> The browser was unable to promote itself to master browser.
    >>>>>>>>>>>> The computer that currently believes it is the master browser
    >>>>>>>>>>>> is JAYS.
    >>>>>>>>>>>>
    >>>>>>>>>>>> Once again, my computer is not called JAYS. Friends and family
    >>>>>>>>>>>> are not Vista Security experts. Looking for capable / expert
    >>>>>>>>>>>> advice from this forum.
    >>>>>>>>>>>>
    >>>>>>>>>>>> What are the possible explanations for this???
    >>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>> "Malke" <malke@invalid.invalid> wrote in message
    >>>>>>>>>>>> news:O5eVD62gIHA.4692@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>>>>>> Nubie wrote:
    >>>>>>>>>>>>>
    >>>>>>>>>>>>>> What should I be looking for in the Settings?
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> ALSO: How would the config of my DSL modem confuse my vista
    >>>>>>>>>>>>>> machine to
    >>>>>>>>>>>>>> think that there is another computer called JAYS on my local
    >>>>>>>>>>>>>> network.
    >>>>>>>>>>>>>
    >>>>>>>>>>>>>>> Nubie;642434 Wrote:
    >>>>>>>>>>>>>>>> Hi
    >>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>> I have a single (lone) windows Vista machine connected
    >>>>>>>>>>>>>>>> directly to the
    >>>>>>>>>>>>>>>> internet via a dsl modem. I just viewed the following in my
    >>>>>>>>>>>>>>>> eventlogs:
    >>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>> "The browser was unable to promote itself to master
    >>>>>>>>>>>>>>>> browser. The
    >>>>>>>>>>>>>>>> computer
    >>>>>>>>>>>>>>>> that
    >>>>>>>>>>>>>>>> currently believes it is the master browser is JAYS. My
    >>>>>>>>>>>>>>>> machine is NOT
    >>>>>>>>>>>>>>>> called JAYS."
    >>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>> What is happening here!!?? If my machine is connected to a
    >>>>>>>>>>>>>>>> DSL modem
    >>>>>>>>>>>>>>>> with
    >>>>>>>>>>>>>>>> no additional
    >>>>>>>>>>>>>>>> machines connected to that modem why is this message
    >>>>>>>>>>>>>>>> appearing ????
    >>>>>>>>>>>>>>>> What is
    >>>>>>>>>>>>>>>> happening here ??
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> It certainly seems as though someone else is on your network.
    >>>>>>>>>>>>> Is this a
    >>>>>>>>>>>>> combination modem/wireless router? If yes, you probably
    >>>>>>>>>>>>> haven't secured
    >>>>>>>>>>>>> your wireless properly and a stranger is using your bandwidth.
    >>>>>>>>>>>>> If you only
    >>>>>>>>>>>>> have a single computer connected directly to a DSL modem by
    >>>>>>>>>>>>> ethernet cable
    >>>>>>>>>>>>> (no wireless router), then call your ISP. Because you don't
    >>>>>>>>>>>>> really know
    >>>>>>>>>>>>> what you're looking at - and I mean no disrespect to you, I'm
    >>>>>>>>>>>>> just being
    >>>>>>>>>>>>> practical - it might be smart for you to have a computer
    >>>>>>>>>>>>> professional come
    >>>>>>>>>>>>> on-site and take a look. This will not be someone from a
    >>>>>>>>>>>>> BigComputerStore/GeekSquad type of place. Get recommendations
    >>>>>>>>>>>>> from friends,
    >>>>>>>>>>>>> family, colleagues.
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> Malke
    >>>>>>>>>>>>> --
    >>>>>>>>>>>>> MS-MVP
    >>>>>>>>>>>>> Elephant Boy Computers
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> Don't Panic!
    >>>>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>><!--colorc--><!--/colorc-->
    >><!--colorc--><!--/colorc-->
    ><!--colorc--><!--/colorc-->
     
    RalfG, Mar 16, 2008
    #30
  12. RalfG

    RalfG Guest

    Not the OP here, I don't have access to his ISP information. You want Nubie.

    "Bob F." <bob@NOSPAN.com> wrote in message
    news:C5E591AE-C0B0-49BB-AFD1-A28BEC95686C@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Well, I am afraid to say, you can't just do that. Network provider have
    > and architecture that they follow that dictate how you should set up you
    > modem and router (if you have one). Some have static IPs (but are fading
    > out fast). Some want the IP to go to you modem and pass through, others
    > expect your modem/router DNS to be turned on and a (NAT) translation to
    > occur and you have your local DNS on. And other things. You can't mix
    > the settings rules they set up and it's hard to predict what they want
    > unless it's a known carrier with some of the very common setup we all know
    > by now. This is probably why JAYS is showing up. So you said you sent a
    > query into your provider. I'd suggest calling them. Tell them it is an
    > initial setup and you need directions. BTW your modem is on their
    > approved list. Is it not.? I am also surprised you can not get to their
    > help/setup page, from another computer maybe. The setup info has got to
    > be there for you. You are not alone. Please check with them.
    >
    > --
    > BobF.
    > "RalfG" <itsnotme@ladeda.deda> wrote in message
    > news:BF84F798-CE74-408B-BE52-F5D7C90E889B@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> Anything specific?
    >> Just based on my own configs, present and past ,with various hardware and
    >> Windows OS's. Trying to be as generic as possible under the
    >> circumstances.
    >>
    >> "Bob F." <bob@NOSPAN.com> wrote in message
    >> news:uOy1ZiuhIHA.3788@TK2MSFTNGP03.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> RalfG,
    >>> From where did you get your settings instructions?
    >>>
    >>> --
    >>> BobF.
    >>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>> news:eFDACeuhIHA.4140@TK2MSFTNGP04.phx.gbl...
    >>>> The modem is set up for DNS forwarding, and the DNS IP's are configured
    >>>> on the modem. With regards to the NetBios over TCP/IP, I just disabled
    >>>> this (thanks for the advice).
    >>>>
    >>>> What is confusing me here is your comments regarding the DHCP server on
    >>>> the modem. Presumably, any internet IP address the modem gives me has
    >>>> to have come from the ISP. The ISP assigned the internet IP to the
    >>>> modem, the modem assigns this to me. (Even if I unplugged my machine
    >>>> from the modem for 30 mins).
    >>>>
    >>>> How would the above cause the confusion wrt another machine ('JAYS')
    >>>> appearing to be on my network?
    >>>> Somehow a NetBIOS message was broadcast, to this other machine on what
    >>>> the modem/router believed to be my network. How could this have
    >>>> happened?
    >>>>
    >>>>
    >>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>> news:C7150467-0DF3-49C9-BFFD-3D3B960F5041@microsoft.com...
    >>>>> Looks like a bit of a dog's breakfast. :)
    >>>>> Questionable entries marked with -******************
    >>>>>
    >>>>> You said earlier that the computer was getting a dynamic IP from your
    >>>>> ISP but the way it is configured below I can't see that happening
    >>>>> reliably. You've got two conflicting DHCP services active.
    >>>>> The default Gateway is set to an internet IP but the DHCP server
    >>>>> listed is the modem/router, which presumable can only supply LAN
    >>>>> addresses within its own network subnet (192.168.0.x). Your ISP will
    >>>>> have it's own dedicated DHCP servers which are on internet IPs. That
    >>>>> is where the 68.127.175.71 address came from. Aside from that the
    >>>>> modem's internal DHCP server wouldn't know which internet IPs were
    >>>>> available and which ones were already being assigned to someone else.
    >>>>> This could be where your mystery connection is being created. Also the
    >>>>> subnet mask for your internet IP is set for the 192.168.0.x subnet
    >>>>> rather than for internet which is not okay.
    >>>>>
    >>>>> Your DNS server is set to a local LAN address (192.168.0.1) rather
    >>>>> than the ISP's DNS servers, which is probably okay if the modem/router
    >>>>> has the real DNS server addresses and DNS forwarding is enabled.
    >>>>> Otherwise these lines should be showing two different IPs from your
    >>>>> ISP. NetBios is enabled on your ethernet TCP/IP adapter but without
    >>>>> NAT or firewall protection in the modem/router this is not a good idea
    >>>>> over an open internet connection.
    >>>>>
    >>>>> It looks like the modem/router's actual LAN IP is 192.168.0.1. That's
    >>>>> the address you should browse to in IE to access the modem's
    >>>>> configuration pages. How you need to configure the computer's network
    >>>>> settings depends on how the modem has been configured but I think at
    >>>>> the very least you should be disabling the modem's onboard DHCP server
    >>>>> if your computer's adapter is intended to get an address automatically
    >>>>> from your ISP. Setting the router's DNS to pass-through mode rather
    >>>>> than forwarding isn't absolutely necessary but it eliminates the extra
    >>>>> rerouting step. In the various DNS Suffix lines I'd expect to see
    >>>>> entries referencing your ISP's domain name. I suspect the tunnel
    >>>>> adapters listed below are just redundant.
    >>>>>
    >>>>>
    >>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>> news:O3ZdjXihIHA.200@TK2MSFTNGP02.phx.gbl...
    >>>>>>
    >>>>>> Windows IP Configuration
    >>>>>>
    >>>>>> Host Name . . . . . . . . . . . . : mypc
    >>>>>> Primary Dns Suffix . . . . . . . :
    >>>>>> Node Type . . . . . . . . . . . . : Hybrid
    >>>>>> IP Routing Enabled. . . . . . . . : No
    >>>>>> WINS Proxy Enabled. . . . . . . . : No
    >>>>>> DNS Suffix Search List. . . . . . :
    >>>>>> domain_not_set.invalid--*******************
    >>>>>>
    >>>>>> Ethernet adapter Local Area Connection:
    >>>>>>
    >>>>>> Connection-specific DNS Suffix . :
    >>>>>> domain_not_set.invalid---************************
    >>>>>> Description . . . . . . . . . . . : NVIDIA nForce Networking
    >>>>>> Controller
    >>>>>> Physical Address. . . . . . . . . : 00-16-D3-A2-E7-AD
    >>>>>> DHCP Enabled. . . . . . . . . . . : Yes
    >>>>>> Autoconfiguration Enabled . . . . : Yes
    >>>>>> Link-local IPv6 Address . . . . . :
    >>>>>> ff80::80f6:625f:f376:8301%6(Preferred)
    >>>>>> IPv4 Address. . . . . . . . . . . : 68.127.175.71(Preferred)
    >>>>>> Subnet Mask . . . . . . . . . . . :
    >>>>>> 255.255.255.0 --*********************
    >>>>>> Lease Obtained. . . . . . . . . . : Friday, March 14, 2008 12:05:54
    >>>>>> PM
    >>>>>> Lease Expires . . . . . . . . . . : Friday, March 14, 2008 3:41:18
    >>>>>> PM
    >>>>>> Default Gateway . . . . . . . . . : 68.127.175.72
    >>>>>> DHCP Server . . . . . . . . . . . :
    >>>>>> 192.168.0.1--*********************
    >>>>>> DHCPv6 IAID . . . . . . . . . . . : 203332435
    >>>>>> DNS Servers . . . . . . . . . . . :
    >>>>>> 192.168.0.1--*********************
    >>>>>>
    >>>>>> 192.168.0.1--*********************
    >>>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
    >>>>>>
    >>>>>> Tunnel adapter Local Area Connection* 6:
    >>>>>>
    >>>>>> Connection-specific DNS Suffix . : domain_not_set.invalid
    >>>>>> Description . . . . . . . . . . . : isatap.domain_not_set.invalid
    >>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>>>>> DHCP Enabled. . . . . . . . . . . : No
    >>>>>> Autoconfiguration Enabled . . . . : Yes
    >>>>>> Link-local IPv6 Address . . . . . :
    >>>>>> ff80::200:5fff:68.128.185.71%14(Preferred
    >>>>>> )
    >>>>>> Default Gateway . . . . . . . . . :
    >>>>>> DNS Servers . . . . . . . . . . . : 192.168.0.1--******************
    >>>>>>
    >>>>>> 192.168.0.1--********************
    >>>>>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>>>>
    >>>>>> Tunnel adapter Local Area Connection* 7:
    >>>>>>
    >>>>>> Connection-specific DNS Suffix . :
    >>>>>> Description . . . . . . . . . . . : Teredo Tunneling
    >>>>>> Pseudo-Interface
    >>>>>> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    >>>>>> DHCP Enabled. . . . . . . . . . . : No
    >>>>>> Autoconfiguration Enabled . . . . : Yes
    >>>>>> IPv6 Address. . . . . . . . . . . :
    >>>>>> 2001:0:4337:9f66:18f9:3343:ff80:50f8(Pref
    >>>>>> erred)
    >>>>>> Link-local IPv6 Address . . . . . :
    >>>>>> ff80::38f9:3343:ff80:50f8%12(Preferred)
    >>>>>> Default Gateway . . . . . . . . . :
    >>>>>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>>>>
    >>>>>> Tunnel adapter Local Area Connection* 14:
    >>>>>>
    >>>>>> Media State . . . . . . . . . . . : Media disconnected
    >>>>>> Connection-specific DNS Suffix . :
    >>>>>> Description . . . . . . . . . . . : 6TO4 Adapter
    >>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>>>>> DHCP Enabled. . . . . . . . . . . : No
    >>>>>> Autoconfiguration Enabled . . . . : Yes
    >>>>>>
    >>>>>> Tunnel adapter Local Area Connection* 10:
    >>>>>>
    >>>>>> Connection-specific DNS Suffix . : domain_not_set.invalid
    >>>>>> Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
    >>>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    >>>>>> DHCP Enabled. . . . . . . . . . . : No
    >>>>>> Autoconfiguration Enabled . . . . : Yes
    >>>>>> Temporary IPv6 Address. . . . . . :
    >>>>>> 2002:227f:ff27::227f:ff27(Preferred)
    >>>>>> Default Gateway . . . . . . . . . : 2002:f058:6301::f058:6301
    >>>>>> DNS Servers . . . . . . . . . . . :
    >>>>>> 192.168.0.1---*******************
    >>>>>>
    >>>>>> 192.168.0.1--*************************
    >>>>>> NetBIOS over Tcpip. . . . . . . . : Disabled
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>>> news:C5E12624-0EEF-4A6D-84C9-AF9BB6440665@microsoft.com...
    >>>>>>> Open a command prompt and enter "ipconfig /all", without the quotes.
    >>>>>>> What do you get?
    >>>>>>>
    >>>>>>> Other points in-line below.
    >>>>>>>
    >>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>> news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...
    >>>>>>>> 0016D3A2E7AD is my machines regular (wire) network card. The
    >>>>>>>> wireless card is disabled in device manager (which presumably rules
    >>>>>>>> any wireles connection out). 68.127.186.255 is AT&T's network,
    >>>>>>>> which is my ISP (ARIN lookup below):
    >>>>>>>>
    >>>>>>>> AT&T Internet Services SBCIS-SIS80 (NET-68-120-0-0-1)
    >>>>>>>> 68.120.0.0 - 68.127.255.255
    >>>>>>>> bras4.pltnca SBC068127176000040211 (NET-68-127-176-0-1)
    >>>>>>>> 68.127.176.0 - 68.127.191.255
    >>>>>>>>
    >>>>>>>> The constantly repeating reconnection notices at 5 minute
    >>>>>>>> intervals, (with resulting successfully assigned IP addresses), is
    >>>>>>>> probably a result of the fact that I remove the ethernet cable from
    >>>>>>>> my network card whenever I step away from my machine.
    >>>>>>>
    >>>>>>> You really shouldn't do that. Only USB is generally safe to
    >>>>>>> hot-plug. Sooner or later you're luck will run out and one or the
    >>>>>>> other ethernet devices will fry. That aside, unplugging it doesn't
    >>>>>>> account for those repeating reconnections. The timing is too
    >>>>>>> consistent, down to the second.
    >>>>>>>
    >>>>>>>>
    >>>>>>>> The only other remotely possible connection to my PC would have
    >>>>>>>> been bluetooth, however the wireless card which provides bluetooth
    >>>>>>>> connectivity is always turned off (at the switch).
    >>>>>>>>
    >>>>>>>> This leaves 2 questions
    >>>>>>>>
    >>>>>>>> 1) How could there be a master browser called JAYS showing up on my
    >>>>>>>> logs (given the above).
    >>>>>>>
    >>>>>>> You would both have to be peers connected on the same LAN or
    >>>>>>> directly to each other (same thing). Any PC on a LAN can be a master
    >>>>>>> browser. I have one XP PC on mine that always insists on taking that
    >>>>>>> status when it joins the LAN.
    >>>>>>>
    >>>>>>>> and (less importantly)
    >>>>>>>>
    >>>>>>>> 2) Why is my machine having a conversation with the outside world
    >>>>>>>> (my ISP) about its workgroup. My understanding was that a
    >>>>>>>> workgroup would be something that would be limited to my LAN alone.
    >>>>>>>
    >>>>>>> Let's see what ipconfig shows.
    >>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>>>>> news:6AD5B7D8-0DFF-4421-8DF9-3FF57637594C@microsoft.com...
    >>>>>>>>> The anomalous name being in the router was only a suggestion, it's
    >>>>>>>>> an option in mine that could also be in yours. As far as not
    >>>>>>>>> finding the LAN DHCP server in the netbios table, this ....
    >>>>>>>>>
    >>>>>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002 None
    >>>>>>>>> The IP
    >>>>>>>>>>>> address lease 192.168.1.64 for the Network Card with network
    >>>>>>>>>>>> address 0016D3A2E7AD has been denied by the DHCP server
    >>>>>>>>>>>> 192.168.0.1 (The DHCP Server sent a DHCPNACK message).
    >>>>>>>>>
    >>>>>>>>> says that it exists, at least some of the time, and that your
    >>>>>>>>> computer tried to use it with an incorrect network address and got
    >>>>>>>>> booted. This on the other hand....
    >>>>>>>>>
    >>>>>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name ""WORKGROUP
    >>>>>>>>> :1d""
    >>>>>>>>>>>> could not be registered on the interface with IP address
    >>>>>>>>>>>> 68.127.186.115. The computer with the IP address 68.127.186.255
    >>>>>>>>>>>> did not allow the name to be claimed by this computer."
    >>>>>>>>>
    >>>>>>>>> says your computer subsequently tried to connect to a server on
    >>>>>>>>> the internet, probably your ISP, possibly somewhere else. There's
    >>>>>>>>> no indication here whether it is the same network adapter making
    >>>>>>>>> the connection as the one above but we can see from the text that
    >>>>>>>>> your network adapter in this case also "somehow" had some
    >>>>>>>>> incorrect information set in its configuration at the time.
    >>>>>>>>>
    >>>>>>>>> OTOH these constantly repeating reconnection notices at 5 minute
    >>>>>>>>> intervals....
    >>>>>>>>>
    >>>>>>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>
    >>>>>>>>> Are very much like what you can see happening with wireless
    >>>>>>>>> connections. If I were going to make a guess as to what is going
    >>>>>>>>> on here I'd say that apart from the ethernet adapter you connect
    >>>>>>>>> to your own modem with you do have a wireless adapter in that
    >>>>>>>>> computer, it is always turned on and it is set to automatically
    >>>>>>>>> connect to any available network. Every so often your PC is
    >>>>>>>>> piggybacking a ride, or trying to, on poor JAYS wireless network.
    >>>>>>>>> :)
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>>> news:OUZ0QCKhIHA.4740@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>>>
    >>>>>>>>>> If JAYS were the name of the modem or in its netbios table, then
    >>>>>>>>>> it should still be there presumably. (I have not reconfigured
    >>>>>>>>>> the modem in several months, and at that I time I set it to
    >>>>>>>>>> factory defaults - so the name JAYS should not be assigned to the
    >>>>>>>>>> modem).
    >>>>>>>>>>
    >>>>>>>>>> I checked the mode that the modem is operating. This is as
    >>>>>>>>>> follows:
    >>>>>>>>>>
    >>>>>>>>>> PPP is on the modem. (PPP session is initiated from the modem.) -
    >>>>>>>>>> i.e. Not operating in Bridging mode
    >>>>>>>>>>
    >>>>>>>>>> I believe my DHCP server is assigned by the gateway, when I
    >>>>>>>>>> connect (i.e. no static IP configured on my machine).
    >>>>>>>>>>
    >>>>>>>>>> I did a lookup of the netbios name table on my PC which I listed
    >>>>>>>>>> below (When I tried nbtstat -a 192.168.0.1 for the modem I got
    >>>>>>>>>> "host not found").
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>> NetBIOS Local Name Table
    >>>>>>>>>>
    >>>>>>>>>> Name Type Status
    >>>>>>>>>> ---------------------------------------------
    >>>>>>>>>> MYPC <00> UNIQUE Registered
    >>>>>>>>>> WORKGROUP <00> GROUP Registered
    >>>>>>>>>> MYPC <20> UNIQUE Registered
    >>>>>>>>>> WORKGROUP <1E> GROUP Registered
    >>>>>>>>>> WORKGROUP <1D> UNIQUE Registered
    >>>>>>>>>> ..__MSBROWSE__. <01> GROUP Registered
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>> "RalfG" <itsnotme@ladeda.deda> wrote in message
    >>>>>>>>>> news:EBF529EE-1C6A-4D4F-BB48-82EA200A86A9@microsoft.com...
    >>>>>>>>>>> It looks like your network connection may be misconfigured. From
    >>>>>>>>>>> the events at timestamp 10:01 and later it appears you have two
    >>>>>>>>>>> conflicting DHCP services being used. You have a DHCP server at
    >>>>>>>>>>> 192.168.0.1 which I presume is the DSL Modem with routing
    >>>>>>>>>>> capabilities enabled. You are also trying to get a DHCP address
    >>>>>>>>>>> directly from your ISP, probably using IP 68.127.186.255 as the
    >>>>>>>>>>> DHCP server address. You should use only one or the other. I'd
    >>>>>>>>>>> try turning off DHCP in the modem first and see how that works
    >>>>>>>>>>> out.
    >>>>>>>>>>>
    >>>>>>>>>>> The modem can probably be configured in several different
    >>>>>>>>>>> operating modes. I have no way of knowing what your available
    >>>>>>>>>>> options are or which mode has been enabled. My own has 4
    >>>>>>>>>>> distinct DSL operating modes plus various combinations of
    >>>>>>>>>>> routing and firewall features. IOW, there are umpteen ways to
    >>>>>>>>>>> screw up the connection. :)
    >>>>>>>>>>>
    >>>>>>>>>>> Typically there are two common connection modes that might be
    >>>>>>>>>>> used. One way is to have the modem set in 'bridge" mode, where
    >>>>>>>>>>> it only makes the hardware connection to the DSL carrier signal.
    >>>>>>>>>>> You would Windows built in PPPOE "dialer" to log into your ISP
    >>>>>>>>>>> from your computer. In this configuration the ISP's DHCP server
    >>>>>>>>>>> would give your computer an internet IP ... i.e..
    >>>>>>>>>>> 68.127.186.115. You would need to set up your ISP username and
    >>>>>>>>>>> password in the PPPOE dialer to log on. Workgroup related
    >>>>>>>>>>> settings in the PC would be irrelevant in this case as long as
    >>>>>>>>>>> the computer can communicate to the modem. The PPPOE dialer is a
    >>>>>>>>>>> virtual device which becomes the effective internet connection.
    >>>>>>>>>>> All of the required settings information would be supplied by
    >>>>>>>>>>> the ISP. Alternatively, a router could be used instead to make
    >>>>>>>>>>> the connections through the modem when it is in this
    >>>>>>>>>>> configuration.
    >>>>>>>>>>>
    >>>>>>>>>>> In the second configuration your modem could be set to connect
    >>>>>>>>>>> to the ISP automatically using its own internal firmware. The
    >>>>>>>>>>> relevant networking settings are made in the modem using its web
    >>>>>>>>>>> interface, either by you yourself or sometimes this information
    >>>>>>>>>>> is pre-programmed in the modem by the ISP if they supplied the
    >>>>>>>>>>> modem. You can normally access the modem's web interface using
    >>>>>>>>>>> your browser (try typing 192.168.0.1 in the address bar). The
    >>>>>>>>>>> modem could be set to auto-dial (AKA always-on) or "dial on
    >>>>>>>>>>> demand" mode (i.e.. the modem connects whenever the PC tries to
    >>>>>>>>>>> access the internet and can disconnect again after a set timeout
    >>>>>>>>>>> period of no activity). In this configuration it is the modem
    >>>>>>>>>>> which gets the internet IP from your ISP and then passes the
    >>>>>>>>>>> internet connection to the PC through its LAN port at address
    >>>>>>>>>>> 192.168.0.1 (or whatever the default is). Routing and DHCP may
    >>>>>>>>>>> or may not be enabled in the modem, but if they are enabled your
    >>>>>>>>>>> computer should use 192.168.0.1 as its DHCP server address and
    >>>>>>>>>>> receive a LAN address from the modem, not an internet IP.
    >>>>>>>>>>> Possibly 192.168.0.1 should be also entered into the computer's
    >>>>>>>>>>> TCP/IP settings as the gateway address if DNS pass-through is
    >>>>>>>>>>> enabled in the modem. Otherwise the ISP's DNS server addresses
    >>>>>>>>>>> should be used. If DHCP is not enabled in the modem you would
    >>>>>>>>>>> enter a fixed LAN address into the computer's TCP/IP
    >>>>>>>>>>> configuration, in the range 192.168.0.x. The modem itself might
    >>>>>>>>>>> have an optional workgroup or domain name entered into its LAN
    >>>>>>>>>>> configuration settings, which is where 'JAYS' could be coming
    >>>>>>>>>>> from. You can probably change or eliminate that yourself.
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>>>>> news:%23ObFDy%23gIHA.5280@TK2MSFTNGP04.phx.gbl...
    >>>>>>>>>>>> No its a dynamic IP Address assigned by my ISP
    >>>>>>>>>>>>
    >>>>>>>>>>>> I have attached all of the event log in the 3 hours around the
    >>>>>>>>>>>> time of the browser conflict below. Im not sure if this
    >>>>>>>>>>>> contains any other information which might give a clue as to
    >>>>>>>>>>>> what is going on.
    >>>>>>>>>>>>
    >>>>>>>>>>>> Level Date and Time Source Event ID Task Category
    >>>>>>>>>>>> Information 3/5/2008 12:32:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 12:27:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 12:22:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 12:17:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 12:12:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 12:11:07 PM Service Control Manager 7036
    >>>>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>>>> Information 3/5/2008 12:10:11 PM Service Control Manager 7036
    >>>>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>>>> Information 3/5/2008 12:07:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 12:02:30 PM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 12:00:46 PM EventLog 6013 None The system
    >>>>>>>>>>>> uptime is 57335 seconds.
    >>>>>>>>>>>> Information 3/5/2008 11:57:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 11:52:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Error 3/5/2008 11:48:19 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Information 3/5/2008 11:47:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Error 3/5/2008 11:43:09 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Information 3/5/2008 11:42:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Error 3/5/2008 11:37:59 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Information 3/5/2008 11:37:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Error 3/5/2008 11:32:49 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Information 3/5/2008 11:32:41 AM Microsoft-Windows-User-PnP
    >>>>>>>>>>>> 20003 None Driver Management has concluded the process to add
    >>>>>>>>>>>> Service tunnel for Device Instance ID ROOT*6TO4MP001 with
    >>>>>>>>>>>> the following status: 0.
    >>>>>>>>>>>> Information 3/5/2008 11:32:30 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>>> Information 3/5/2008 11:32:26 AM Tcpip 4201 None The system
    >>>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>>> Information 3/5/2008 11:28:17 AM BROWSER 8033 None The browser
    >>>>>>>>>>>> has forced an election on network
    >>>>>>>>>>>> DeviceNetBT_Tcpip_{6C1B0769-602C-49AD-95C1-0AD3B66DA864}
    >>>>>>>>>>>> because a master browser was stopped.
    >>>>>>>>>>>> Information 3/5/2008 11:24:52 AM Service Control Manager 7036
    >>>>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service
    >>>>>>>>>>>> entered the stopped state.
    >>>>>>>>>>>> Information 3/5/2008 11:24:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 11:19:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 11:14:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 11:09:56 AM Service Control Manager 7036
    >>>>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>>>> Information 3/5/2008 11:09:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 11:08:55 AM Service Control Manager 7036
    >>>>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>>>> Information 3/5/2008 11:08:22 AM Service Control Manager 7036
    >>>>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service
    >>>>>>>>>>>> entered the running state.
    >>>>>>>>>>>> Information 3/5/2008 11:05:06 AM volsnap 33 None The oldest
    >>>>>>>>>>>> shadow copy of volume C: was deleted to keep disk space usage
    >>>>>>>>>>>> for shadow copies of volume C: below the user defined limit.
    >>>>>>>>>>>> Information 3/5/2008 11:04:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 10:59:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 10:54:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 10:49:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Error 3/5/2008 10:45:09 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Error 3/5/2008 10:45:09 AM BROWSER 8009 None The browser was
    >>>>>>>>>>>> unable to promote itself to master browser. The computer that
    >>>>>>>>>>>> currently believes it is the master browser is JAYS.
    >>>>>>>>>>>> Information 3/5/2008 10:44:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Error 3/5/2008 10:39:59 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Information 3/5/2008 10:39:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Error 3/5/2008 10:34:49 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Information 3/5/2008 10:34:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Error 3/5/2008 10:29:38 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Information 3/5/2008 10:29:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Error 3/5/2008 10:24:28 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Information 3/5/2008 10:24:21 AM Microsoft-Windows-User-PnP
    >>>>>>>>>>>> 20003 None Driver Management has concluded the process to add
    >>>>>>>>>>>> Service tunnel for Device Instance ID ROOT*6TO4MP001 with
    >>>>>>>>>>>> the following status: 0.
    >>>>>>>>>>>> Information 3/5/2008 10:24:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>>> Information 3/5/2008 10:24:06 AM Tcpip 4201 None The system
    >>>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>>> Information 3/5/2008 10:18:41 AM Service Control Manager 7036
    >>>>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service
    >>>>>>>>>>>> entered the stopped state.
    >>>>>>>>>>>> Error 3/5/2008 10:17:06 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Information 3/5/2008 10:16:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Error 3/5/2008 10:11:54 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Information 3/5/2008 10:11:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Error 3/5/2008 10:06:42 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Information 3/5/2008 10:06:09 AM Microsoft-Windows-Dhcp-Client
    >>>>>>>>>>>> 1103 None Your computer was successfully assigned an address
    >>>>>>>>>>>> from the network, and it can now connect to other computers.
    >>>>>>>>>>>> Information 3/5/2008 10:05:43 AM Service Control Manager 7036
    >>>>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>>>> Information 3/5/2008 10:05:33 AM Service Control Manager 7036
    >>>>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>>>> Information 3/5/2008 10:05:26 AM Service Control Manager 7036
    >>>>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>>>> Information 3/5/2008 10:02:39 AM Service Control Manager 7036
    >>>>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>>>> Information 3/5/2008 10:02:11 AM Service Control Manager 7036
    >>>>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service
    >>>>>>>>>>>> entered the running state.
    >>>>>>>>>>>> Information 3/5/2008 10:01:36 AM Microsoft-Windows-User-PnP
    >>>>>>>>>>>> 20003 None Driver Management has concluded the process to add
    >>>>>>>>>>>> Service tunnel for Device Instance ID ROOT*6TO4MP001 with
    >>>>>>>>>>>> the following status: 0.
    >>>>>>>>>>>> Error 3/5/2008 10:01:30 AM netbt 4321 None "The name
    >>>>>>>>>>>> ""WORKGROUP :1d"" could not be registered on the interface with
    >>>>>>>>>>>> IP address 68.127.186.115. The computer with the IP address
    >>>>>>>>>>>> 68.127.186.255 did not allow the name to be claimed by this
    >>>>>>>>>>>> computer."
    >>>>>>>>>>>> Information 3/5/2008 10:01:17 AM Microsoft-Windows-User-PnP
    >>>>>>>>>>>> 20003 None Driver Management has concluded the process to add
    >>>>>>>>>>>> Service tunnel for Device Instance ID ROOT*ISATAP002 with
    >>>>>>>>>>>> the following status: 0.
    >>>>>>>>>>>> Error 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1002
    >>>>>>>>>>>> None The IP address lease 192.168.1.64 for the Network Card
    >>>>>>>>>>>> with network address 0016D3A2E7AD has been denied by the DHCP
    >>>>>>>>>>>> server 192.168.0.1 (The DHCP Server sent a DHCPNACK message).
    >>>>>>>>>>>> Warning 3/5/2008 10:01:08 AM Microsoft-Windows-Dhcp-Client 1003
    >>>>>>>>>>>> None "The description for Event ID 1003 from source
    >>>>>>>>>>>> Microsoft-Windows-Dhcp-Client cannot be found. Either the
    >>>>>>>>>>>> component that raises this event is not installed on your local
    >>>>>>>>>>>> computer or the installation is corrupted. You can install or
    >>>>>>>>>>>> repair the component on the local computer.
    >>>>>>>>>>>>
    >>>>>>>>>>>> If the event originated on another computer, the display
    >>>>>>>>>>>> information had to be saved with the event.
    >>>>>>>>>>>>
    >>>>>>>>>>>> The following information was included with the event:
    >>>>>>>>>>>>
    >>>>>>>>>>>> 0016D3A2E7AD
    >>>>>>>>>>>> %%2163146757
    >>>>>>>>>>>>
    >>>>>>>>>>>> The description string for parameter reference (%1) could not
    >>>>>>>>>>>> be found
    >>>>>>>>>>>> "
    >>>>>>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>>> Information 3/5/2008 10:00:52 AM Tcpip 4201 None The system
    >>>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>>> Information 3/5/2008 9:57:44 AM Service Control Manager 7036
    >>>>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>>>> Information 3/5/2008 9:57:37 AM Service Control Manager 7036
    >>>>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>>>> Information 3/5/2008 9:52:42 AM Service Control Manager 7036
    >>>>>>>>>>>> None The LiveUpdate service entered the stopped state.
    >>>>>>>>>>>> Information 3/5/2008 9:52:35 AM Service Control Manager 7036
    >>>>>>>>>>>> None The LiveUpdate service entered the running state.
    >>>>>>>>>>>> Information 3/5/2008 9:38:26 AM Service Control Manager 7036
    >>>>>>>>>>>> None The WinHTTP Web Proxy Auto-Discovery Service service
    >>>>>>>>>>>> entered the stopped state.
    >>>>>>>>>>>> Information 3/5/2008 9:37:56 AM Microsoft-Windows-User-PnP
    >>>>>>>>>>>> 20003 None Driver Management has concluded the process to add
    >>>>>>>>>>>> Service tunnel for Device Instance ID ROOT*ISATAP002 with
    >>>>>>>>>>>> the following status: 0.
    >>>>>>>>>>>> Information 3/5/2008 9:37:48 AM Service Control Manager 7036
    >>>>>>>>>>>> None The Windows Image Acquisition (WIA) service entered the
    >>>>>>>>>>>> running state.
    >>>>>>>>>>>> Information 3/5/2008 9:37:39 AM
    >>>>>>>>>>>> Microsoft-Windows-Power-Troubleshooter 1 None "The system has
    >>>>>>>>>>>> resumed from sleep.
    >>>>>>>>>>>>
    >>>>>>>>>>>> Sleep Time: 3/5/2008 7:12:57 AM
    >>>>>>>>>>>> Wake Time: 3/5/2008 5:37:34 PM
    >>>>>>>>>>>>
    >>>>>>>>>>>> Wake Source: Unknown"
    >>>>>>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system
    >>>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>>> Information 3/5/2008 9:37:37 AM Tcpip 4201 None The system
    >>>>>>>>>>>> detected that network adapter Local Area Connection was
    >>>>>>>>>>>> connected to the network, and has initiated normal operation.
    >>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>> "Bob F." <bob@NOSPAN.com> wrote in message
    >>>>>>>>>>>> news:52055B79-F315-4C46-986D-CB8AFBFF2D37@microsoft.com...
    >>>>>>>>>>>>> Where did you get the setup information for your internet
    >>>>>>>>>>>>> connection? Did you use a static IP? Maybe it's incorrect and
    >>>>>>>>>>>>> you are encroaching onto someone else's IP space.
    >>>>>>>>>>>>>
    >>>>>>>>>>>>> --
    >>>>>>>>>>>>> BobF.
    >>>>>>>>>>>>> "Dave" <dave@beepbeep.com> wrote in message
    >>>>>>>>>>>>> news:eBrCR47gIHA.4436@TK2MSFTNGP02.phx.gbl...
    >>>>>>>>>>>>>> What shows up in Start - Network?
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>>
    >>>>>>>>>>>>>> "Nubie" <newsgoup_contact@atigen.com> wrote in message
    >>>>>>>>>>>>>> news:#orAgk7gIHA.2448@TK2MSFTNGP03.phx.gbl...
    >>>>>>>>>>>>>>> My (lone) machine is connected directly to the DSL router
    >>>>>>>>>>>>>>> with no wireless capabilities on the router. Despite this I
    >>>>>>>>>>>>>>> get the following message in the event log:
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> The browser was unable to promote itself to master browser.
    >>>>>>>>>>>>>>> The computer that currently believes it is the master
    >>>>>>>>>>>>>>> browser is JAYS.
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> Once again, my computer is not called JAYS. Friends and
    >>>>>>>>>>>>>>> family are not Vista Security experts. Looking for capable
    >>>>>>>>>>>>>>> / expert advice from this forum.
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> What are the possible explanations for this???
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>> "Malke" <malke@invalid.invalid> wrote in message
    >>>>>>>>>>>>>>> news:O5eVD62gIHA.4692@TK2MSFTNGP05.phx.gbl...
    >>>>>>>>>>>>>>>> Nubie wrote:
    >>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>> What should I be looking for in the Settings?
    >>>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>> ALSO: How would the config of my DSL modem confuse my
    >>>>>>>>>>>>>>>>> vista machine to
    >>>>>>>>>>>>>>>>> think that there is another computer called JAYS on my
    >>>>>>>>>>>>>>>>> local network.
    >>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>>> Nubie;642434 Wrote:
    >>>>>>>>>>>>>>>>>>> Hi
    >>>>>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>>>> I have a single (lone) windows Vista machine connected
    >>>>>>>>>>>>>>>>>>> directly to the
    >>>>>>>>>>>>>>>>>>> internet via a dsl modem. I just viewed the following in
    >>>>>>>>>>>>>>>>>>> my eventlogs:
    >>>>>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>>>> "The browser was unable to promote itself to master
    >>>>>>>>>>>>>>>>>>> browser. The
    >>>>>>>>>>>>>>>>>>> computer
    >>>>>>>>>>>>>>>>>>> that
    >>>>>>>>>>>>>>>>>>> currently believes it is the master browser is JAYS. My
    >>>>>>>>>>>>>>>>>>> machine is NOT
    >>>>>>>>>>>>>>>>>>> called JAYS."
    >>>>>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>>>> What is happening here!!?? If my machine is connected to
    >>>>>>>>>>>>>>>>>>> a DSL modem
    >>>>>>>>>>>>>>>>>>> with
    >>>>>>>>>>>>>>>>>>> no additional
    >>>>>>>>>>>>>>>>>>> machines connected to that modem why is this message
    >>>>>>>>>>>>>>>>>>> appearing ????
    >>>>>>>>>>>>>>>>>>> What is
    >>>>>>>>>>>>>>>>>>> happening here ??
    >>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>> It certainly seems as though someone else is on your
    >>>>>>>>>>>>>>>> network. Is this a
    >>>>>>>>>>>>>>>> combination modem/wireless router? If yes, you probably
    >>>>>>>>>>>>>>>> haven't secured
    >>>>>>>>>>>>>>>> your wireless properly and a stranger is using your
    >>>>>>>>>>>>>>>> bandwidth. If you only
    >>>>>>>>>>>>>>>> have a single computer connected directly to a DSL modem by
    >>>>>>>>>>>>>>>> ethernet cable
    >>>>>>>>>>>>>>>> (no wireless router), then call your ISP. Because you don't
    >>>>>>>>>>>>>>>> really know
    >>>>>>>>>>>>>>>> what you're looking at - and I mean no disrespect to you,
    >>>>>>>>>>>>>>>> I'm just being
    >>>>>>>>>>>>>>>> practical - it might be smart for you to have a computer
    >>>>>>>>>>>>>>>> professional come
    >>>>>>>>>>>>>>>> on-site and take a look. This will not be someone from a
    >>>>>>>>>>>>>>>> BigComputerStore/GeekSquad type of place. Get
    >>>>>>>>>>>>>>>> recommendations from friends,
    >>>>>>>>>>>>>>>> family, colleagues.
    >>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>> Malke
    >>>>>>>>>>>>>>>> --
    >>>>>>>>>>>>>>>> MS-MVP
    >>>>>>>>>>>>>>>> Elephant Boy Computers
    >>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>> Don't Panic!
    >>>>>>>>>>>>>>>
    >>>>>>>>>>>>>
    >>>>>>>>>>>>
    >>>>>>>>>>>
    >>>>>>>>>>
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>
    >>>>
    >>><!--colorc--><!--/colorc-->
    >><!--colorc--><!--/colorc-->
    > <!--colorc--><!--/colorc-->
     
    RalfG, Mar 16, 2008
    #31
  13. FromTheRafters

    FromTheRafters Guest

    [snip]

    Do you really need to post such large messages?

    For those who would fault me for oversnipping - I refer you to this message
    for continuity.

    Message-ID: <E69B6194-CE35-4797-BA9E-89F62B714C56@microsoft.com>
     
    FromTheRafters, Mar 16, 2008
    #32
Page 2 of 2

Share This Page