beta4 en0 still not working

MBP,1.83,1GBMem, 10.4.6

as I wrote before, beta2 worked with bridged-networking on en0, beta3 and 4 don't. en1 was NEVER a problem for me.

on XP

ipconfig /all

Windows-IP-Konfiguration

Hostname. . . . . . . . . . . . . : macxp
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Unbekannt
IP-Routing aktiviert. . . . . . . : Nein
WINS-Proxy aktiviert. . . . . . . : Nein

Ethernetadapter LAN-Verbindung:

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Parallels Network Adapter
Physikalische Adresse . . . . . . : 00-03-FF-B4-74-24
DHCP aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 10.2.1.220
Subnetzmaske. . . . . . . . . . . : 255.255.240.0
Standardgateway . . . . . . . . . : 10.2.0.1
DNS-Server. . . . . . . . . . . . : 10.2.0.10
10.2.0.11

and the MBP and XP can ping each other without a problem.
I can't ping the gateway or any other computer on the network

Please, I immedeatly paid for the product as beta2 let me use en0/bridged, but now I can't work with it (and I NEED it to access some data in an exotic database!)

thanks
josef

 

Thanks for reporting - we will check this.

 

josef,

Are you sure that your network environment didn't change since you've
tried beta2? Ex. network router upgraded, security policy changed...

In beta2 there was "Wireless" checkbox below interface drop-down list.
Did you checked that checkbox for bridging to en0 to work for you?

 

> Are you sure that your network environment didn't change since you've
> tried beta2? Ex. network router upgraded, security policy changed...
no, I can't remember to have made any changes...

> In beta2 there was "Wireless" checkbox below interface drop-down list.
> Did you checked that checkbox for bridging to en0 to work for you?
hmm, don't think so (though I can't remeber exactly). I cleanly removed everything after upgrading to beta3.
What I have done now is to activate internet sharing in os x for ethernet, and give the XP the ip-address of my mac (10.2.1.110), it works this way, but the internet sharing deactivates itself every 10 minutes or so, then I have to start it again - not the most stable setup, but for short periods I manage to get networking to function...

Is there a way to download the beta2 again so I can check if that works?

thanks
josef

 

josef,

please, check your private messages.

> What I have done now is to activate internet sharing in os x for ethernet, and give the XP the
> ip-address of my mac (10.2.1.110), it works this way, but the internet sharing deactivates
> itself every 10 minutes or so, then I have to start it again - not the most stable setup, but for
> short periods I manage to get networking to function...

Hmm.. Do I read correctly that you've assigned the same IP address both to your Mac and to
XP VM? You shouldn't do that as it only makes matters worse. IP addresses must be unique
across reachable network.

Just to make things clear, would you mind posting your network configuration for the case
when you bridge to en0 and it doesn't work?
In Terminal window an your Mac issue:
ifconfig
And for XP VM, try to ping your router (I expect it to fail), and then:
arp -a

 

> Hmm.. Do I read correctly that you've assigned the same IP address both to your Mac and to
> XP VM? You shouldn't do that as it only makes matters worse. IP addresses must be unique
> across reachable network.

sorry, i meant that i give 10.2.1.110 as the gateway address, xp itself has 10.2.1.220, this of course only works when i enable internet sharing via ethernet in os x.

I now disabled and switched back to 'pure' bridged (deactivated inet sharing), here is my output:

Mac first:
ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::216:cbff:fe8c:82ff%en0 prefixlen 64 scopeid 0x4
inet 10.2.1.110 netmask 0xfffff000 broadcast 10.2.15.255
ether 00:16:cb:8c:82:ff
media: autoselect (100baseTX <full-duplex>) status: active
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:16:cb:07:95:93
media: autoselect (<unknown type>) status: inactive
supported media: autoselect
wlt1: flags=41<UP,RUNNING> mtu 1500
vi2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::201:23ff:fe45:6789%vi2 prefixlen 64 scopeid 0x7
inet 192.168.2.101 netmask 0xffffff00 broadcast 192.168.2.255
ether 00:01:23:45:67:89
media: autoselect status: active
supported media: autoselect
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 2030
lladdr 00:16:cb:ff:fe:5d:3f:3c
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>

XP:

ping fails (as you guessed),

arp -a gives:

Schnittstelle: 10.2.1.220 --- 0x2
Internetadresse Physikal. Adresse Typ
10.2.0.10 00-d0-b7-07-64-d9 dynamisch
10.2.0.11 00-d0-b7-07-65-1a dynamisch

the output from ipconfig /all is in the first post...

thanks
josef

 

hmmm, strange, arp gets the actual mac-addresses from the name-servers,
00-d0-b7-07-64-d9 and 00-d0-b7-07-65-1a
are the correct values from the nics from our dns, how comes?

josef

 

josef,

So, you did ping the router at 10.2.0.1 and "arp -a" didn't show it's address...
What kind of router do you have? What model it is? Software version, may be?
Do you know of any security feature (like MAC address filtering) that is activated
on the router?

Thanks for being with us

PS: Can you ping other hosts on your local network, say DNS at 10.2.0.10?

 

we are getting nearer...
no, I did not see the 10.2.0.1 after the ping...
yes, we use vmps so only computers with known mac-adresses can join the net. therefore the parallel-adapter got 00-03-FF-B4-74-24\0 wh™\0\0\0¬eY@¬eY@ed. but I'm blocked on the switch. our network-admin will configure it for me tomorrow, will keep you informed...
thanks for the hint
jo˜

 

bridged is working like a charm now, network admin forgot to add my MAC-address to be allowed, so therefore i could not get online

THANKS for helping
josef