http://img365.imageshack.us/img365/7...wupdate6yd.jpg
The first one says "wireless network"...this is my desktop network status page.
Results 11 to 20 of 34
-
2005-12-16, 16:06 #11Junior Member
- Join Date
- Dec 2005
- Posts
- 23
-
2005-12-16, 16:29 #12Junior Member
- Join Date
- Dec 2005
- Posts
- 23
This is what happens:
Originally Posted by MrC
http://img510.imageshack.us/img510/7699/telnet1pb.jpg
Even when I am unprotected (and not running any other programs including antispyare).
http://img243.imageshack.us/img243/1...otected6ja.jpg
-
2005-12-16, 16:38 #13Senior Member
- Join Date
- Apr 2005
- Location
- Colorado
- Posts
- 10,101
You've posted screen shots showing the SlimServer web interface running in a browser window. I assume that the URL you're using is:
http://localhost:9000
What if, on the same machine you try to use:
http://192.168.1.100:9000
?
-
2005-12-16, 16:39 #14Junior Member
- Join Date
- Dec 2005
- Posts
- 23
It works. 1234567890
Originally Posted by JJZolx
-
2005-12-16, 16:44 #15Junior Member
- Join Date
- Dec 2005
- Posts
- 23
You actually bring up a good point, though...atleast you made me think of a question that hasn't been adressed from my first point:
Under Allowed IP Addresses can I do *.*.*.* and that just allow any IP address...so I wouldn't have to worry about it...right now i have like 5 ips in there just trying to cover all the bases, but I don't like that. However *.*.*.* doesn't help!
-
2005-12-16, 16:50 #16Senior Member
- Join Date
- Apr 2005
- Location
- Colorado
- Posts
- 10,101
Do you actually have "Block Incoming Connections" enabled? You should be able to just set it to "Do not block" and not worry about the Allowed IP Addresses.
Originally Posted by mangotbg
-
2005-12-16, 17:03 #17Junior Member
- Join Date
- Dec 2005
- Posts
- 23
Originally Posted by JJZolx
I didn't know those two options coordinated like that, but no I did not have it on "Block Incoming Connection". I have it on "Do not block" as you suggest.
I'm currently connecting the computer directly to the cable modem to see if it will work that way? That's the only thing I can think of right now...
-
2005-12-16, 17:10 #18Senior Member
- Join Date
- Apr 2005
- Location
- Colorado
- Posts
- 10,101
Not sure what you'll be able to test by doing that. Obviously, _something_ is blocking access to your SlimServer. Most likely something running on the server machine itself. There's a very distant possibility that the router might be blocking traffic to the server from machines on the LAN, but most routers are configured by default to permit all LAN to LAN traffic, so that's unlikely unless you've fiddled with something there.
Originally Posted by mangotbg
-
2005-12-16, 17:15 #19Junior Member
- Join Date
- Dec 2005
- Posts
- 23
Well, this is what I figured out by doing what I did... I can't even ping the desktop from my laptop. The laptop is connected wirelessly to my neighbor's router. My computer is directly hooked up to my cabe modem. I got a new IP address by doing so, but when I go to ping the new IP it times out? What?!?! What could be keeping my pc from being pingable?
Originally Posted by JJZolx
-
2005-12-16, 17:23 #20Senior Member
- Join Date
- Apr 2005
- Location
- Colorado
- Posts
- 10,101
A firewall can certainly do that. Did you try pinging 192.168.1.100 when both the laptop and server were on the LAN?
Originally Posted by mangotbg
Back up a minute... What was the earlier screenshot showing a wireless connection with IP address .1.101? Was that on the SlimServer machine or the laptop? What exactly does you network normally look like - how is each machine connected to the router?

Reply With Quote
