| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4390.1 | Have reproduced the problem | CSC32::R_BUCK | Authenticated and assimilated | Tue May 06 1997 15:47 | 12 |
| Just to update, this appears to be a real problem. On at least one
Windows 95 system here we get the same message when trying to use the
Find Address application. To the best of my knowledge, the executable
IPCONFIG.EXE is only present on a Windows NT system. Maybe there is
something hardcoded?
We have speculated that simply copying the file to the Windows 95
system might make the problem go away, but this would not be an
acceptable solution.
Randall Buck
MCS - Network Support
|
| 4390.2 | Same result | LEMAN::PAIVA | Hawkeye - Network Support @GEO | Wed May 07 1997 09:11 | 6 |
| Randall,
I could reproduce your problem and got address not found messages when
looking for a DECnet or MAC address...
Pedro
|
| 4390.3 | MCM Broken, problem escalated | CSC32::R_BUCK | Authenticated and assimilated | Wed May 07 1997 15:06 | 19 |
| Further speculation, (for what it's worth). Looks like at tleast one
of out lab system has the program IPCONFIG.EXE in the C:\WINDOWS
directory. Machine is running Windows 95 currently but was upgraded
from Windows for Workgroups 3.11 Pretty sure it was running the
Microsoft TCP/IP software while a WFW system.
Systems that have a 'clean' Windows 95 installation, (i.e. format the
disk and install W95), do not have the IPCONFIG.EXE program.
So, it sure looks like Multichassis Manager is wrong in assuming that
IPCONFIG.EXE will be available on a Windows 95 system. A possible
workaround would be to distribute the IPCONFIG.EXE program that appears
to be left over from a prior version of Windows, but I would guess that
something has to be worked out with Microsoft before doing this.
By the way, the problem has been formally escalated.
Randall Buck
MCS - Network Support
|
| 4390.4 | | NETCAD::DOODY | Michael Doody | Thu May 08 1997 12:12 | 7 |
| The program that provides similar information in windows 95
is called winipcfg.exe.
Just fyi, its a handy thing to know if you need to get the
IP address or hardware address of the machine.
-Mike
|
| 4390.5 | Very usefull utility, but cannot use it as a workaround | CSC32::R_BUCK | Authenticated and assimilated | Mon May 12 1997 12:12 | 8 |
| RE: .-1
We tried a workaround by making a copy of WINIPCFG.EXE to IPCONFIG.EXE
but it did not really do the trick. Window is displayed from the
program, but the MCM find address utility does not continue on.
Randall Buck
MCS - Network Support
|
| 4390.6 | Possible Workaround | NETCAD::DRAGON | | Fri May 23 1997 13:04 | 24 |
|
In looking into this a bit MCM definitely has a problem in which it
assumes that IPCONFIG.EXE is present on a WIN95 machine.
A possible hack workaround would be to write a program that displays
output similiar to IPCONFIG.EXE and either call it IPCONFIG.EXE or
within the HUBWATCH.INI file add the lines:
[arp]
ipconfig=yourprog.exe
Place yourprog.exe in your path.
The output of IPCONFIG is used to see if the IP address that you are
looking for is your own. Therefore, if you want this function to
work, yourprog.exe would actually have to display correct IP info,
otherwise have it display some IP address which you would not get
on your network.
I haven't actually tried this, but I think it will work.
This will be PTR.
Bob
|
| 4390.7 | Fixed Next Release | NETCAD::DRAGON | | Thu Jun 05 1997 14:44 | 7 |
|
This problem is fixed in the clearVISN V2.0 MCM V6.1 release.
Thanks very much for bringing this to our attention.
Regards,
Bob
|