I spent 9 hours trying to setup slimserver with no avail...

**dean** · 2005-12-16, 17:24

I'd bet it's related to the firewall you've got installed on there.

I realize that it's turned off, but I've heard stories about
firewalls having to be uninstalled in order to fix similar problems.

On Dec 16, 2005, at 4:15 PM, mangotbg wrote:
> 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?

**mangotbg** · 2005-12-16, 17:29

Originally Posted by JJZolx

A firewall can certainly do that. Did you try pinging 192.168.1.100 when both the laptop and server were on the LAN?

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?

192.168.1.101 is my laptop
192.168.1.100 is my desktop
192.168.1.2 is my router

My computer is connected to a hub that is connected to the router. The laptop connects wirelessly. I guess I haven't tried hooking the laptop up with RJ45.

Oh, and as "scary" as it can be to do this the computer is currently connected to the cable modem w/o any firewall...so I don't understand why I can't ping it? The laptop is behind a router, obviously, though...i dunno if that has something to do with it.

**gjrhine** · 2005-12-16, 18:50

Why is the modem connected to the computer rather than the router?

**Maditude** · 2005-12-16, 19:21

Originally Posted by gjrhine

Why is the modem connected to the computer rather than the router?

A very good question...

mangotbg: I would highly recommend reconfiguring your network, like so:

1) Connect the cable-modem to your router's WAN port.
2) Connect the rest of your computers to your router's LAN port(s). If said router only has one LAN port, plug your computers into a switch or hub, and then the switch or hub into the routers LAN port. I'm sure you'll enjoy having all your computers able to access the internet.

That will at least get everything on the same network...
Your computers should all be getting a DHCP address from your router (might want to configure the one that will run slim-server with a static address).

**mangotbg** · 2005-12-16, 19:39

Originally Posted by Maditude

A very good question...

mangotbg: I would highly recommend reconfiguring your network, like so:

1) Connect the cable-modem to your router's WAN port.
2) Connect the rest of your computers to your router's LAN port(s). If said router only has one LAN port, plug your computers into a switch or hub, and then the switch or hub into the routers LAN port. I'm sure you'll enjoy having all your computers able to access the internet.

That will at least get everything on the same network...
Your computers should all be getting a DHCP address from your router (might want to configure the one that will run slim-server with a static address).

As to why the modem _WAS_ connected directly to the computer was to see if I could get a ping. I couldn't. Shouldn't a computer connected directly to the modem, without any firewall *hardware or software based* be pingable by anyone else? It's not a rhetoricle question, I really think it should but it wouldn't? Wouldn't that seem as if something is off?

I'm going to try uninstalling my firewall as suggested and see if it is indeed somehow affecting the ports even though it was disabled.

**mangotbg** · 2005-12-16, 20:12

Interesting news:

I disabled the laptop's wifi and connected to the same hub that the desktop is on (which is in turn connected to the Linksys router) using RJ45 cables.

Laptop IP = 192.168.1.102
Desktop IP = 192.168.1.100

192.168.1.102 still cannot ping 192.168.1.100

however

192.168.1.100 _CAN_ ping 192.168.1.102?

Can anyone explain this?

http://img215.imageshack.us/img215/953/ping8xx.jpg

**gjrhine** · 2005-12-16, 20:19

Both connected to lan ports (not modem port)?

**JJZolx** · 2005-12-16, 20:21

Originally Posted by mangotbg

Interesting news:

I disabled the laptop's wifi and connected to the same hub that the desktop is on (which is in turn connected to the Linksys router) using RJ45 cables.

Laptop IP = 192.168.1.102
Desktop IP = 192.168.1.100

192.168.1.102 still cannot ping 192.168.1.100

however

192.168.1.100 _CAN_ ping 192.168.1.102?

Can anyone explain this?

http://img215.imageshack.us/img215/953/ping8xx.jpg

The laptop's ethernet port has a different MAC address than the wireless card. As far as your DHCP server is concerned the .101 address is still in use by the wireless card, so it handed out another IP address.

The reason you can ping the laptop is because the laptop isn't screwed up by some port blocking firewall software. The way most software firewalls will be configured on a desktop computer is that they will permit anything _out_, but only allow return traffic in response to an outgoing request.

**mangotbg** · 2005-12-16, 20:39

Originally Posted by JJZolx

The laptop's ethernet port has a different MAC address than the wireless card. As far as your DHCP server is concerned the .101 address is still in use by the wireless card, so it handed out another IP address.

The reason you can ping the laptop is because the laptop isn't screwed up by some port blocking firewall software. The way most software firewalls will be configured on a desktop computer is that they will permit anything _out_, but only allow return traffic in response to an outgoing request.

Is there anything I can do to fix this?

**JJZolx** · 2005-12-16, 20:42

Originally Posted by mangotbg

Is there anything I can do to fix this?

Have you uninstalled F-Secure and rebooted the PC yet?

Thread: I spent 9 hours trying to setup slimserver with no avail...

Thread Tools

Search Thread

Display

Re: I spent 9 hours trying to setupslimserver with no avail...

Posting Permissions