Windows randomly disconnects

N

neen

Bit poster
Hi there,

I'm using Windows XP Pro on Parallels, with a 2wire router from AT&T, and for some reason I lose my internet connection (but not my network connection) frequently. I have to restart and disable/enable the network connection repeatedly to get it to work. Does anyone have any idea what's causing this?

I forgot to mention - when I first boot up the VM, I have internet. Most of the time, though, it will disconnect me shortly after, and I have to struggle to get it to connect again.
 
Last edited:
ipconfig /all:

C:\Documents and Settings\VirtualXP>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : VIRTUALXP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Parallels Network Adapter
Physical Address. . . . . . . . . : 00-1A-7C-D2-AF-D8
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.76
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : Wednesday, December 31, 2008 2:26:19 PM
Lease Expires . . . . . . . . . . : Thursday, January 01, 2009 2:26:19 PM
Click to expand...

ifconfig -a:

neens-mac-pro:~ neen$ ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fd42:786a:2651:7cd4:217:f2ff:fe0a:d57e prefixlen 128
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:17:f2:0a:d5:7e
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>
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:17:f2:0a:d5:7f
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>
en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::219:e3ff:fede:f095%en2 prefixlen 64 scopeid 0x6
inet 192.168.1.101 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:19:e3:de:f0:95
media: autoselect status: active
supported media: autoselect
fw0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2030
lladdr 00:1b:63:ff:fe:69:86:36
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
en4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::21c:42ff:fe00:1%en4 prefixlen 64 scopeid 0x8
inet 169.254.167.59 netmask 0xffff0000 broadcast 169.254.255.255
ether 00:1c:42:00:00:01
media: autoselect status: active
supported media: autoselect
en3: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::21c:42ff:fe00:0%en3 prefixlen 64 scopeid 0x9
inet 169.254.167.59 netmask 0xffff0000 broadcast 169.254.255.255
ether 00:1c:42:00:00:00
media: autoselect status: active
supported media: autoselect
Click to expand...
 
From the first look, I guess, that you are using Bridged Ethernet network settings for VM, if this is true, settings are correct, but even so, it looks that Parallels Network interfaces are still down
(APIPA range for IP addresses - 169.254.x.x)
Please clarify what are settings for Virtual machine, and what is Parallels Desktop version 3 or 4?
 
I have Parallels Desktop 3.0 build 5608.

My network setting is set to bridged ethernet. Is there anything else you need?
 
It looks that router settings doesn't allow the same IP, from the same network interface,
Please try following
1. Make sure that Parallels Interfaces are on in System Preferences -Network and set to obtain IP by DHCP
2. In Parallels Desktop - Preferences- Network make sure that DHCP scope is checked
3. Switch to Shared Network

Some more background.
When you set mode to bridged , Parallels Desktop creates new virtual interface on real interface, but some wifi routers detects that packets are coming from interface with the same MAC address, and if security settings are set to disable such behavior , there will be no Internet access,
 
Thanks John,

I figured it was something along those lines, as my previous router didn't have a problem.

When I set it to shared networking, I still seem to have issues getting the connection to work. I get a message telling me I have limited or no connectivity.
 
Yes, it is I mentioned that Parallels Interfaces are down
Try to restart Mac OS, and run ifconfig -a again, there should be no APIPA addresses in list
APIPA is in range (169.254.x.x)
 
Hi there John,

I have restarted, and now ifconfig -a shows this:
neens-mac-pro:~ neen$ ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fd19:7a8d:40ff:4dfb:217:f2ff:fe0a:d57e prefixlen 128
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:17:f2:0a:d5:7e
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>
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:17:f2:0a:d5:7f
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>
en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::219:e3ff:fede:f095%en2 prefixlen 64 scopeid 0x6
inet 192.168.1.101 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:19:e3:de:f0:95
media: autoselect status: active
supported media: autoselect
fw0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2030
lladdr 00:1b:63:ff:fe:69:86:36
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
en4: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::21c:42ff:fe00:1%en4 prefixlen 64 scopeid 0x8
inet 10.211.55.2 netmask 0xffffff00 broadcast 10.211.55.255
ether 00:1c:42:00:00:01
media: autoselect status: active
supported media: autoselect
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::21c:42ff:fe00:0%en3 prefixlen 64 scopeid 0x9
inet 10.37.129.2 netmask 0xffffff00 broadcast 10.37.129.255
ether 00:1c:42:00:00:00
media: autoselect status: active
supported media: autoselect
Click to expand...
 
With this settings it should work for now,
When you lost Internet connection, please check again ifconfig -a
if it is showing 169.xxx for Parallels Interfaces, it means that device drivers shut down Parallels Interfaces
 
You must log in or register to reply here.
Back
Top