MysticMaven
Contributor
Contributor

Any way to set which network connection Fusion uses?

Jump to solution

I have Fusion on a MacMini. The primary network is airport connected to a DSL router. The secondary is the ethernet connected to an activedirectory network.

I am trying to join the domain, but VMWare says it can't see it. I assume it's because it's trying to use the airport connection.

Is there a way to make it use the ethernet connection instead?

0 Kudos
1 Solution

Accepted Solutions
Harliv
Hot Shot
Hot Shot

Are the WINS servers configured properly?

You mentioned the ip addresses are working. Are you able to ping the domain controller?

View solution in original post

0 Kudos
7 Replies
bgertzfield
Commander
Commander

There isn't a user interface for this, but you can edit the file "/Library/Application Support/VMware Fusion/boot.sh". Look at the lines:

  1. Bridge to host network interface 'en0'.

#"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 en0

  1. Bridge to the primary host network interface (which can change over time).

"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 ''

and uncomment the second line (your ethernet is probably already en0).

MysticMaven
Contributor
Contributor

I tried uncommenting the line. However, I am still unable to join the domain.

Here is what is currently happening. I can see the network using ip addresses, but not using DNS names. I have put in the correct DNS servers and can ping them fine.

I don't know if this is a VMWare issue, or just windows, but I've never seen it before. Any other suggestions?

Message was edited by:

MysticMaven

0 Kudos
Harliv
Hot Shot
Hot Shot

Are the WINS servers configured properly?

You mentioned the ip addresses are working. Are you able to ping the domain controller?

View solution in original post

0 Kudos
MysticMaven
Contributor
Contributor

Yes. I can ping the ip of the domain controller, but not the dns name of it.

EDIT: It was WINS. Thank you both for you help.

Message was edited by:

MysticMaven

0 Kudos
Harliv
Hot Shot
Hot Shot

Any time. I am glad we could help.

0 Kudos
PhilipJ
Contributor
Contributor

Hello I tried this and It did not work. I had to boot into safe mode and copy the backup file of boot.sh I had made back to the /Library/Application Support/VMware Fusion folder then I was able to boot regular. Any idea's? OSX 10.4.10 (MacBook Pro), vmware version 1.0, also upgraded to beta 1.1 and same thing. Edited file looked like this. I am trying to get fusion to use wireless, en1 and everything else en0. Any help appreciated. UPDATE: I also tried with last line commented out, same thing.

  1. vmnet-bridge puts itself in background (daemon mode)

  1. Bridge to host network interface 'en0'.

"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 en1

  1. Bridge to the primary host network interface (which can change over time).

"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 ''

;;

0 Kudos
rcardona2k
Immortal
Immortal

What exactly did you try and not work? Are you trying to join a domain like the original poster? You might want to open your own message thread describe exactly what is not working for you.

0 Kudos