Results 1 to 7 of 7
  1. craigf's Avatar
    Posts
    39 Posts
    Global Posts
    40 Global Posts
       #1  
    I searched for tips on this and guess I wasn't using the right keywords since nothing directly relevant came up.

    I'm trying to access a couple of servers I have on my home network (one webserver and one Squeezebox server) and my Pre can't see either one even when it's connected to my network via Wi-Fi using the same NAT router that those boxes are connected to.

    I checked my Pre's IP address (using both the app and terminal) and it has a 192.168.0.x address and is on the 255.255.255.0 subdomain like it should be, so I'm stumped.

    Is there some issue with the phone having a cellular IP address or something that is causing the issue? Any suggestions would be really appreciated...thanks.
  2. craigf's Avatar
    Posts
    39 Posts
    Global Posts
    40 Global Posts
       #2  
    Wow...seriously, nobody has tried accessing a server on a local network using their Pre before? I didn't think what I was trying was so unique.
  3. #3  
    I can confirm this. Apache running on 192.168.0.5:80. Pre on 192.168.0.15. Both subnet mask 255.255.255.0. Pre cannot access the Apache server.

    C:\Users\Scott>ping -n 10 192.168.0.15

    Pinging 192.168.0.15 with 32 bytes of data:
    Reply from 192.168.0.15: bytes=32 time=101ms TTL=64
    Reply from 192.168.0.15: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.15: bytes=32 time=249ms TTL=64
    Reply from 192.168.0.15: bytes=32 time=170ms TTL=64
    Reply from 192.168.0.15: bytes=32 time=91ms TTL=64
    Reply from 192.168.0.15: bytes=32 time=318ms TTL=64
    Reply from 192.168.0.15: bytes=32 time=239ms TTL=64
    Reply from 192.168.0.15: bytes=32 time=161ms TTL=64
    Reply from 192.168.0.15: bytes=32 time=79ms TTL=64
    Reply from 192.168.0.15: bytes=32 time=308ms TTL=64

    Ping statistics for 192.168.0.15:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 318ms, Average = 173ms

    C:\Users\Scott>

    Something strange going on there too. There was packet loss on a few occasions too.
  4. lordbah's Avatar
    Posts
    341 Posts
    Global Posts
    435 Global Posts
    #4  
    Works for me. On the Pre I run Web and browse 192.168.218.104 which is the internal IP of my Linux/Apache box.

    WiFi is sometimes glitchy coming off the Touchstone in the morning. It says it's on, but I have to turn it off and back on again via the menu before it actually works. Could that be happening in your case?
  5. #5  
    Quote Originally Posted by lordbah View Post
    Works for me. On the Pre I run Web and browse 192.168.218.104 which is the internal IP of my Linux/Apache box.

    WiFi is sometimes glitchy coming off the Touchstone in the morning. It says it's on, but I have to turn it off and back on again via the menu before it actually works. Could that be happening in your case?
    (In my case) I don't think this is the problem as I can ping the Pre. What's really weird is the latency, which doesn't occur anywhere else on the network. 192.168.0.1 can also be pinged fine <1ms from both the PC and Pre. I don't know where to start!
  6. #6  
    I'm at my office, connected to my wifi.

    I run Desknow email server on our Windows 2003 server here at the office, on local ip 192.168.0.26 port 8080. My Pre is connected to the wireless router on 192.168.2.5 (wireless router is connected to huge switch which runs through a Symantec hardware firewall/VPN)

    I browse to 192.168.0.26:8080 on my Pre and can see the Desknow email server login page just fine. Login with any account (mine, all the other guys here in the office, or the administrator) just fine. Everything seems to work fine here.

    I can also access it outside the office using our external IP, as I have port 81 forwarded to port 8080 for local ip 192.168.0.26 on the Symantec firewall. (connected to my home wifi or the cellular data. both work fine.)

    So, everything seems fine to me.
  7. tacroy's Avatar
    Posts
    169 Posts
    Global Posts
    219 Global Posts
    #7  
    Has anyone that has had a problem with this figured out how to fix it? I am trying to use the boxee app which accesses a web server on your internal network. But the pre can't see it! All my other machines can. And like a previous poster, if i find my IP through the pre's web browser it shows the same as my router (which implies it is on the same internal network) but when I try to put the ip of the webserver into the pre browser it fails as it were on an external network!

Tags for this Thread

Posting Permissions