darkfiber1010

First, this is probably none of my business, but why do you have the network set up in the way that you do. What I mean by this is why do you have two NICs in the PC with one connecting to the internet and one connecting to a router? Versus the traditional setup where all your PC's would connect to the built in ethernet switch on the router, and then the Internet to the WAN interface on the router? The only reason I ask is that most times I find its better to keep things simple if possible. Anyways I'm affraid other than your network setup I can't offer any advice as to why your problem is happening. It is possible that something is causing a lot of extra traffic on your network, but that is just a theory.

Yes it is very possible. You are going to have to create a VPN connection though. Post back what router you are using and what operating systems are involoved and I can give you more specific information. Or search for info on setting up a VPN. I know for a fact there are other posts in this forum detailing VPNs I just can't find them right now.

As far as the software there are several different kinds you could use, but let’s stick with the free ones. If both machines are windows based and I'm assuming they are, you could use the built in Remote Desktop Connection. The only problem with that is the computer you are trying to connect to must be running Windows XP Professional. If that is the case, let me know and I will post specific directions for Remote Desktop Connection. Otherwise your best bet is VNC. Below are a list of generic steps for configuring remote access software, just incase you don't use VNC, but they should still work with VNC. Step 1: If the computer you are trying to connect to is behind a router/gateway, I suggest giving it a static LAN IP address, this is necessary for step 2. If it is not behind a router/gateway, meaning it connects directly to the Internet, then ignore this step and read step 2 b. Step 2: a. If your computer is behind a home router/gateway you will need to forward the port(s) that your remote access software uses, to the static IP addresses that you gave your computer in step 1. b. If the computers are not behind a router/gateway, but are behind some type of software firewall, you will need to add the port(s) to the exceptions list on the firewall. By defaylt VNC uses ports 5900 to 5906 on the server (the one you are connecting to) and 5800 to 5806 on the viewer (the one you are connecting from) but you might want to double check the ports for your specific version of VNC just incase. Step 3: This step is optional, but since you are connecting to a remote computer over the Internet I highly suggest it. The computer you are trying to connect to most likely has a dynamic IP address which means every now and then it gets a new address from the ISP. This becomes a problem when you are trying to connect to a PC with remote access software by IP address, because you have to find out the new IP address of the PC each time it changes. Fortunately there are free services known as dynamic dns services that allow you to map a dynamic IP address to hostname that will never change, this allows you to use the hostname to connect to the PC. Once again depending if your remote computer connects directly to the internet or is behind a router/gateway, there are different options. a. If the computer is not behind a router/gateway you will need to download a dynamic dns software client. Once such client is No-IP. Go to their website http://www.no-ip.com/ and create an account. After creating the account, you will need to go to the download section and download the client. Install the client and follow the directions to configure it. Now simply enter the hostname into your remote access software's connect to field. b. If the computer is behind a router/gateway you will need to configure the router to do dynamic dns updates. Most popular routers such as Linksys and Netgear support this. You will have to consult the directions for your specific router. One popular service for this is Dyndns. Go to their website http://www.dyndns.org and then create and account. After you create an account and login, go to My Services. Then go to My Services and Add Host Service. After adding the host, now go to the router and configure it to update to the dynamic DNS service by entering your account information. Once again consult your specific router's instructions. Now simply enter the hostname into your remote access software's connect to field. Once all these steps are completed, and you have your remote access software installed, the remote connection should work. However if it doesn't , post back and we can figure it out.

Both of these are pretty good GUI utilities for pinging and similar tasks. Even if you just want to mess around Qcheck in particular can give you a lot of interesting info. Ping Plotter: http://www.pingplotter.com/ Qcheck: http://www.ixiacom.com/products/performanc...skey=pa_q_check

In most of the experience I've had, the cable is bad somewhere. Yeah it might look perfectly fine and work most of the time, but there is something in the cable (usually something in the terminations) that is off just enough to cause intermitent connectivity. For example, the way the cable is seated in machine A might be fine, but when it is plugged in to machine B it might be seated slightly differnt, just enough to cause what ever is off to act up. You could test the cable to check for this, but testers arn't exactly a house hold item so I wouldn't expect you to have one or to buy one just for one cable.

