Another computer question

PittSpeed Automotive PittSpeed Off Topic
1

Our new workstations (Dell w/XP 64 bit) have two network adapters: a 1394 net adapter and Broadcom Gigabit adapter (the latter is used for connecting to our network). My problem is that the Pro/E license file uses the broadcom NIC address for identifying the computer, and gets confused by the 1394 card. It must look at that card first(?) Is there some way to identify the Broadcom card as the main card?

Otherwise I have to disable the 1394 card, reread the Pro/E license file so it sees the Broadcom card, then reenable the 1394 card. Or I guess I could permanently disable the 1394 card since it isn’t being used right now.

Thanks!

2

“network binding order”

right click network places -> properties… then advanced adn advanced settings

put broadcom on the top

3

Tried and it still does it. I think it may be an issue with Pro/E and FlexLM licensing. I’m going to try to reinstall the software now that i switched the order.

4

well, if you just made the change, reinstall over and do a ‘repair’… it probably just grabs the eth0 NIC and tosses it into the .ini file (or however it works)… i have no idea what FlexLM or Pro/E is, so sorry!

what i would do is enable teh correct binding order, disable the 1394 and reinstall… then see if it’s working or not… if not, somewhere, whether in the GUI or in a config file, you HAVE to be able to tell the program what NIC priority to use…

5

If we paid for Pro/E tech support I could call them… :mad:

6

The reason for not just keeping the conflicting NIC disabled? Is there plans to EVER use it?

Seems like too easy of a solution if you are asking for alternative methods.

7

That’s what I ended up doing. You’re right, we’ll probably never use it. I’m still not sure why Sonny’s suggestion didn’t work, but I give up for now!

It’s also been an issue in the past with a laptop with a wireless card. Same solution, disable the card until it’s needed.

8

Is the license node locked or floating, and is the license manager local or remote if floating.

(remember who I work for).

9

who do you work for?

10

I’m sorry, but for some reason I pictured you saying that in the Arnold Schwarzenegger voice from Kindergarten Cop. :rofl:

11

Who is ur daddy and what does he doooooooo…

12

Floating license, local license manager.

My bigger problem now is that Workbench 11.0 (64 bit version) wants Pro/E to also be 64-bit. I can import Pro/E into version 10.0 but not 11.0. And even though we own Pro/E Wildfire 2.0, I can’t get the 64-bit version of it since we don’t have maintenance. Damn it, now there’s just one more step to importing geometry. :doh:

I’m starting to regret going 64 bit. Novell Client also doesn’t have a 64 bit version, which is what we use for our local network servers. And I get blank sheets when I print from ANSYS, which then tends to crash after printing.

Not to mention that I can’t figure out how to model a spring in Workbench (although that’s my own ignorance).

Rant over.

13

You can thank me for convincing product management to kill the 32-bit Pro/E Geometry Interface in AWP 110 x64. Sorry! :doh:

Let me talk to the FLEXlm specialist tomorrow and try to reproduce it. There is probably a problem with the adapter binding like Sonny said, but he may know more. I don’t recall hearing this problem with our FLEXlm stuff.

14

there ya go

15

Why you no good… :smiley: If you know Palamara tell him I blame him for it.

I appreciate the help!

16

Palamara laughed and said “that’s your fault!”.

Try this:

  1. re-prioritize the 1394 as secondary network adapter as previously mentioned.
  2. Disable the 1394 network adapter.
  3. “net stop” the Pro/E license manager or go to services.msc and stop it there.
  4. enable the 1394 network adapter.
  5. net start the Pro/E license manager

then, tell us if that changes the network binding.

I may have to mess with interface metrics or routing if this doesn’t work.

17

i just saw “NOVELL”

sooooo fucking out…

18

If “net stop” is the same thing as pushing the “stop server” button (??) then no, it didn’t change anything.

19

Ugh. OK, do this…slightly different order.

  1. Disable the 1394 network adapter.
  2. “net stop” the Pro/E license manager or go to services.msc and stop it there.
  3. net start the Pro/E license manager
  4. enable the 1394 network adapter.

Does it work when the process is done like that?

20

Yes, that works until i reboot the computer. But it’s almost never rebooted, and if it is i can just go in and do that procedure.