Parallels Forums
> Archives > Parallels Desktop for Mac  
beta 6 networking problem  
  

beta 6 networking problem

Apr 29, 2006, 10:22 PM
#1  

johnnykrisma
Junior Member


Join: Apr 2006
Posts: 12		 beta 6 networking problem
Hey guys, just loaded in beta 6 and now I got no networking. I restarted VM a couple times, reinstalled my network adapter. Tried default as well as my wireless (which is the active one). Now just restarted the VM and now PW is locked up.

machine is MBP 2GHz/2GB ram, VM running W2K assigned 512 MB RAM.

Thanks

__________________
MacBook Pro 2.0GHz/2GB RAM
Windows XP on BootCamp Partition in VM
Apr 29, 2006, 10:27 PM
#2  

mcg
Senior Member


Join: Apr 2006
Posts: 168		 Yeah, something is up. When I go to the System Preferences > Network > Network Status, I see two adaptors when I think I should see just one: "Ethernet Adaptor (en2)" and "Parallels Host-Guest Adapter."

Ethernet Adaptor en2 says, "The cable for Ethernet Adaptor (en2) is connected, but your computer does not have an IP address and cannot connect to the Internet." The other one says something similar. Renewing the DHCP lease has no effect.

Furthermore, in System Preferences > Sharing > Internet, I can see "Ethernet Adaptor (en2)" in the list titled "To computers using:", but not Parallels Host-Guest adaptor. In the drop-down list "Share your connection from:", I see both.
Apr 29, 2006, 10:29 PM
#3  

jwhitney
Junior Member


Join: Apr 2006
Posts: 6		 same thing here
MacBook Pro, no problems with networking until beta 6.
Apr 29, 2006, 10:34 PM
#4  

donsullivan
Junior Member


Join: Apr 2006
Posts: 20		 Add me to the list on this one. I've had to reset the VM half a dozen times in the last few minutes. One thing I noted was if I turned off DHCP and entered a static IP address I was able to get it to work. I've swapped back and forth a few times and the pattern is pretty consistent. With DHCP active, the machine does not acquire an IP address.

i know my DHCP server is working since a Renewal request under OSX works just fine.

In my case I'm running on a MacBook Pro 2Ghz, WinXP, 768MB RAM allocated. I'm using wireless to communicate.
Apr 29, 2006, 10:30 PM
#5  

Scott Willsey
Senior Member


Join: Apr 2006
Posts: 174		 I'm hosed. I can't get networking to work any more. Same thing - can't get an IP. Still using bridged ethernet set to en1 - just like it was in all previous betas. No workee.
Apr 29, 2006, 10:31 PM
#6  

mcg
Senior Member