Yes, the point of a firewall is to filter or block. It usually does this by inspecting traffic and comparing it to a set of rules to determine if it is allowed or blocked. This process adds to response times, which does technically slow you down in the amount of data you can send and receive, but the amount that it slows you down is so small that you really won't notice it. There is nothing you can do to fix it except not using a firewall, but as I said it’s not something you should worry about. The benefits of the firewall out weigh the small microseconds of response time that you will gain with out a firewall. If you are having problems with a specific firewall slowing down your connection by a large amount of time (several seconds or minutes) then it might be improperly configured or faulty.

RDC can be frustrating at times, especially when it doesn't work. First get the obvious out of the way. Make sure the hostname didn't change if that’s what you are using to connect. Make sure the IP address didn't change if that’s what you are using to connect. Make sure the Allow Remote Desktop Connections box is still checked in System Properties, Remote Tab. (I know you said the service is running though so it should be). I noticed you said you had external RDC connections forwarded to the desktop. It’s possible that somehow someone got into your machine remotely and messed around with things and that’s why it no longer works. Although this is not likely, I don't know what kind of security you have set up, so just keep it in mind. Personally I never use the default RDC ports when making external connections. RDC uses well known ports and it is not wise to keep the default ports when using RDC in an external connection scenario (connecting to your computer at home from a computer somewhere else via the Internet). So you can do one of two things. You could create a VPN connection and RDC over that which would eliminate the need to change RDC ports and make the connection more secure overall. Or if you don't want to go through the hassle of a VPN you could change the RDC ports by following these steps: http://support.microsoft.com/default.aspx?...kb;en-us;306759 Another good source of security info for RDC: http://www.mobydisk.com/techres/securing_remote_desktop.html Sorry for getting side tracked with security stuff, hope you figure out your problem.

Me again, just wanted to add that all of the above was assuming that your drivers are installed correctly and that the card is configured correctly. Just out of curiosity, does the wireless connection work on another access points at other locations? Or does it always have this issue regardless of the access point? If it does have the issues reguardless, that could be something other than IE settings causing the problem.

I've never had that problem on 98, but I've had a similar problem on XP when the "Dial whenever a network connection is not present" is checked. Usually if you check "Never Dial a connection", this will solve the problem. I'm not 100% sure on this but I think the problem has to do with a timeout issue. For what ever reason sometimes when using wireless connections (especially if the signal is weak or response time is slow such as in public access points), IE doesn't always detect the connection in time and if you have the "Dial whenever..." checked, it uses that. This is a theory, but there should be some kind of registry tweak or edit somewhere that lets you increase this timeout. If such a thing existed this would probably fix the problem. If no such registry edit exists, you can also try this. I realize that you probably want "Dial whenever a network..." checked because it’s just more convent when your using a dial up connection. However if you check "Never Dial..." to fix your wireless issue you can create a shortcut for your Dial up connection on the desktop and click on that before opening IE. I know that’s an extra step when your using your dial-up, but at least you won't have to go into connection options every time and check "never dial a connection" when your trying to use the wireless access. Or alternatively you could just use Firefox and see what happens

Not sure why all those wierd things are happening. Sounds like something is messed up with the NIC or drivers maybe? Anyways as far as the "Ping to test a cable" thing, its not a good way to tell. Sometimes a cable can be just good enough to get pings accross but it won't be able to handle normal data. Your best bet would be to use a cable tester.

A lot of home routers, Linksys particularly have problems with passing VPN traffic. Usually though if the router has a problem you won't be able to connect for very long if at all, so I don't think that is the case here. Here are some things you can try. First I don't know if this was fixed since service pack 2 or not but there is a registry edit that you used to have to do for the XP SERVER when in your situation. Here is the link http://support.microsoft.com/default.aspx?...6&Product=winxp After you do that, go to the CLIENT and try adding the IP address you are getting from the server as a static route. Do this by going to command prompt and typing: "route add 192.x.x.x mask 255.255.255.0 192.x.x.x" The first 192.x.x.x following add would be the destination address of your VPN server (PC A). The second 192.x.x.x address would be the address your client receives from the server. Yes this would mean that theoretically since you are using a range of addresses, you would have to do this process for each address in the range Also I admit its been awhile since I've played around with this stuff, I kind of remember something about the client and server having to have IP addresses on differnt subnets. I know it doesn't make sense at first and I wish I could remember the reason for it. Anywayas you might try it though just to see. For example if the server is on 192.168.1.0, assign the 192.168.2.0 subnet range to the clients. Good Luck, Jon

