Advice..

[Kagehi]

Since this does effect the server I have too, I figured I would ask here. I recently dumped my Dialup ISP (couldn't get a good enough signal for their wireless DSL option, so...), in favor of Cable internet. Costs me too much, for too little, but I am far enough for *real* ISPs that this is inevitable. In any case, I also changed the network configuration. I now have a Linksys WRT750N Wireless N router. So, here are the questions:

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. :(

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

[Bulle]

If your Cat5 network cable is in good shape (you did not torture it too much when running it along your walls right ?) then 30 feet is more than fine. You can normally connect with a Cat5 cable from up to 300+ feet (that's what the norm says). I have the same kind of setup cable-wise, I spent one whole evening gluing my network cable around the corners of my rooms to reach the server. Works like a charm.

Regarding changing IPs, you should probably configure your box to use a static IP on your internal network (192.168.xxx.xxx). Not much reason to use DHCP when you have like 3 computers... It is the default solution under Windows because it even works for dummies :grin: but you can do better than that.
Once you replace DHCP by a static IP in the network configuration for your card the router will adapt. The real problem you may have is if you accept connections from outside your network, through your cable provider. Unless you have a fixed IP at your provider's you will need to setup a kind of dynamic DNS entry that you refresh everytime you connect to the big world outside. DynDNS is a solution, there are others like NO-IP. The refresh part is usually taken care of either by the router (my Linksys has this, but it is old and behaves stupid) or a daemon you run locally on one of your machines.

[AndMetal]

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.


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.

[trevius]

Sounds like most of the info needed is already covered by the guys, but I figured I would add 1 small snippet in case you don't already know. When you are running pings from command prompt, the command to run an extended ping is "ping -t <ip address>". This way you can run a continuous ping to these different destinations to make sure that none are dropping packets. The default of 5 pings isn't enough to see most packet loss unless it is really heavy loss.

From what you wrote, I wouldn't doubt in the least that the problem could be with the OS. I have had weird issues on certain machines where pages needed to be reloaded more than 1 time to get them to not 404. It does sounds like you have had quite a range of issues, but it could all still be coincidental.

[Kagehi]

Hmm. Ok. Think I found what I need. There is a button called 'DHCP Reservation' that lets you select existing connections and set them to always use that IP. Found some ass on my router too. Any idea how you kick them off, other than setting up all the security I had off before?

Or, maybe he isn't on now, just listed in the system, due to having "been" on... Can't find anything for kicking users, but the router password is now changes, his mac address is in the "do not allow" list, and WEP is enabled. Oh, and SSID is off, which was my first stupid mistake. :(

Anyway. As to the issue with downloads. Guess I must be the damn PC. I have pinged it in the past with no issues, when on the original non-wireless router. Its not likely the problem appeared in the wiring "after" that. And, I have had no issues transferring files between them at all. Can try pinging again I guess. Tomorrow, when I get off work. :p

[AndMetal]

Anyway. As to the issue with downloads. Guess I must be the damn PC. I have pinged it in the past with no issues, when on the original non-wireless router. Its not likely the problem appeared in the wiring "after" that. And, I have had no issues transferring files between them at all. Can try pinging again I guess. Tomorrow, when I get off work. :p

Just to clarify (maybe I misunderstood), are you connecting via wired or wireless?

If you are connecting via wireless, you'll want to use NetStumbler (http://www.netstumbler.com/downloads/) to see who is using what channels around you. That was one MAJOR issue I had before (like 10 other people using channel 6, creating a lot of interference & packet loss).

[Kagehi]

Both machines are connected via wire. I got the wireless so that when I niece visited she could get internet via wifi, as well as possibly a laptop, etc., that I might buy at some point. So, no, the issues isn't that I have one on wireless. Previously I had an older model that was purely wire only, which I replaced with this new one.

[trevius]

Just 1 more thought on this that I didn't think of before; If you are running any kind of P2P or Torrent software on any of the PCs in your network, they will almost definitely cause connection issues with almost any internet downloads or programs. They can use hundreds of connections to different end-points and overload your internet connection or router. Make sure you limit the bandwidth allowed for such programs as well as limit the max number of connections that they can use. If you don't use any of these types of programs you can ignore this post, but if so I would try turning them off and see if that helps.

[Kagehi]

I do use them, but I wasn't at the time. Got home late, so haven't had a chance to do any pings, etc. and see what the issue is. BTW, how do you kill a bad update download and redo is for Windows? The Flash patch failed to install, and I presume it was do to a bad file, but the Windows patcher is doing the same thing that AVG did, instead of trying to redownload the failed patch, it just keeps trying to run the bad one from the local drive.. To me, the idea that something "critical" like Windows Update, or my antivirus, is too fracking stupid to figure something that obvious out automatically is just unbelievable. Its almost as dumb as the damn recorders they make that, despite being a bloody PC inside, can't a) keep time properly, or b) remember your setting, never or even just the fracking date and time, if the power goes out. Who hires the nitwits that make these things anyway, and from where?