PDA

View Full Version : Dialin Question, Part 2


Tahna Los
04-17-2001, 03:27 PM
Same problem, different question:

How would you configure a computer with Win 2000 Workstation to receive an outside connection (like a server)?[nbsp][nbsp]Do I need to specify some sort of IP address?[nbsp][nbsp]Can I make one up?

In short, we've set up my boss's computer with capability to receive incoming connections.[nbsp][nbsp]So I did a test with my computer.[nbsp][nbsp]On both computers, I went into the properties, set TCP/IP properties with an address of 111.111.111.111

Didn't work.[nbsp][nbsp]What may I be doing wrong?

dank
04-17-2001, 03:47 PM
My experience with networking Win 2000 is that the most important thing is setting up a group/user/password with the desired access level and then set up any computers seeking access with that same user/computer name and password.

I don't think there's any direct need for setting the IP address, unless you are going through a hub or router or something that requires it for internal use.

Dan

Tahna Los
04-17-2001, 04:01 PM
Next Question:

How do I access the computer that I'm "logging" into?

Someone told me that if I enter the IP address in the "Run" portion of the menu, then I can automatically get into his computer and pull files and the whatnot.

Seeing that I don't think that this works via a modem connection, I have to rely on CesarFTP which one of you suggested.[nbsp][nbsp]However, I believe I need to specify the address of the computer that I'm FTPing to.[nbsp][nbsp]Hence the need to specify the IP address.

sheila
04-17-2001, 04:14 PM
Question:
What protocol are you using, to get the two computers to speak with each other over the phone line?

You DO need to use some sort of protocol.

Justin
04-17-2001, 04:40 PM
I haven't done this first hand under Windows, but basically you need to do one of two things:

1) Run DHCP on the Windows 2000 "server" box. This will automatically assign an IP address to the connecting machine from one of the "private" network blocks.

2) Set up a private network, and assign an IP to each machine.

Personally, for a small network, I recommend #2. Don't just blindly make up an address, though, use one of the private networks.

For example, set the Win2k box up with 192.168.0.1 and the connecting machine to 192.168.0.2. Netmask is 255.255.255.0.

On the connecting computer, you need to set it's "default gateway" to be the IP of the server machine.

Finally, if you haven't already, you need to set up a PPP server on the server. This is what enables you to connect (though there are other protocols, PPP is easiest to work with on the client side).

From there I recommend searching at Google or even Microsoft for assistance. I've never run a PPP server on Windows, so I can't help you there.

If you already have PPP running (I'm guessing you are, if you were already trying to access the machine via the run menu), the rest is the easy part and the above suggestions should get you going.

As far as networking -- you can access a connected Windows machine directly by typing "\\" preceding it's IP in the 'Run' window. I discovered this yesterday myself while trying to get a networked printer to work :)

Finally -- the one thing you are probably wanting to do here -- we get to file sharing.

If all of the above has worked, you are connected. In your "Network Neighborhood" or "My Network Places" (depending on OS), expand Entire Network, Microsoft Windows network, and so on until you find the other PC. If you haven't set up any shares you won't see any in there, but this will verify you can get this far.

On each machine (or just the one that has stuff the other needs to get), right-click on a folder and select "Sharing", and set up a share. It will then be available in the Network Neighborhood/Places on the other box.

Hope some of this helps. I've been playing a lot with this lately, what with two separate subnets on either side of a firewall, sharing files *through the firewall between different subnets and workgroups* (was easy - gotta show Windows who's boss ;) ), wireless networking, etc... mind you this isn't at work, their network is pathetic compared to mine :P

(as you can tell, it's way past sleepy time...)

------------------
Justin Nelson
SFE Software (http://www.sfesoftware.com)

Tahna Los
04-17-2001, 05:12 PM
Justin: All of the files involved will be stored on my boss's computer.[nbsp][nbsp]And that computer is Win2000 Professional, not the server edition.[nbsp][nbsp]The server itself does not have any external connections, and is itself not connected to the internet.

Sheila: Attempted to connect via a TCP/IP protocol.[nbsp][nbsp]Figured that would be the best solution as the Laptop and computer will soon be 5000 miles apart.
[This message has been edited by Tahna Los (edited 04-17-01@4:22 pm)]