That is interesting, although I know every person is different so what seems straight forward for one isn't for another and vice versa. I heard the old CCNA was much more straight forward. I think that was the 640-607 exam but I can't be sure I use to know the numbers but don't anymore lol.

darkhack, my appologies I must have misunderstood you. I thought you meant you made a VPN with Windows XP and then switched to Windows 2003 S on the same computer and got the same blue screen problem. That is why I mentioned hardware. However if you tried it with two differnt physical computers as you say then it obviously isn't hardware. I strongly doubt it would be your ISP. At this point I'm not sure what it could be, but I will keep thinking. Let me know if you figure it out.

Damian_Iz, I didn't forget about you I've just been busy. Tomorro I will post some more directions to try to help you out. You're probably going to have to go in to the properties of the vpn server "Incomming connections" Icon then go to the Network tab then Internet Protocol and make sure Allow access to LAN is checked. Also you may have to manually specify an IP address range in order to correct the problem. In the mean time use google and find sites that explain VPN LAN browsing issues. Maybe you can figure it out for yourself till then.

darkhack, definitely check chicagotech's links, if they don't do anything for you it kind of does sound like hardware maybe. I know you say not but what is leading me to believe that is, it happened to you on the same computer under two different operating systems. It could mean a failing hard drive. Also it could be the copies of the OS that you used (although unlikely). Did you use installations that were slipstreamed, otherwise customized, or perhaps bootlegged (you don't have to answer this last one, I don't care I'm just pointing out that sometimes the copies available on the Internet don't always work).

Damian_IZ, I need more information in order to help you. Are you at least getting a successful VPN connection? What I mean by this is when you try to connect to your VPN server, does it successfully connect or do you get an error message for example "Error 721". If it does connect successfully without an error, then the problem is one of two things. The LAN settings on the VPN server connection might need to be reconfigured. Or it might be a problem with your router, some linksys routers have issues with VPNs that can not be corrected. However once you give me more information we can decided what the problem is.

Yeah those questions look pretty normal. Most of the IT cert tests are like that. It’s never about just knowing the content, you also have to be able to deduct, reason, and think logically. Just from personal experience I found the Net+ easier than the A+. If you think these tests suck, wait till you try a Cisco test. The CCNA test was brutal as far as "tricky" questions go. Microsoft isn't any better either. All's I can tell you is welcome to the wonderful world of IT cert exams. P.S. I personally don't care but I know a lot of the cert exams state at the beginning that you can't copy and reproduce questions and doing so will result in consequences or something, so you might want to be careful about posting exact copies of the questions.

It sounds like you want your router to perform dhcp. This will automatically give each computer you have an IP address. I can't tell you how to set it up because it depends on who made your router. Check the website of the router's company or call their tech support and ask them how to enable dhcp on the router.

Hmm I don't know much about using Windows Media Services for streaming but I suspect your problem has something to do with a network setting or limitation that the program has. Sorry I couldn't help but it might be worth checking this project out. The program is pretty flexible and has some very nice media streaming capabilites. http://www.videolan.org/

