SMC DSL Router - How come I cant use MSN's Phone or Netmeeting

[emonkey]

Yep. More stupid questions.

I have a DSL Router and 3 systems in my home network.

When i try to do voice in MSN or AIM, or Netmeeting within the network i can do it just fine. But connecting to other systems through the internet doesnt work. Im pretty sure its because the router acts as a firewall, so how do i "securely" get around that for MSN, AIM or Netmeeting.

Ive tried using dialup to do voice or netmeeting and it works perfectly (except for speed of course) so an easy solution is appreciated.


Note:
I had a friend mess with my system the other day and he enabled DMZ in the router to my comp so he could vid conference through netmeeting. I dont know if it worked or not but when I got home the other night and tried shutting down it said "shutting down will disconnect the computer //HARRY ARGON/ from the system" or something. So i think DMZ opened me up to some major hacking. If you have suggestions for a more secure way to do this without using DMZ then id be very happy.

Thanks

 

[bex0rs]

I would first "un-DMZ" your box, then password protect all of your shares. Hopefully you didn't have anything critical shared because it's probably "in the open" now. Be sure to have a software firewall (like ZoneAlarm) running whenever you put your box in the DMZ. I'd also run a virus scan now, just to be sure everything is clean.

Moving on to the other issue, the SMC Router keeps an excellent log of denied packets. Just poke around the web interface and you'll find it. If you know the IP that you were trying to connect to in MSN, IM, or netmeeting, you can easily figure out which ports you need to forward to your computer by checking the log to see what wasn't getting through. This solution will only work for one computer on your LAN at a time, but at least it will get you up and running. If you need more specific help, feel free to ask more questions.

~bex0rs

 

[Wurlybird9]

So lemme get this straight...
because I'm also considering using a router with @home cable service...

Using the router and a single IP, I can only use these programs on one computer at a time? That sounds very limiting...

A bunch of people are saying extra IP's are wasted $$$,
but given this limitation and multiple users in my home,
I don't see why...

Jon

 

[Tallgeese]

<< A bunch of people are saying extra IP's are wasted $$$,
but given this limitation and multiple users in my home,
I don't see why...
Jon >>

Check this thread for some more info about how crappy (read: nonexistent) @home's network engineering really is.

You are right, Wurly. NAT routers/firewalls have problems with applications requiring port ranges or random ports to be open to transmit/receive data. And currently, the devices in the SOHO price range cannot forward to more than one address at a time.

But, I have to ask...you say that more than 1 person at a time is gonna be using NetMeeting simultaneously? Using vid-conferencing (OK, maybe just voice)? Ay carumba!

Simultaneous gaming, I can see, but vid or voice conferencing? Incoming bandwidth limitations imposed by your cable provider would bite a setup like that in the butt first.

 

[Wurlybird9]

I did read the @home thread...

And yeah, ok, vidconferencing would eat up bandwidth...

but what about other apps that require open ports?
Like, simultaneous voicechatting?
Or, simultaneous file transfer in ICQ?

I suppose I could just reserve all the cool stuff for myself ;P
But I'd just like to know if there are valid reasons for requesting additional IP's instead of using a router,
other than gaming purposes
(and some people are saying that even gaming can work behind a router)

 

[Tallgeese]

<< I suppose I could just reserve all the cool stuff for myself ;P >>

By Jove, I think he's GOT it!
First rule of system administration: get the cool sh*t for yourself, first. Justification? Testing, baby!

Really tho, gaming will work, but again, you can run into that simultaneous use issue.
Perhaps, in your case, multiple IP may be the only way to go to get what you need/want. But what we're saying to most people (who say they don't need/want simultaneous access like you have) is 1.) get a router, gosh-darn-it, and 2.) quite paying through the nose to @home. Who, even if they take your money for the extra IP addr, may or may not help you troubleshoot any problems, since the hub/switch and wiring you use to connect machines on your local LAN are not their responsibility. And most don't support any networked installs, period (at least, officially).