W2K3 install on Rx8620 : "SAC could not set the IP Address"

G

Guest

Guest
Archived from groups: comp.sys.hp.apps,comp.sys.hp.hardware,comp.sys.misc,comp.sys.hp.mpe,comp.sys.hp.hpux (More info?)

I found on HP website the document : "Configuring Microsoft® Windows® Server
2003 on the HP Integrity Server, Enterprise Edition" ( c00090141.pdf ) ...

I installed W2K3 trought lan - MP, and when it's installed, i try to set the
ip address with SAC, i've
the message :"SAC could not set the IP Address."...
"
SAC>I
Net: 2, Ip=0.0.0.0 Subnet=0.0.0.0 Gateway=0.0.0.0
SAC>I 2 10.100.13.136 255.255.254.0 10.100.13.253
SAC could not set the IP Address.
SAC>i 0 10.100.13.136 255.255.255.0 10.100.13.253
SAC could not clear the existing IP Address.
SAC>i 1 10.100.13.136 255.255.255.0 10.100.13.253
SAC could not retrieve the IP Address.
SAC>
"
----------------------------------------------------------
and from CMD :
"
C:\WINDOWS\system32>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
C:\WINDOWS\system32>ipconfig /renew #to see if it can reach the DHCP
server...
Windows IP Configuration
No operation can be performed on Local Area Connection while it has its
media disconnected.
C:\WINDOWS\system32>route print
IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 XX 6e XX 9a XX ...... Broadcom NetXtreme Gigabit Ethernet
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
255.255.255.255 255.255.255.255 255.255.255.255 10003 1
===========================================================================
Persistent Routes:
None
C:\WINDOWS\system32>
"
----------------------------------------------------------
Driver Broadcom NetXtreme Gigabit Ethernet found... OK Mac add. - Cable is
connected!!! This is operational with HP-UX OS.
----------------------------------------------------------
I'll try a new installation, but i'm afraid to have the same msg...

Does anyone have an idea?


Sincerely,

Jérôme

Belgium
 
G

Guest

Guest
Archived from groups: comp.sys.hp.apps,comp.sys.hp.hardware,comp.sys.misc,comp.sys.hp.mpe,comp.sys.hp.hpux (More info?)

On Mon, 31 Jan 2005 19:15:19 +0100, "DJe" <no.spam@thx.net> wrote:

>I found on HP website the document : "Configuring Microsoft® Windows® Server
>2003 on the HP Integrity Server, Enterprise Edition" ( c00090141.pdf ) ...
>
>I installed W2K3 trought lan - MP, and when it's installed, i try to set the
>ip address with SAC, i've
>the message :"SAC could not set the IP Address."...
>"
>SAC>I
>Net: 2, Ip=0.0.0.0 Subnet=0.0.0.0 Gateway=0.0.0.0
>SAC>I 2 10.100.13.136 255.255.254.0 10.100.13.253
>SAC could not set the IP Address.
>SAC>i 0 10.100.13.136 255.255.255.0 10.100.13.253
>SAC could not clear the existing IP Address.
>SAC>i 1 10.100.13.136 255.255.255.0 10.100.13.253
>SAC could not retrieve the IP Address.
>SAC>
>"
>----------------------------------------------------------
>and from CMD :
>"
>C:\WINDOWS\system32>ipconfig
>Windows IP Configuration
>Ethernet adapter Local Area Connection:
> Media State . . . . . . . . . . . : Media disconnected

You need to have the Ethernet adapter plugged into an active hub or
switch. If your site supports DHCP, then you should see a DHCP address
on "Net: 2", otherwise you will see a '169' address on "Net: 2". You
can now use the "I" command on the SAC to set the IP address.

Remember, this IP address is only temporary. You will need to RDP into
the system and permanently set it.
 
G

Guest

Guest
Archived from groups: comp.sys.hp.apps,comp.sys.hp.hardware,comp.sys.misc,comp.sys.hp.mpe,comp.sys.hp.hpux (More info?)

I opened an HP Case for my problem...
Because the network is plugged , we have a DHCP srv., and the driver is
found :

C:\WINDOWS\system32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : your-0ihdmmwz2s
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-XX-6E-XX-9A-XX

--------------------------------------------------
"Broadcom NetXtreme Gigabit Ethernet" mean W2K3 found the driver, right?

Sincerely,

Jérôme
Belgium