I don't know if you’re trying to set up a VPN Server, client or both. I have some instructions that I originally wrote for someone that wasn't that familiar with computers so if they are a little over explanatory at times I'm sorry. I'm assuming you’re using Windows XP, and some version of a hardware router/firewall. To answer your initial question though, a standalone VPN router is a nice thing to have but you don't need one if you want to save some money. A regular Windows XP (or other OS) computer will work just fine as a VPN Server. Setting Up the VPN Server: Step 1: Create a Connection Access the New Connection Wizard, usually found in the Start menu under Accessories then Communications or in the Control Panel under Network Connections Step 2: Click next and then select "Advanced Connections", then select "Accept Incoming Connections" Step 3: Leave everything unchecked and click next. On the next screen select "Allow Virtual Private connections" and click next. Step 4: Select the existing user account that you wish to access the VPN, or create a new one by clicking add. When finished click next Step 5: At the network software screen, you shouldn't have to do anything. The default values should be fine. However if you have issues later on we can come back here. So just click next for now and then finish. A new connection called Incoming connections should now be in your network connections folder located in Control Panel. Step 6: Setting up the Router/Gateway (this is where the fun begins) This step is specific to your router in order to complete the following you will need to consult the manufacturer website or if its one of the common ones such as Linksys I might be able to walk you through it. a. First there is one last thing we need to do on the server computer before we set up the router/gateway but it ties in with the router setup so that is why it is in here. In order for your VPN Server to function correctly you need to assign it a static LAN IP address and also Static DNS information. First access your router's setup and record your ISP's or LAN Server's DNS server IP address (there may be more than one, use both). Next look at the subnet mask that your router is using. Write down the subnet mask, it should look similar to 255.255.255.0. Now look at the DHCP range if the range is something like 192.168.0.2 to 192.168.0.254, write down the first number in the range to use as your static address and then change the range to the next highest number so it prevents your static address from causing an error. For example using the above range, you should use 192.168.0.2 for your static address and change the new range to 192.168.0.3 to 192.168.0.254 . Next Open your Local Area Connection and select properties then Internet Protocol and properties. Select "Use the following IP address" and enter the IP address and subnet mask, along with the static DNS information and click ok. Your connection should now have a static LAN IP address. b. Now that you have a static LAN IP address you need to go into the router and enable port forwarding to that address. The main port that needs to be forwarded for a Microsoft PPTP VPN is TCP 1723. Also 1721 I think. c. Also you need to enable VPN Pass-through and if there is the option specifically PPTP pass-through. On most home router/gateways there is no option for GRE 47 which is just as crucial as TCP port 1723 to the operation of the VPN. However PPTP pass-through should take care of this. I say should because some vendors such as linksys are notorious for having problems with their routers actually allowing GRE even though it claims to be supported. d. Finally you will need someway of reaching the VPN server from the Internet. This is done through either a WAN IP address or a hostname. You get a WAN IP address from your internet service provider, but in most cases due to technical reasons that address changes periodically, known as dynamic. In order to use a VPN Server you should have a WAN address that doesn't change known as static. You can buy a static address from your ISP but these are costly, however there is a perfectly legal and free way of getting around this. You use a Dynamic hostname service like www.dyndns.org. This service allows you to associate your changing IP address with a host name that doesn't change. The way it works is once you register for their service you pick a host name like "bobsVPN.dyndns.org" and initially you type in your WAN IP address so the service associates your address with the name. Next you go to your router/gateway and configure it for dynamic dns updates. What this does is when ever the WAN IP address from your ISP changes, the router automatically tells the dns service and the service associates your hostname with the new address. Most routers/gateway support this, the setup just once again just depends on your manufacturer. Setting up the Client: Step 1: Create a Connection Access the New Connection Wizard, usually found in the Start menu under Accessories then Communications or in the Control Panel under Network Connections Step 2: Click next, select "Connect to the Internet at my Workplace" and click next. It doesn't really matter if you are connecting to your workplace; Microsoft just worded it that way for some reason. Step 3: Select "Virtual Private Network Connection" and click next. You can enter anything you want for the company name; once again it doesn't matter if it’s not a company. Click next Step 4: If you’re using a high-speed connection you should select "Do Not Dial" and click next Step 5: Here you need to type the IP address or hostname of the VPN server. If you are connecting to someone else's VPN server they will provide you with the hostname or IP address. If it is your VPN server than use a Static IP address or a hostname that you created with a dynamic dns service. Step 6: Select the "Add shortcut to desktop" for your convenience if you wish and click Finish. Step 7: Setting up the Router/Gateway Most home routers/gateways don't block outgoing ports but just to be on the safe side enable PPTP pass-through.

