Ipconfig missing?

[Doo-dah]

Hi

I've been trying to set up ICS between my XP Pro machine and my
daughter's Win ME machine.

I can get the network going (sometimes) but when I try to check using
IPCONFIG on my machine, (Start - Cmd - IPCONFIG) I get a message stating
that 'IPCONFIG is not recognised as an internal or external command,
operable program or batch file'.

I do hope an expert can tell me what's happening!

 

[Guest]

I would try Ripping and Reinstalling TCP/IP.

 

[Guest]

I have the same problem. It seems that ipconfig is no longer supported by XP and I cant find how to display dynamic assigned ip addresses any more

 

[Guest]

I found it myself. Start/Run/Cmd/IPCONFIG does work

 

[Steve Winograd [MVP]]

Hi

I've been trying to set up ICS between my XP Pro machine and my
daughter's Win ME machine.

I can get the network going (sometimes) but when I try to check using
IPCONFIG on my machine, (Start - Cmd - IPCONFIG) I get a message stating
that 'IPCONFIG is not recognised as an internal or external command,
operable program or batch file'.

I do hope an expert can tell me what's happening!

Try this command:

C:\Windows\System32\Ipconfig

If that works, there's a problem with "Path" environment variable that
XP uses to find executable files. To see its value, enter:

echo %Path%

On my computer, that command produces the output:

C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

If any of those folder names are missing on your computer, add them
with this command:

set Path=<missing folder names separated by ;>;%Path%
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Guest]

Roger that on the ipconfig in a command prompt. I spent part of today using that very tool as described. Occasionally I would get the same error message. When I investigated, I found all were caused by typos when I was hurrying. You think?

 

[Doo-dah]

Roger that on the ipconfig in a command prompt. I spent part of today

using that very tool as described. Occasionally I would get the same
error message. When I investigated, I found all were caused by typos
when I was hurrying. You think?

No. It was because some other program had reset the <path> variable as
in the post by Steve Winograd.

But thanks for the suggestion.

 

[Doo-dah]

Try this command:

C:\Windows\System32\Ipconfig

If that works, there's a problem with "Path" environment variable that
XP uses to find executable files. To see its value, enter:

echo %Path%

On my computer, that command produces the output:

C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

If any of those folder names are missing on your computer, add them
with this command:

set Path=<missing folder names separated by ;>;%Path%

That did the trick, Steve. I had forgotten all about DOS commands but
did have a vague idea it might have been something to do with the <path>
variable. Some other prog had reset the path. Now I can get IPCONFIG
fine.

However, I have now changed the setup to a X-over cable between just the
two PCs. I had been using a router when I had three m/cs on the go, but
sold the standby one as the rubber band had perished as it was so old.


I STILL can't get the second machine to get an IP addy. I can only get
a 169 IP. I'm suspecting a duff X-over cable.

Any ideas, anyone?

 

[Steve Winograd [MVP]]

That did the trick, Steve. I had forgotten all about DOS commands but
did have a vague idea it might have been something to do with the <path>
variable. Some other prog had reset the path. Now I can get IPCONFIG
fine.

However, I have now changed the setup to a X-over cable between just the
two PCs. I had been using a router when I had three m/cs on the go, but
sold the standby one as the rubber band had perished as it was so old.


I STILL can't get the second machine to get an IP addy. I can only get
a 169 IP. I'm suspecting a duff X-over cable.

Any ideas, anyone?

If the X-over cable is bad, XP should give a message saying that a
network cable is unplugged.

Disable ICS on the XP computer, so that both computers' LAN
connections will have 169.254 IP addresses. Then, try pinging each
computer from the other.

If pinging in both directions works, the hardware is OK. In that
case, re-enable ICS on XP.

If pinging fails, it could be a hardware problem, or it could be that
a firewall program is blocking communications between the computers.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com