Can't see internal network in Parallels

Moved from "How to"

Greetings,

I'm having a terrible problem getting Parallels to see an internal Windows network natively. There's a "tunnelling" problem. I keep getting errors, when I know I am authenticated onto the network. (can get there through Mac OSX)

This is a challenge for VPN, and for source control. Any suggestions how to get directly to the network from Parallels (ie: not through Mac OSX?)

Many thanks in advance,

--reffi

 

Bridged Networking should do the trick.

 

bridged networking?

sorry, I'm a newbie. Can you be more specific???

 

Bridging still does not do the trick

Many thanks, I figured out Bridging. But, it is still not seeing the network NATIVELY. Two things are completely blocking me from doing my work:

RUN: cannot run anything as if it was really on a windows machine
Internal networks cannot be found, ftp tunnels and cannot go directly to the network, and ips error out.

How can I run this program as if it is running windows Natively?

 

Bridged networking

What do you mean by natively? That is not a very specific term for networking. Bridged networking assigns your virtual machine a separate IP address from the network as if it was a separate computer. You should be able to use network places to navigate directly to any accessible network drives. If you can't, it is probably a windows networking or firewall problem.
If by native you mean that Windows (or whatever OS you use) is directly controlling the hardware your computer uses to connect to the network, like an express card or pc card network adapter, you should be able to control this through the Parallels Devices menu.

 

Do you have a default route and DNS/WINS configured in your VM? Having connectivity isn't enough - you still need to find things with DNS and when you use bridged networking all that has to be handled by Windows as the Mac host is no longer providing those services.

You can test the problem by using IP addresses instead of hostnames. If the remote system can be found by IP but not hostname then you have DNS resolver issues. This could lack of defined name servers, or no defined DNS prefix. If the remote system cannot be found by IP or name then you could have a default router problem or a netmask problem.