I assume you are trying to set up a VPN Right?, because thats what that information is. First if you’re not that familiar with computers VPNs might be a bit difficult for you. I strongly suggest reading up on VPNs, but I will try to give you a quick but fairly through explanation of all the concepts. A VPN (virtual private network) is special, secure encrypted connection from one network to another. VPNs allow you to access network resources such as printers, file shares, etc on a different network than the one you are directly connected to. For example VPNs are used very commonly in situations where an employee needs to connect to a secure network such as a private office network, from home using an unsecured connection like the internet. VPNs do not allow you to control another computer remotely, that is access the remote computer's desktop as if you were at that computer. You will need Remote Desktop software for this. Remote desktop software can be used in conjunction with VPNs however. Anyways the information you posted is some of the information you need to know in order to set up your VPN. Now I don't know if you are trying to set up a VPN to your house or from your house to somewhere else or what, but If you have a high-speed connection such as cable or DSL you most likely have a router/gateway between your computer and your cable/DSL modem. In order to setup a VPN you will need to change some settings on the router/gateway, and that is the information you listed TCP refers to a type of port. The acronym isn't important, basically ports are a way for computers keep track of a conversation on a network. GRE is a type of protocol process that allows VPNs to be more secure. Now as I mentioned before I don't know if you’re trying to set up a VPN Server (the computer you want to connect to) or VPN client (the computer you use to connect to the server) or both. I am assuming you are trying to set up a client, if you are trying to set up a sever let me know, and I will post those directions, which involve much more configuration. I am assuming your using Windows XP, if not let me know and we can adjust the directions accordingly. Setting up the Client: Step 1: Create a Connection Access the New Connection Wizard, usually found in the Start menu under Accessories then Communications or in the Control Panel under Network Connections Step 2: Click next, select "Connect to the Internet at my Workplace" and click next. It doesn't really matter if you are connecting to your workplace; Microsoft just worded it that way for some reason. Step 3: Select "Virtual Private Network Connection" and click next. You can enter anything you want for the company name; once again it doesn't matter if it’s not a company. Click next Step 4: If you’re using a high-speed connection you should select "Do Not Dial" and click next Step 5: Here you need to type the IP address or hostname of the VPN server. If you are connecting to someone else's VPN server they will provide you with the hostname or IP address. An IP address is a unique identifier for computers, kind of like the street address your house has. "192.168.0.1" is an example of an IP address. A hostname can appear several ways but in this situation it would look similar to "something.something.com". Step 6: Select the "Add shortcut to desktop" for your convenience if you wish and click Finish. Step 7: Setting up the Router/Gateway This step is specific to your router/gateway. Linksys, Netgear and Dlink are some of the common ones so you may have one of those it should say right on the front. In order to complete the following you will need to consult the manufacture website or if its one of the common ones such as Linksys I might be able to walk you through it. a. When using a VPN client you really don't have to do much to the router/gateway. Most home routers/gateways don't block outgoing connections so the client ports 1024-65535 that you listed don't need to be opened. b. I can't remember if you need to do this for an outgoing client VPN connection but to be safe we will. You need to enable VPN Pass-through and if there is the option specifically PPTP pass-through. On most home router/gateways there is no option for GRE which is what we talked about earlier, however PPTP pass-through should take care of this. I say should because some vendors such as linksys are notorious for having problems with their routers not allowing GRE even though it claims to be supported. That should get you started, let me know and give me more info so I can help you better. Thanks, Jon

No, Although..... If you really wanted free broadband from the college here's what you can do. Hope that the network info you have is still valid, go to the college and tap into their LAN without them knowing, rig up a series of wireless transmitters, use enough so that you can get the signal at your house and there you go free broadband access. Well except for the several thousand dollar up front fee of the wireless transmitters but thats just a one time thing

Here's a random idea that I just thought of that might or might not (most likely not) work, but its worth a try. Setup a firewall on each connection that will allow/deny access based on programs instead of ports. On connection 1 block firefox and allow ie. Do the exact opposite on connection 2. My theory behind this is that when the browser tries to use one connection and gets blocked by the firewall maybe it will go to the next connection. I don't know if this will hold true though. Good luck, Jon H.

If you arn't being charged too much extra for the static, go with static. It will make your life easier down the road if you want to set up things like remote desktop access, VPNs, FTP servers etc.

Are you restricting this to just home routers or all routers? If it's all routers please add Cisco so I can vote for it.