"Robert Klute" <robert_klute_removethis@hp.com> wrote in message
news:v8etv0lr74otpa37pa5cviscrrd76vkfsk@4ax.com...
> On Mon, 31 Jan 2005 19:15:19 +0100, "DJe" <no.spam@thx.net> wrote:
>
>>I found on HP website the document : "Configuring Microsoft® Windows®
>>Server
>>2003 on the HP Integrity Server, Enterprise Edition" ( c00090141.pdf ) ...
>>
>>I installed W2K3 trought lan - MP, and when it's installed, i try to set
>>the
>>ip address with SAC, i've
>>the message :"SAC could not set the IP Address."...
>>"
>>SAC>I
>>Net: 2, Ip=0.0.0.0 Subnet=0.0.0.0 Gateway=0.0.0.0
>>SAC>I 2 10.100.13.136 255.255.254.0 10.100.13.253
>>SAC could not set the IP Address.
>>SAC>i 0 10.100.13.136 255.255.255.0 10.100.13.253
>>SAC could not clear the existing IP Address.
>>SAC>i 1 10.100.13.136 255.255.255.0 10.100.13.253
>>SAC could not retrieve the IP Address.
>>SAC>
>>"
>>----------------------------------------------------------
>>and from CMD :
>>"
>>C:\WINDOWS\system32>ipconfig
>>Windows IP Configuration
>>Ethernet adapter Local Area Connection:
>> Media State . . . . . . . . . . . : Media disconnected
>
> You need to have the Ethernet adapter plugged into an active hub or
> switch. If your site supports DHCP, then you should see a DHCP address
> on "Net: 2", otherwise you will see a '169' address on "Net: 2". You
> can now use the "I" command on the SAC to set the IP address.
>
> Remember, this IP address is only temporary. You will need to RDP into
> the system and permanently set it.
 
G

Guest

Guest
Archived from groups: comp.sys.hp.apps,comp.sys.hp.hardware,comp.sys.misc,comp.sys.hp.mpe,comp.sys.hp.hpux (More info?)

On Wed, 2 Feb 2005 16:00:19 +0100, "DJe" <no.spam@thx.net> wrote:

>I opened an HP Case for my problem...
>Because the network is plugged , we have a DHCP srv., and the driver is
>found :
>
>C:\WINDOWS\system32>ipconfig /all
>Windows IP Configuration
> Host Name . . . . . . . . . . . . : your-0ihdmmwz2s
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Broadcast
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>Ethernet adapter Local Area Connection:
> Media State . . . . . . . . . . . : Media disconnected
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
> Physical Address. . . . . . . . . : 00-XX-6E-XX-9A-XX
>
>--------------------------------------------------
>"Broadcom NetXtreme Gigabit Ethernet" mean W2K3 found the driver, right?

Yes, it does recognize the device. How many LAN connections do you
have? I sometimes find that it helps to temporarily plug in all the LAN
connections to the network when it first comes up as I am occasionally
suprised with the LAN number ordering that Windows does.

Remember Windows should see the core system LAN connections, but will
not 'see' the MP LAN connections.


Robert Klute
Americas Solution Center, Cupertino
Hewlett-Packard Company
-----
The opinions are those of the poster, not the company.
 
G

Guest

Guest
Archived from groups: comp.sys.hp.apps,comp.sys.hp.hardware,comp.sys.misc,comp.sys.hp.mpe,comp.sys.hp.hpux (More info?)

DJe wrote:

> "Broadcom NetXtreme Gigabit Ethernet" mean W2K3 found the driver, right?

Not quite. This only means that W2K3 found some sort of device-id and/or
device-class, probably with the PCI vendor/device/subsystem/function IDs.

It also found a INF file that seemed to know about this device-id, and
installed the driver with the information of the INF file.

It's possible that the driver in the Windows 2003 _seem_ to work, from
the viewpoint of the OS, and parts of the device do actually work, and
signal the appropriate messages to the driver, but not necessarily the
whole of the device does work.

I remember something with NT4 server and an Intel Pro100B network card.

Try installing the newest driver for the device. Download it from the
Broadcom site.

But before we are going off in the wrong direction: do the
link-status-leds on the network card and/or the hub/switch indicate a
working link? Maybe you are using crossover cables instead of straight
(computer to switch), or straight instead of crossover (computer to
computer).

--
Alex
 
G

Guest

Guest
Archived from groups: comp.sys.hp.apps,comp.sys.hp.hardware,comp.sys.misc,comp.sys.hp.mpe,comp.sys.hp.hpux (More info?)

Alex van Denzel wrote:

> DJe wrote:
>
>> "Broadcom NetXtreme Gigabit Ethernet" mean W2K3 found the driver, right?
>
>
> Not quite. This only means that W2K3 found some sort of device-id and/or
> device-class, probably with the PCI vendor/device/subsystem/function IDs.
>
> It also found a INF file that seemed to know about this device-id, and
> installed the driver with the information of the INF file.
>
> It's possible that the driver in the Windows 2003 _seem_ to work, from
> the viewpoint of the OS, and parts of the device do actually work, and
> signal the appropriate messages to the driver, but not necessarily the
> whole of the device does work.
>
> I remember something with NT4 server and an Intel Pro100B network card.
>
> Try installing the newest driver for the device. Download it from the
> Broadcom site.
>
> But before we are going off in the wrong direction: do the
> link-status-leds on the network card and/or the hub/switch indicate a
> working link? Maybe you are using crossover cables instead of straight
> (computer to switch), or straight instead of crossover (computer to
> computer).
>
> --
> Alex
This is not a W2k3 newsgroup.
 
G

Guest

Guest
Archived from groups: comp.sys.hp.apps,comp.sys.hp.hardware,comp.sys.misc,comp.sys.hp.mpe,comp.sys.hp.hpux (More info?)

[Followups set to comp.sys.hp.hardware]

In comp.sys.hp.apps Alan D Johnson <adjtech@hvc.rr.com> wrote:
> This is not a W2k3 newsgroup.

No, but then, it is an HP server, so perhaps comp.sys.hp.hardware. If
all else failed, comp.sys.hp.misc.

Still, I would think that until there is a critical mass it would be
"OK" for the odd other OS on HP kit to appear somewhere in the
comp.sys.hp heirarcy. Just one person's opinion of course.

Now, upon seeing the newsgroup headers set to what appear to be the
entirety of the comp.sys.hp hierarchy and thensome... I would remind
the OP (assuming it was the OP) of the following - particularly the
follow-up to and the "appropriate" group bits:

One can specify more than one newsgroup in the Newsgroups: line. The
format would look like this:

Newsgroups: group1,group2,group3

with no spaces in the grouplist. This has several advantages (so long
as it is not abused by posting messages to inappropriate groups). Only
one copy of your message must traverse the Internet, saving network
bandwidth; only one copy of your message must be stored on each news
server on the Internet, saving many MB of space world-wide; you only
have to enter the news posting once, saving you time; people only have
to read/skip your post once, saving them time; all responses in any
group can be seen in all groups, keeping everyone up to date with the
conversation.

Also, you can add a Followup-to: header line which will direct all the
follow-ups to a particular group, making it easier for you to look for
responses.

I hope you find this helpful. If you do, please pass it along to your
peers as you see them needing the same advice.

sincerely,

rick jones
--
Wisdom Teeth are impacted, people are affected by the effects of events.
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to raj in cup.hp.com but NOT BOTH...
 
G

Guest

Guest
Archived from groups: comp.sys.hp.hardware (More info?)

Rick Jones wrote:
> [Followups set to comp.sys.hp.hardware]
>
> In comp.sys.hp.apps Alan D Johnson <adjtech@hvc.rr.com> wrote:
>
>>This is not a W2k3 newsgroup.
>
>
> No, but then, it is an HP server, so perhaps comp.sys.hp.hardware. If
> all else failed, comp.sys.hp.misc.
>
> Still, I would think that until there is a critical mass it would be
> "OK" for the odd other OS on HP kit to appear somewhere in the
> comp.sys.hp heirarcy. Just one person's opinion of course.
>
> Now, upon seeing the newsgroup headers set to what appear to be the
> entirety of the comp.sys.hp hierarchy and thensome... I would remind
> the OP (assuming it was the OP) of the following - particularly the
> follow-up to and the "appropriate" group bits:
>
> One can specify more than one newsgroup in the Newsgroups: line. The
> format would look like this:
>
> Newsgroups: group1,group2,group3
>
> with no spaces in the grouplist. This has several advantages (so long
> as it is not abused by posting messages to inappropriate groups). Only
> one copy of your message must traverse the Internet, saving network
> bandwidth; only one copy of your message must be stored on each news
> server on the Internet, saving many MB of space world-wide; you only
> have to enter the news posting once, saving you time; people only have
> to read/skip your post once, saving them time; all responses in any
> group can be seen in all groups, keeping everyone up to date with the
> conversation.
>
> Also, you can add a Followup-to: header line which will direct all the
> follow-ups to a particular group, making it easier for you to look for
> responses.
>
> I hope you find this helpful. If you do, please pass it along to your
> peers as you see them needing the same advice.
>
> sincerely,
>
> rick jones
Then silly me I realized that cross posted the reply, sigh... I only did
it after it started getting responses in this group.