Re: TCP/IP disabled

TCP/IP won't be disabled with network cables disconnected. You should still
be able to access the local machine at 127.0.0.1

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


"Pavel A." <pavel_a@geeklife.com> wrote in message
news:eQOHTUhUDHA.2272@TK2MSFTNGP11.phx.gbl...

> Connect it to ethernet hub (not connected to anything else).
>
> "George" <gmoss@blackcreekisc.com> wrote in message
> news:00d801c35212$19943c60$a501280a@phx.gbl...

> > I have a computer with Windows XP. We are running a
> > program that requires a tcp/ip address to be active. This
> > particular computer is a demo computer and will not be on
> > a network and must run standalone. Unplugging the network
> > cable kills the tcp/ip protocol. In Windows 2000, we added
> > a registry key to disable media sense and that worked
> > fine. It does not work on Windows XP. How can we keep the
> > tcp/ip protocol from being disabled, without having a
> > network cable connected?

>
>

I have 1 network card installed on my computer and it is
on the motherboard...What happened was I overclocked my
computer to 30% and the system hung so I had to flash the
bios. When i rebooted into windows my network connection
was all messed up. I have an internal network so in my
network connections 2 network connections show up.
My "real" nic card and then one that says 1394
Connection. The 3 com network connection gets an ip
address of 192.168... which is the internal network and
the 1394 connection used to be the one connecting to the
internet and pulling the outside ip address. The problem
is now I cant get an ip address with the 1394 connection
and when i try to repair it i get a message
saying "Tcp/ip is not enabled for this connection" and
when i go to ipconfig /all only the 3com card shows up.
Anyone know how I can repair this problem? I have
uninstalled and reinstalled the network adapters but that
didnt solve it and tcp/ip is installed on both adapters
as well.
Thanks in advance
Mike

Mike wrote:

> I have 1 network card installed on my computer and it is
> on the motherboard...What happened was I overclocked my
> computer to 30% and the system hung so I had to flash the
> bios. When i rebooted into windows my network connection
> was all messed up. I have an internal network so in my
> network connections 2 network connections show up.
> My "real" nic card and then one that says 1394
> Connection. The 3 com network connection gets an ip
> address of 192.168... which is the internal network and
> the 1394 connection used to be the one connecting to the
> internet and pulling the outside ip address. The problem
> is now I cant get an ip address with the 1394 connection
> and when i try to repair it i get a message
> saying "Tcp/ip is not enabled for this connection" and
> when i go to ipconfig /all only the 3com card shows up.
> Anyone know how I can repair this problem? I have
> uninstalled and reinstalled the network adapters but that
> didnt solve it and tcp/ip is installed on both adapters
> as well.
> Thanks in advance
> Mike

You may have fried some hardware (the NIC?), or you may have
simply caused errors to propagate from RAM to your HD. You can
try reloading the OS & drivers from scratch to test the error
hypothesis, but if you fried hardware, then replace those
pieces.

I have little sympathy for you, since the proper term for
overclocking is overcooking. {Been there, done that.}
--
Cheers, Bob