Quote:
Originally Posted by Kagehi
1. I am not sure I "can" make the IPs static for each port, instead of on an "as needed" basis. For example, I have the .100 IP for my machine at the moment, but that was because it was the first "live" machine plugged in, even though the guy setting things up left it unplugged (cable color probably confused him), and I didn't realize I popped in into port 2 when I fixed it. This is probably not going to be a huge issue most times, but it "could" effect the operation of minilogin if my host machine got the wrong IP at some point. Would be a lot nicer if the minilogin allowed "ranges" for cases like this frankly. At least then you could target the basic range of IPs on an internal network that the login and server *might* be on, it would still be fairly useless for internet IP addresses.
Should I try to change the way it works to use static addresses, or would this be useless on this router? And, if not, is there some way I can use the "external" IP as the minilogin and server IP, or would the firewall in the router refuse that? It seems like there are some possible drawbacks with how wireless routers handle this sort of thing. :(
|
The best way to handle this is to use static IPs for your servers and anything else that needs a consistent IP address. Some routers incorporate assigning static addresses using DHCP based on the MAC address (I think I had a D-Link that did it). If yours doesn't, then you'll just have to configure them by hand. The "hardest" part is getting the DNS servers. I highly recommend against using your router as your DNS server because it's usually slower than going directly to the source. Everything else can use dynamic IP addresses, which sound like they're assigned to xxx.xxx.xxx.100+.
Since your dynamic IPs start in the 100's, you can use everything below that for your statics. I personally use 1 for the router (which is set by default), 10-19 for servers, 30-39 for game systems, 50-59 for desktops, etc. You can do it however you want, but it helps to have it planned out.
Quote:
Originally Posted by Kagehi
2. This is less about the server than just my network. I have had no problems, so far, with my main machine, which has, at most, about a 1-2 foot lead from the router to the computer (well except a few stutters where the connection came up with a "page not found", but worked the next attempt... I *can* download via this machine, passing the file through the router to a folder on the other machine, without any problems. *but* I have had Windows update foobar one install (for the a flash bug, which I can't get it to redownload...), AVG blow up on a 23MB patch download, firefox failed to patch 3-4 times before it worked, and initially I was getting some sort of HTTP BSOD with the second system (that machine was "not" able to connect via the dialup, so it was a while since it was patched, if it ever was, I don't remember)... I think the patches, once they installed, fixed the last issue, but its... I don't know what, dropping packets maybe, and not doing re-requests, getting them, but with corrupt data? Something that is causing erratic behavior.
What I am wondering is, could this be the length of the Cat5e cable I am running? The room is about 15 feet across, but I had to run in across the wall, around a few curves, then into the closet, before connecting it to a socket, which I wired a short bit into, to another socket, which then goes another 2-3 feet, to the second computer. In all, its probably about 29-30 feet of cable. Yeah, I know, this is bad, but I a) didn't have much choice, given where things needed to sit, and b) I thought it was within the "acceptable" distances. But, I am getting downloads that contain CRC check errors, don't complete, etc. Java flat out refuses to update at all, since it requires a "lot" of files to patch, and ever time I do it, I get an error in some file that didn't download correctly.
I almost hope this is an issue with the OS, since that might be easier to fix than to try to find some way to make the wiring shorter (that being nearly impossible without rotating the room in 16 dimensions, or something, so that the universe things the wall my computer "has to" set one is the same as the one the second computer is on the opposite side of. Given that I haven't quite figured out how to bend time and space to manage this, I am kind of at a loss for a solution. lol
|
A little base info on network cabling, and a little clarification about what Bulle said...
The maximum run you should have is 100 meters (about 328 feet) before using a repeater. The general rule is you can have up to 90 meters of horizontal cabling (from the "closet" to the "drop"), 2-3 meters of vertical cabling (in the closet, so between any patch panels, etc), and about 5 meters of cable from the drop to the computer. The last 2-3 meters are the fudge factor. At least, that's how it was taught during the network design portion of my CCNA class back in 2003.
So, because you're looking at much less than that, length shouldn't be your issue. It sounds like it might be an issue with the sockets you're talking about, it just depends on how they're wired. Another possibility it like Bulle mentioned, but could also be pinched cables (semi-crushed between the door & frame in the closet, along the wall & floor, etc).
An easy way to test out the integrity of the cabling is with a simple ping test. If you ping 127.0.0.1 (localhost) for a baseline (to make sure it isn't a problem with the TCP/IP stack on your computer), your router, another computer on your network, and a remote website (yahoo.com or something like that), see where you get any packet loss. That will help you narrow it down. |