Join: Apr 2006
Posts: 168		 Looks we have a dreaded case of beta rot! :( Well, this happens sometimes. Hopefully they'll get a Beta 6.1 turned around in short order. Heaven knows I've done this kind of thing to my beta testers in the past.
Apr 29, 2006, 10:36 PM
#7  

Nathen
Junior Member


Join: Apr 2006
Posts: 1		 the problem only seems to affecting the virtual maching picking up an IP address via DHCP, if I set a static address I'm able to ping the rest of the network/internet without issue.
Apr 29, 2006, 10:36 PM
#8  

niccas
Junior Member


Join: Apr 2006
Posts: 11		 Ditto, no network here :-(
Apr 29, 2006, 10:38 PM
#9  

johnsail
Junior Member


Join: Apr 2006
Posts: 1		 Same here...
Installed Beta 5 and everthing was awesome...
Upgraded to Beta 6 and .... no wireless networking. I tried reverting to the previous networking adapter in the parallels tools, restarted a couple of times, tried Windoze networking Wizards... (how can anyone really enjoy using Windoze?) and still nothing.

hoping for Beta 7 soon.
Apr 29, 2006, 10:40 PM
#10  

Kypt
Junior Member


Join: Apr 2006
Posts: 8		 Can vouch for this as well, can't get networking to work :(
Apr 29, 2006, 10:44 PM
#11  

dbourne
Junior Member


Join: Apr 2006
Posts: 18		 MBP 1.8 Wireless ethernet

It didn't work at first.

Looked in My Network Places and found local network.

Then opened Parallels Tool Center, disabled, re enabled Network Driver, applied and now my browser sees the outside world.
Apr 29, 2006, 10:53 PM
#12  

mdrevs
Junior Member


Join: Apr 2006
Posts: 4		 I'm running an iMac 20" on Beta 6 and both wired and wireless work fine in XP. I also have the Parallels Guest-Host adapter. Only problem I have is with the lack of USB 2.0 and some of my USB devices don't work and cause BSOD, but I expect the will be fixed over the next few releases.
Apr 29, 2006, 11:12 PM
#13  

burgeke
Junior Member


Join: Apr 2006
Posts: 29		 Same here...
Apr 30, 2006, 12:04 AM
#14  

daveef
Junior Member


Join: Apr 2006
Posts: 24		 same here worked great in beta 5, just no usb, in 6 no networking with my wireless. so cant get any of my programs loaded to test. Since i had not networking ,had brilliant idea of trashing all parallel stuff and reinstalling parallel and window XP. think how great i felt 2 hours later with still no networking. i will wait for 7. man wish i still had 5 , next time only loading on program in to test, lmao
Apr 30, 2006, 12:05 AM
#15  

mike3k
Member


Join: Apr 2006
Posts: 65		 Same here. Networking is seriously screwed up in beta 6. I've never had any problems with networking in previous betas. Of all the betas, 5 was the best. 6 is definitely a step backward.

If it helps, here's the output of ifconfig:
Code:
[mike: mike]$ ifconfig -a
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=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 00:16:cb:89:5a:03 
        media: autoselect status: inactive
        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
        inet 192.168.0.104 netmask 0xffffff00 broadcast 192.168.0.255
        ether 00:16:cb:04:f3:8c 
        media: autoselect status: active
        supported media: autoselect
wlt1: flags=41<UP,RUNNING> mtu 1500
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::201:23ff:fe45:6789%en2 prefixlen 64 scopeid 0x7 
        inet 10.37.129.2 netmask 0xffffff00 broadcast 10.37.129.255
        ether 00:01:23:45:67:89 
        media: autoselect status: active
        supported media: autoselect
fw0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 494
        lladdr 00:16:cb:ff:fe:55:71:40 
        media: autoselect <full-duplex> status: inactive
        supported media: autoselect <full-duplex>
Apr 29, 2006, 10:37 PM
#16  

peterwor
Senior Member


Join: Apr 2006
Posts: 142		 I also have absolutely NO networking capability anymore after loading Beta6. I changed nothing and was using en1:Airport Adapter on my MBP.

its HOSED!!!! Come on Parallels, the last 2 betas have been going downhill, I undertand that you've been adding lots of new features but also breaking old ones, not good QC process.

Peter
Apr 29, 2006, 10:42 PM
#17  

johnnykrisma
Junior Member


Join: Apr 2006
Posts: 12		 C'mon now Peterwor, it's *beta* software. Sometimes it gets worse before it gets better. I think you are being a little too hard of them. How many other companies are releasing betas to software on a saturday night?

__________________
MacBook Pro 2.0GHz/2GB RAM
Windows XP on BootCamp Partition in VM
Apr 29, 2006, 10:46 PM
#18  

jsolderitsch
Member


Join: Apr 2006
Posts: 54		 I also find networking problematic now (beta 6). The first time I tried beta 6 I had not yet updated the new Parallels Tools and I had NO PROBLEM with networking using bridged networking to my wireless connection. Actually, my bridged setting was to the DEFAULT ADAPTOR rather than en1.

But, I then updated to the Parallels Tools for beta 6 and I lost bridged networking. I tried going back to the default network driver and it did not help.

So I plugged in my ethernet cable and bridged to en0. That worked! Then I switched back to bridging to the Default Adaptor and networking still worked with the network cable plugged in.

I have not yet re-tried en1 or unplugged the ethernet cable to see if wireless might come back.

Clearly a beta regression for bridged networking.
Apr 30, 2006, 01:49 AM
#19  

tomm
Junior Member


Join: Apr 2006
Posts: 10		 networking hosed in beta 6
Just like many of others, my Parallels PeeCee XP-pro netwoking does not work anymore in this new beta 6.

I hapilly installed beta 6, it asked me to reboot my MacBook Pro and when I launched the new beta6, I could not connect to the Internet. I am using the same setup as before, which is en1 = airport on my MBP. I noticed it was now set to default in Network adaptor, so I changed it to en1, but that did not help. In fact, I tried all the options and none of them worked. Host -only netwrorking did not work either. So I can't go online in Windoze now. It worked well in all the other betas.

Just like others, I see Ethernet Adaptor (en2) and Parallels Host-Guest Adaptor in addition to the Airport.

You Parallels guys have really messed up this one in your Parallel universe. This thing should not have been released.

What do we do to fix it?

By the way, my license will expire in 5 days. Is it going to be renewed somehow and how?

thanks
Apr 30, 2006, 02:06 AM
#20  

netdog
Senior Member


Join: Apr 2006
Posts: 117		 Add me to the list. Newest tools installed. Network adapter disabled, then enabled again. Nothing gets it going. It seems like a fix in the network tools might be the route for you guys to get this going again.
 
« Previous Thread | Next Thread »


1 | 2 |  >

Search this thread Forum jump
 
Advanced Search
Thread tools Display modes
Printable Version
Linear Mode
Hybrid Mode
Threaded Mode

Powered by vBulletin
Copyright © 2000 - 2009, Jelsoft Enterprises Ltd.