|
-
July 20th, 2002, 06:51 AM
#11
Aside from checking to see what's running in the background, check to see what hardware pertaining to networking the OS believes it has running. (start -> settings -> ctrl pnl -> network)
if you have something listed in there, it is more than likely the OS is trying to use it for a network connect. Some video tuners will place them selves in your network stack and bind a TCP/IP to them for various reasons. There are other devices that will bind networking protocols to themselves.. Worth a look.
Regards.
edit :
There is no way that it could have communicated to anything, that is why it is wierd to me.
Your lack of cabling is what causes the error. Your machine will initiate a DHCP request, hence the broadcast packets on 255.255.255.0. Should there have been sufficient hardware, cabling and respective DHCP servers, your system would have acquired a new DHCP lease and your system would have notified you of that as well.
\"I believe that you can reach the point where there is no longer any difference between developing the habit of pretending to believe and developing the habit of believing.\"
-
July 20th, 2002, 11:12 AM
#12
Junior Member
It basically means that your ip was dumped and your pc was unable to connect to dhcp to obtain new ip, basically, you were connected, and the last lease for the ip obtained expire while not connected, & then, due to obtain ip & dns automatically & dhcp enabled, window default settings, your pc refreshed the ip with dns to default ip, basically same as 127.0.0.1,
all shalt live forever!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|