Need to set static ip for bridged ethernet

C

ConnieMM

Bit poster
Hi,

I'm running a access-based db and I'm running it on parallels 5/windows xp (home edition) installed on a mac mini (snow leopard). Previously this db was on a dedicated windows machine and I and my colleagues would access it using windows remote desktop (we did that from our parallels environment on our macs to the old dedicated server). The old server had a static ip address and we could access that machine from within the network (using that static ip) and from the internet, using the public facing ip address that we've port mapped through our router.

Now that we've added a layer between windows running this db (i.e. the mac mini it runs on) I need to set up a static ip address for the VM -- as I understand it, I should do this in Bridged mode, and we have it set up that way but I cannot find a way to set a static ip address for the VM. If I go to network places and right click on the parallels ethernet adapter connection that shows up, I can get to the tcp/ip window but when I try to type something in there for fixed ip, it won't let me. Just stays blank. So I'm assuming that is the wrong place. Just feel like I'm missing something obvious but windows is so not my forte.

If we didn't have a remote user, we could probably just solve this by turning on file sharing within the network, but we do have the remote user.

If there is a better/easier way to do this, I'm all ears. Otherwise, I think if we can assign a fixed ip to the VM, this all should work as it did before.

Thanks,
Connie
 
That should be the right spot. Did you switch from "Obtain Ip address automatically" to "Use the following IP address"? You can't set a fixed IP unless you do (otherwise you're using DHCP).

Steve
 
Hi, it is a Windows-related question (not a parallels-one), but post a screenshot where Windows doesn't let you to enter the IP
 
Yes I did switch to manual. I will take a screen shot as you suggest but I can't do it till Monday. Just as an aside I think the other missing piece here is that we don't have the remote access settings turned on in windows. Duh. But I didn't set up the old dedicated server so this set up is all new territory for me and as I said I'm quite remedial with windows. But I still think we'll need a fixed ip to connect so I do have to solve that. The only other wrinkle I will note is this is xp home (we will have to upgrade to pro for remote to work) but I can't imagine using home version would prevent being able to enter a fixed ip address.

But at least I know I was in the right place and that's a big help!

Connie
 
You must log in or register to reply here.
Back
Top