virtualbox.org

I am currently trying to set up & use VirtualBox on my WindowsXP company laptop. As part of my work requirements, I have to use AT&T Network Client (version 6.9.0.3006) to connect to my corporate network. Unfortunately, if I have installed VirtualBox, it doesn't work.

It doesn't matter whether VirtualBox is running or not. If I open the detailed messages window for AT&T Client, it says that it cannot connect to the DNS server. I tried rebooting after installing, but it doesn't help.

Even if I shut down VirtualBox, I still cannot connect to the company network. I have to completely uninstall it, and reboot my laptop.

Since, as part of the installation process, it temporarily stops all networking processes, I'm assuming that it hijacks something, and doesn't let it go. As I'm typing this, it occurs to me that perhaps I should have looked at the Services, to see if there was something there I could just turn off.

However, even if it is something like turning a service off, I would still like to be able to open up a virtual server while connected to my corporate network.

Is there something I can tweak that will let me do this?

Thansk in advance for any help you can give me.

Bill

Before people start telling me how to run AT&T Network Client *within* VirtualBox, I should point out that it is the VPN tunnel on the host server (my laptop itself) that is not working.

After you install VB, reinstall the AT&T client. It's been discussed here on the forums before that there are issues with that software. A reinstall usually helps.

I appreciate the help. Unfortunately, it did not work for me.

I get AT&T Network Client from my employer by way of one of these automated installer intranet sites. It creates two directories under Program Files: "AT&T Network Client" and "AT&T Network Client Install". The 2nd of those has an installer file in it named ncsetup690.exe. I've used this to install on my personal computer once in an emergency. I tried using it to re-install on my company laptop after installing VirtualBox. It did not seem to make any difference at all.

It's possible that if I completely uninstall AT&T Net Client first, then install VirtualBox, then reinstall AT&T, it might work. Unfortunately, I work from home, and if the reinstall of AT&T didn't work I would have to drive in to the office (45 minutes one-way) to be able to reinstall from the company's intranet site. (Without AT&T I can't get to the site, but from the office I'm on their network and don't need it).

I'll keep this option in my back pocket, and try it again next time I need to go to the office (which only happens every 3 or 4 months).

Again, thanks for the assistance.

Bill

Get that stuff on a stick and have them mail it to you, its just a 'file'.

From that AT&T Net Client site, it looks like the trick is:

1.) Right-Click on "My Network Places"
2.) Select "Properties"

This opens the "Network Connections" window.

3.) Right-Click on "AGN Virtual Network Adapter"
4.) Select "Properties"

This opens the "AGN Virtual Network Adapter Properties" window.

5.) Select the "General" tab. (Probably already selected.)

6.) Uncheck the box next to "VirtualBox Bridged Networking Driver" in the "This connection uses the following items:" box.
7.) Click OK.

After this, things should work just fine.


Unfortunately, I only found this fix after spending HOURS uninstalling and reinstalling trying to get this to work, and after coming in to work unnecessarily to try and fix it.

Hope this helps anyone with a similar problem.

Okay, I'm really confused now. I had put in some concerted effort trying to get this working, and always ran into the DNS issue. It was a known bug, reported in this forum multiple times, with (if I remember correctly) the only workaround being to reinstall AT&T client. Since this would kill my connection to the server that I would be installing it from, that was not an option without going to the office (which I try not to do unless necessary. I love working from home.) So, I posted my query here and promptly forgot about it.

When I got the most recent post, I was overjoyed. I happen to be ending up a couple of weeks of having to work from the office, so this would be the perfect time to play with it again. Before going through anything I wanted to see the error message again, since it has been a while since I tried it last time. So, I reinstalled Virtual Box, and fired up AT&T. Gues what happened?

IT WORKED!!!

I know I haven't done anything with VB since my last post, and unless I got an upgrade pushed form my home office without my knowledge, I didn't think AT&T had changed either. I have no idea why it works now. But it does, so I am happy.

For what it's worth though, I don't have "VirtualBox Bridged Networking Driver" in the "This connection uses the following items:" box. All I have is:
Client for Microsoft Networks
AGN Filter Interface
File and Printer Sharing for Microsoft Networks
AT&T Wi-Fi Support Driver
IBM Personal Communications LLC2 Driver
Internet Protocol (TCP/IP)
Perhaps something else I got pushed to me removed it, and that's why it works now.

Thanks for looking at this for me, to everyone who looked, whether you replied to the post or not.

BDixon wrote:Okay, I'm really confused now. I had put in some concerted effort trying to get this working, and always ran into the DNS issue. It was a known bug, reported in this forum multiple times, with (if I remember correctly) the only workaround being to reinstall AT&T client. Since this would kill my connection to the server that I would be installing it from, that was not an option without going to the office (which I try not to do unless necessary. I love working from home.) So, I posted my query here and promptly forgot about it.

When I got the most recent post, I was overjoyed. I happen to be ending up a couple of weeks of having to work from the office, so this would be the perfect time to play with it again. Before going through anything I wanted to see the error message again, since it has been a while since I tried it last time. So, I reinstalled Virtual Box, and fired up AT&T. Gues what happened?

IT WORKED!!!

I know I haven't done anything with VB since my last post, and unless I got an upgrade pushed form my home office without my knowledge, I didn't think AT&T had changed either. I have no idea why it works now. But it does, so I am happy.

For what it's worth though, I don't have "VirtualBox Bridged Networking Driver" in the "This connection uses the following items:" box. All I have is:
Client for Microsoft Networks
AGN Filter Interface
File and Printer Sharing for Microsoft Networks
AT&T Wi-Fi Support Driver
IBM Personal Communications LLC2 Driver
Internet Protocol (TCP/IP)
Perhaps something else I got pushed to me removed it, and that's why it works now.

Thanks for looking at this for me, to everyone who looked, whether you replied to the post or not.

oh , the same as mine...