N
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...<span style="color:blue">
> What did your ISP say?
>
> --
> BobF.
> "Nubie" <newsgoup_contact@atigen.com> wrote in message
> news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...<span style="color:green">
>> 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...<span style="color:darkred">
>>> 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 6TO4MP 001 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 6TO4MP 001 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 6TO4MP 001 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 ISATAP 002 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 ISATAP 002 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
>>>>>>>>>> www.elephantboycomputers.com
>>>>>>>>>> Don't Panic!
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>></span>
>></span>
> </span>
(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...<span style="color:blue">
> What did your ISP say?
>
> --
> BobF.
> "Nubie" <newsgoup_contact@atigen.com> wrote in message
> news:OqbxzEThIHA.4076@TK2MSFTNGP05.phx.gbl...<span style="color:green">
>> 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...<span style="color:darkred">
>>> 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 6TO4MP 001 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 6TO4MP 001 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 6TO4MP 001 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 ISATAP 002 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 ISATAP 002 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
>>>>>>>>>> www.elephantboycomputers.com
>>>>>>>>>> Don't Panic!
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>></span>
>></span>
> </span>