Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BEFSR81 - Using Static IP & Dynamic

Status
Not open for further replies.

Torky

IS-IT--Management
Nov 4, 2002
3
US
I am very new to the router world, sorry. Here is what I am trying to do. 3 machines public and 4 machines private. I have swbell and 5 static IPs. I aslo have a EZXS55W switch and a BEFSR81 Router. I put the first three machines on the switch and the other four on the router. Everythng was perfect except they did not see each other. Please help. Thanks.
 
Torky,

You'll need to provide information about the network configuration, OS's being run and the protocol's implemented.

What do you mean by "see each other?" The fact that you are on two different sides of the router is going to make this difficult. If you are using NetBEUI for the sharing, this will not work. NetBEUI is not routable and will only work on the same segment/subnet. If you are trying to do it with TCP/IP, the router's NAT [firewall] is going to interfere. I would also hope that the three "public" machines are well secured.

The Old Man
 
TheOldMan386,
I am running xp on most machines, and 98 on 2. The "Public" machines are running xp. The protocol is TCP/IP. I am not sure the machines have to be public. I need to access the machines remotley, and I was planning on using windows remote desktop. I have it running and it works great, but would you recomend another way to achieve this. I also have one machine with a Novex2000 board. Which is a security camera system with remote access. It uses the ip to comunicate to the outside world. As far as "see each other," I mean to locally share files. I am not sure this can be done with the equipment I have. If I need something else please let me know, Thanks, Torky!
 
The Old Man

Sorry about the name, 386 instead of 346!

Torky
 
Torky,

No problem with the name.

You could open the ports in the router to allow the ability to map drives and share files but that sort of defeats the purpose of the firewall. With the Linksys, if the ports are open, they're open to anyone, including any hackers on the internet. As far as I know, remote desktop is also pretty insecure. One of the tactics we've used in the past to protect an external server is to lock down all maintenance functions so that they had to be done by an account physically logged on to the machine, not over the network. If you needed to sccess files or put new files on the server, it was done by FTP. The FTP server was configured to restrict access to the LAN's specific subnet. It may not be the most convenient arrangement but it was secure.

Hope that helps.
[yinyang] What goes around - comes around. [wink]
The Old Man

If you feel that this post can help others, please indicate it with a star.
 
I'd be pretty hesitant to put any always on machine (especially running an MS OS) completely open on the interent. Remote desktop does use encryption (don't have the specs handy but it should be similar to MS's VPN). You could put everything behind the router and only open the ports required. 3389 for RD and whatever you need for the camera software. The biggest problem that I see is that the router can only forward port 3389 to one particular machine. You will have to set up your network so that this 1 machine can access the others trhrough the local network. Another option you could look at is VPN.


FWIW, here's a couple of articles about RD:
The known previous vulnerabilites in RD were patched in SP1.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top