Help with local network access

[schitonk]

you're not getting an ip from dhcp. if youre connecting through a router make sure dhcp is enabled and that the router is what connects to your modem to get out to inet.

[alphawave7]

you're not getting an ip from dhcp. if youre connecting through a router make sure dhcp is enabled and that the router is what connects to your modem to get out to inet.

Correct. the 169.xxx address is a default when dhcp server cannot see the device/puter, or has failed , for whatever reason, to properly assign an IP/subnet to the device/puter.

[mech259]

I have always had a static route to the SS server. I can change the port on my setup and try that. I don't understand why the current setup with port 80 worked for about a week just fine then quit working.

[mech259]

I also checked port status on my ISP and 80 is not blocked. I also checked my firewall and 80 is open for SS

[alphawave7]

I have always had a static route to the SS server. I can change the port on my setup and try that. I don't understand why the current setup with port 80 worked for about a week just fine then quit working.

This has less to do with SS, and more to do with the device running SS..your router simply isn't seeing the machine, for whatever reason. Does your router have a client table, where you can see the machine has joined the lan? Wireshark can also see the arp traffic and tell you if the router is com'ing with your machine. The 169.xxx addy tells us the machine is defaulting, not joining the lan.

[mech259]

I never thought it had anything to do with SS. I was trying to solve my local problem. Well, did a workaround and put the 169.xxx ip addy as a secondary IP and now it works.

[alphawave7]

I never thought it had anything to do with SS. I was trying to solve my local problem. Well, did a workaround and put the 169.xxx ip addy as a secondary IP and now it works.

When you said 'change my port in the setup' I thought you meant in SS, not your adapter. Sorry.

Still, why not add a static IP to your server's adapter, IN the range of your lan's dhcp? Then, dhcp won't matter anymore, and you'll have lan access.

[mech259]

I have always had a static route to the SS server. I can change the port on my setup and try that. I don't understand why the current setup with port 80 worked for about a week just fine then quit working.

I didn't change the port setting, thught about it, but after checking my ISP, they don't block that port. I have always had a static IP for the SS server. The problem lies within Windows 7. Think I'll move the server to my Linux Ubuntu machine, not as flaky as Windoze.

[GJ51]

It may not be a factor in your particular instance, but I've found over the years that everything just seems to go better when you don't use port 80. Even though your ISP dosn't block the port, they may still use it for remote management of the internet gateway device they provide.

I find all manner of wierd things going on in my FIOS router that aren't my doing. At one time I was convinced they had a bot that periodically went into the router and cleared many things I had set. After that we tried a few things that seem to have thrown them off the trail of our mods that allow us to access our servers. But we still never use por 80 or 443 for incomming traffic. Since then everything runs fine.

YMMV