View Full Version : troubleshooting advise needed
Matt
January 10th 04, 10:43 AM
I having some problems with the network and I'm receiving on the XP machine a private address of 169.x.x.x.
The other machines on the network seem fine, yet I cannot find what's wrong. Any suggestions would be abbreciated. Can you give me a list of ideas?
Could it be a bad network cable?
Marc Reynolds [MSFT]
January 10th 04, 10:44 AM
Could be a bad network cable, bad NIC, bad NIC driver, bad port on your hub
or router...
--
Thanks,
Marc Reynolds
Microsoft Technical Support
This posting is provided "AS IS" with no warranties, and confers no rights.
"Matt" > wrote in message
...
> I having some problems with the network and I'm receiving on the XP
machine a private address of 169.x.x.x.
>
> The other machines on the network seem fine, yet I cannot find what's
wrong. Any suggestions would be abbreciated. Can you give me a list of
ideas?
>
> Could it be a bad network cable?
Ben
January 10th 04, 10:45 AM
You have run out of IPs in the DHCP scope?
>-----Original Message-----
>Could be a bad network cable, bad NIC, bad NIC driver,
bad port on your hub
>or router...
>
>--
>
>Thanks,
>Marc Reynolds
>Microsoft Technical Support
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"Matt" > wrote in
message
>news:B93444C1-8D84-4F54-B174-
...
>> I having some problems with the network and I'm
receiving on the XP
>machine a private address of 169.x.x.x.
>>
>> The other machines on the network seem fine, yet I
cannot find what's
>wrong. Any suggestions would be abbreciated. Can you
give me a list of
>ideas?
>>
>> Could it be a bad network cable?
>
>
>.
>
vBulletin® v3.6.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.