IPConfig is blank

[Ian Fry]

I have had the PC networked using static IP with a DNS server elsewhere on
the network.
Upgraded it to Windows Server 2003.
Symptom
- setting Network TCP/IP properties on the Adapter(NIC1394) goes ahead OK.
- using netsh command (in desparation) comes back with OK and the above is
altered.
But in both cases
- IPConfg /All just says
"Windows IP COnfiguration"
- cannot ping myself

I have NOT installed DNS Server on this PC yet

[richard@rrcomputerconsulting.com]

On Dec 4, 9:30 am, Ian Fry <Ian...@discussions.microsoft.com> wrote:
> I have had the PC networked using static IP with a DNS server elsewhere on
> the network.
> Upgraded it to Windows Server 2003.
> Symptom
> - setting Network TCP/IP properties on the Adapter(NIC1394) goes ahead OK.
> - using netsh command (in desparation) comes back with OK and the above is
> altered.
> But in both cases
> - IPConfg /All just says
> "Windows IP COnfiguration"
> - cannot ping myself
>
> I have NOT installed DNS Server on this PC yet

Is the 1394 NIC actually the firewire port on the PC? Do you have any
other actual NICs installed?

[Ian Fry]

Thanks Richard.
I will investigate 'firewire' ports.
There is only one adapter on the PC.

"richard@rrcomputerconsulting.com" wrote:

> On Dec 4, 9:30 am, Ian Fry <Ian...@discussions.microsoft.com> wrote:
> > I have had the PC networked using static IP with a DNS server elsewhere on
> > the network.
> > Upgraded it to Windows Server 2003.
> > Symptom
> > - setting Network TCP/IP properties on the Adapter(NIC1394) goes ahead OK.
> > - using netsh command (in desparation) comes back with OK and the above is
> > altered.
> > But in both cases
> > - IPConfg /All just says
> > "Windows IP COnfiguration"
> > - cannot ping myself
> >
> > I have NOT installed DNS Server on this PC yet
>
> Is the 1394 NIC actually the firewire port on the PC? Do you have any
> other actual NICs installed?
>
>

[Lanwench [MVP - Exchange]]

Ian Fry <IanFry@discussions.microsoft.com> wrote:
> I have had the PC networked using static IP with a DNS server
> elsewhere on the network.
> Upgraded it to Windows Server 2003.
> Symptom
> - setting Network TCP/IP properties on the Adapter(NIC1394) goes
> ahead OK.
> - using netsh command (in desparation) comes back with OK and the
> above is altered.
> But in both cases
> - IPConfg /All just says
> "Windows IP COnfiguration"
> - cannot ping myself
>
> I have NOT installed DNS Server on this PC yet

What did you upgrade from?
Check out device manager....I suspect you need a W2003 NIC driver. 1394
would be firewire, not your ethernet adapter.

[dennyd]

Look for the Yellow question mark on the Device manager.

Ian Fry <IanFry@discussions.microsoft.com> wrote:
> I have had the PC networked using static IP with a DNS server
> elsewhere on the network.
> Upgraded it to Windows Server 2003.
> Symptom
> - setting Network TCP/IP properties on the Adapter(NIC1394) goes
> ahead OK.
> - using netsh command (in desparation) comes back with OK and the
> above is altered.
> But in both cases
> - IPConfg /All just says
> "Windows IP COnfiguration"
> - cannot ping myself
>
> I have NOT installed DNS Server on this PC yet

What did you upgrade from?
Check out device manager....I suspect you need a W2003 NIC driver. 1394
would be firewire, not your ethernet adapter.