Announcement

Collapse
No announcement yet.

Connecting to Pi via IP address

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • RobbH
    replied
    Originally posted by d6jg View Post
    ....The OP has appeared in a few places asking the same question but never provides any information on his network infrastructure or IPs of connected devices - unless he does no one is going to be able to answer the query.
    It's very easy to miss, but in post number 4 in this thread, he did say this:

    Laptop, Touch, TV, iPhones all showing in IP Scan. All are 10.0.0.xx and Pi also shows.

    Leave a comment:


  • d6jg
    replied
    Originally posted by jimwillsher View Post

    My home network is 10.0.0.x/24. As long as it's a private subnet - 10.anything, 176,16.anything, 192.168.anything etc, you're okay.

    https://en.wikipedia.org/wiki/Private_network
    Likewise.

    The OP has appeared in a few places asking the same question but never provides any information on his network infrastructure or IPs of connected devices - unless he does no one is going to be able to answer the query.

    Leave a comment:


  • jimwillsher
    replied
    Originally posted by garym View Post
    This is odd and it should be very simple. Maybe it is normal but your IP address of 10.0.0.52 seems unusual to me. Every local network I’ve ever had has been 192.168.1.xxx or 192.168.0.xxx.
    My home network is 10.0.0.x/24. As long as it's a private subnet - 10.anything, 176,16.anything, 192.168.anything etc, you're okay.

    Leave a comment:


  • Redrum
    replied
    Originally posted by slartibartfast View Post

    You can plug the HDMI out into a TV. Not so easy with a Pi4 and the annoying micro HDMI 😀
    Ah yes...I bought my micro HDMI adaptor when I bought my first 4, because some astute forum member mention that change to a 4. . Easy way to check!

    Jim

    Leave a comment:


  • slartibartfast
    replied
    Originally posted by Redrum View Post

    Or the pi, or pcp is not running - pi hardware, bad SD image, etc.

    I'm drawing a bit of a blank (because I never have had a need to do it) - is there a way to verify things are running without a network connection? All I can think of is blinking LED's...

    Jim
    You can plug the HDMI out into a TV. Not so easy with a Pi4 and the annoying micro HDMI 😀

    Leave a comment:


  • Redrum
    replied
    Originally posted by RobbH View Post
    My guess is that Slarti's suggestion of a bad ethernet cable connecting the Pi to the router needs to be explored before further action is attempted.
    Or the pi, or pcp is not running - pi hardware, bad SD image, etc.

    I'm drawing a bit of a blank (because I never have had a need to do it) - is there a way to verify things are running without a network connection? All I can think of is blinking LED's...

    Jim

    Leave a comment:


  • RobbH
    replied
    I think I need to correct some misunderstandings I caused. The OP (shacky73) answered a number of questions I asked, but it was sometimes difficult to sort his answers out from my questions. I have tried make this easier by putting my questions and comments in parentheses, while his answers are out in the open:

    (It sounds like you now have the Pi running pCP connected to your modem/router by ethernet, correct?)

    Yes. TV streaming. iPhones connect via WiFi. Laptop running LMS and SB Touch both connected WiFi and double hop working fine.

    (Do you still have a wireless extender in the network? Or any other devices, like access points? -- not answered; assuming not)

    (How is your Windows laptop connected to the network -- ethernet or wifi? Same for the Touch?)

    both WiFi

    (If your ip scanner is not reporting the other addresses, both the laptop and the Touch should be able to report their own ip addresses.)

    Laptop, Touch, TV, iPhones all showing in IP Scan. All are 10.0.0.xx and Pi also shows.​
    Note that he is reporting that now all his devices (except the router) are on the 10.0.0.x network, and we can safely assume the router is at 10.0.0.1. So my diatribe about different ways to find the ip addresses of his devices was irrelevant. There are plenty of good reasons for him to know how to access his router's web interface, but at present ip addresses do not appear to be part of his problem. My guess is that Slarti's suggestion of a bad ethernet cable connecting the Pi to the router needs to be explored before further action is attempted.

    Leave a comment:


  • RobbH
    replied
    Originally posted by Redrum View Post

    ...Often (two isp's that I have had) have the login username and password printed on the label on the router for ease of "remembering" Then, once logged in, the client list is usually quite apparent. No manual needed. After all, someone (isp? shacky73? ) had to setup wifi un and pw.
    I suggested he look there in one of the earlier threads. It's worth repeating! My impression (again, not confirmed in any way) is that he was not involved in the setup, so username and password are probably whatever the router manufacturer uses as default. In that case, they are probably printed on the label.

    he could also call tech support for his isp and they would help him.
    ....
    Jim
    Probably the best idea yet!

    Leave a comment:


  • Redrum
    replied
    Originally posted by RobbH View Post

    My impression -- not confirmed -- is that Shacky73 does not have a manual for his router and does not have access to its web interface. He has said that it was provided by Comcast/Xfinity, but we do not know the brand or model number, so it is very difficult to provide any guidance.

    could be, but I find my router (on a PC) with run->cmd->ipconfig, then look at default gateway. Often (two isp's that I have had) have the login username and password printed on the label on the router for ease of "remembering" Then, once logged in, the client list is usually quite apparent. No manual needed. After all, someone (isp? shacky73? ) had to setup wifi un and pw.

    he could also call tech support for his isp and they would help him.

    With my approach, I am just making sure that "I can't see it" isn't because of not looking in the correct spot. I have "lost" devices (not looking for the right "name") and what I do it turn off the device, note the # of clients connected, turn it on, watch the # increment, then know it must be there somewhere .

    Jim

    Leave a comment:


  • RobbH
    replied
    Originally posted by CJS View Post
    The web interface of shacky73's router can most probably be accessed via http://10.0.0.1
    Any ideas about default username/password? I think "admin" and "password" are standard on Netgear routers, but I don't know about others.

    Leave a comment:


  • CJS
    replied
    Originally posted by RobbH View Post
    My impression -- not confirmed -- is that Shacky73 does not have a manual for his router and does not have access to its web interface. He has said that it was provided by Comcast/Xfinity, but we do not know the brand or model number, so it is very difficult to provide any guidance.
    The web interface of shacky73's router can most probably be accessed via http://10.0.0.1

    Leave a comment:


  • RobbH
    replied
    Originally posted by Redrum View Post
    ...There are many ways to determine the ip address of your pi, but, I prefer to log into the router and look at the clients list....
    My impression -- not confirmed -- is that Shacky73 does not have a manual for his router and does not have access to its web interface. He has said that it was provided by Comcast/Xfinity, but we do not know the brand or model number, so it is very difficult to provide any guidance.


    Leave a comment:


  • RobbH
    replied
    I said:

    You are now in much better hands than I can offer, so I leave it to them to guide you.
    But then...

    Originally posted by slartibartfast View Post

    Could it be a faulty ethernet cable?
    I am moved to chime in: I thought that, too. Or, perhaps some lint or dirt might have gotten lodged in the ethernet port on the Pi, or even on the router. An examination of the ports with a flashlight might be helpful. Some non-metalic object like a toothpick could be used to clear out any debris found there.

    Leave a comment:


  • Redrum
    replied
    I read through the thread, and there is some good advice, here, but let me suggest a huge step back to your OP and suggest a couple simple things:

    There are many ways to determine the ip address of your pi, but, I prefer to log into the router and look at the clients list, in fact, you can filter to just ethernet connections. I note the ip address from there, in fact I often highlight it and control-c (copy). If unsure what one it is in the list, I start with the pi powered off, power on, wait for the count to increase, and find the new one.

    With the ip address copied, In the browser, I just want to make sure you are not entering it in a search window. I usually highlight the address that is currently in the address window (example "google.com" which is really "https://www.google.com/") then do a control-v (paste). So, I paste over the url with the ip address. This way I have removed my fat fingers from the equation.

    Also, there is a selection in chrome - select an address in any address window->right click->always show full url. I like it to make sure "https://www." is visible. Reason, you don't want to inadvertently enter "https://www.10.0.0.52" 'cause, that won't work.

    control-c/v, use 'em all the time, wordstar paying off all these years later

    Jim

    Leave a comment:


  • RobbH
    replied
    Originally posted by shacky73 View Post
    ....I know enough to be dangerous and am mobile.
    First of all, thanks for responding, and then even more thanks for responding with humor! If I were a better communicator, I would have found a way to express what I was trying to say without sounding like a stern taskmaster. I'm sorry about my tone, but that was the best I could do.

    You are now in much better hands than I can offer, so I leave it to them to guide you.

    Leave a comment:

Working...
X