Jump to content

Arie

Member
  • Posts

    832
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything posted by Arie

  1. It seems to be a problem now with the website itself, which runs on DotNetNuke. When I enter the URL in the address bar of my browser, it forwards me to the hostname, as written above. When I enter the URL\test.txt in the address bar of my browser, it does not forward me to the hostname, but stays on the URL entered and shows me the text file. In other words, the webserver works fine now, but the website itself is the problem. I'll forward it to the webdeveloper and see what he comes up with.
  2. While I was writing my last message, something has changed drastically... On the webserver the website was all of a sudden stopped. When restarting the website I got the error message: "the format of the specified network name is not valid". I changed the ListenOnlySomethingSomething as suggested somewhere on the Microsoft website by removing an invalid IP address and now when I try to access the website from home for example via its IP address, it finds the server... but then tries to forward me to http://hostnameofserver... which obviously cannot be found on the internet! What is causing this forwarding to the hostname of the server?
  3. Its been a while... What I've done thus far... I've placed the server back in its rack, but that didn't solve the issue. I have updated the firmware of our router, which didn't solve it either. I've changed everything possible on the router again and again to get the website working, but nothing I tried helped a bit. Then I had an idea! We have a Windows Home Server on our network via DHCP at current which is hooked up to be configured and which will be moved to another one of our locations, a small one. I changed the port forwarding of port 80 on our router to the IP address of this Windows Home Server, as it runs a website as well, and I tried connecting to our internet IP address to see if I would see the Windows Home Server website. Guess what, it showed up fine from outside the office! This means that the problem is the webserver itself and that we can exclude the router from being the issue. But what can make that the webserver cannot be accessed from outside our LAN? Port forwarding is fine, as we know now, it's something on the server which is configured wrong. The question is what? Can it be some kind of policy issue which only allows connections from the LAN? I couldn't find anything in Group Policy or the Local Security Policy about this, but perhaps I have missed something? Windows Firewall is disabled. We're running ESET NOD32 on the webserver, but disabling it doesn't help. ESET NOD32 is running on the before mentioned Windows Home Server as well, so that can't be the issue. Perhaps I've configured something wrong in the Internet Information Services Manager?
  4. Thank you very much for your help MrJinje Yes, it is enabled. I understand what you mean. Our router can be configured via a terminal and via a web interface, but you cannot change the order in access lists, so that won't be the issue. I have thought of something silly which might be the cause of the problem and that is that the web server has been taken out of its rack and placed in a different room for configuring the website itself, testing, et cetera, all third party work by the way. The web server hasn't been placed back in its rack yet. I'm not suggesting that it could be a routing issue for example, as our network is far from complicated, but there have been issues on our network in the past where someone would have used faulty UTP cables which caused network connectivity errors. Replacing the cables with proper UTP cables solved these issues instantly. Perhaps the room where the web server is now has this same problem. In our office the response time might be good enough for the website to show, but perhaps from outside our office the response time of the web server might be too low because of the bad cabling and perhaps this causes the error message that the website cannot be found. I don't know if this could be the issue, but it's worth checking. I'll put the server in its rack again tomorrow or Friday to see if it solves the issue or not.
  5. Yes, I could set up a VPN, but the website needs to be publically accessable When you say you are trying to connect from home, what do you mean, are you typing in it's internal IP address, the IP address of your remote router or something else ? When I wrote from home, I mean any location besides at work, so at home, a friend's place, et cetera. We have one router facing the internet, a DrayTek Vigor3300. Of course I don't use the internal IP address from another location, that would not work We have a block of IP addresses. Our router IP address forwards port 80 to the web server for example, but I have also tried adding the web server to the DMZ for example, but it doesn't work. IP have also tried binding other IP addresses like I wrote already, but no luck. When I enter the router IP address 123.123.123.123 in a browser while I'm at the office it forwards me to the hostname of the web server and the website shows. No matter what I try, accessing it from any other location doesn't work. I also have various terminal servers for example, but these work fine when I forward port 3389 for example. I'm quite sure therefore that I'm not doing something wrong in forwarding the right ports. I'm thinking more that it is a problem with the web server itself, perhaps a policy I don't know about, some kind of IIS configuration thingy, et cetera. But any idea what the problem could be and how to solve it is welcome. I'm going nuts here
  6. I wish I had one lying around I must have a HP mouse lying around somewhere, I'll try with that one.
  7. Default motherboard settings for both motherboards didn't work. I have enabled legacy USB devices for example in the BIOS of both motherboards as well, but that didn't do the trick either.
  8. A while ago I started building a HTPC with a 32-bit version of Windows 7 Home Premium. My build first used an ASUS P5N7A-VM motherboard. During the setup process already, the simple Logitech keyboard which I had connected via USB worked fine, but the simple Logitech mouse which was also connected via USB didn't work. Once the setup process had finished, the USB mouse refused to work. Unplugging the mouse and connecting it again didn't solve the issue. I get an error message that the USB device it not working properly. Using a different USB port didn't solve the issue either. I have tried a different Logitech USB mouse, but the issue remained. I changed the keyboard for another Logitech keyboard as well, thinking it might be a conflict between the keyboard and mouse, but again the issue didn't go away. Plugging in only a mouse didn't solve it either. Reinstalling the computer, but this time with another keyboard and mouse resulted in the same. The installation of the Logitech SetPoint software also didn't solve anything. Believing that it could be the motherboard, I changed it as well for an ASUS M4A785G HTPC. Nothing changed however. Both mice are not seen during the setup process and both mice refuse to work after the setup process is finished, no matter what I do. The only keyboard and mouse which worked, is a small keyboard which I have which has a trackball on it, so it's actually a keyboard and mouse in one. I have tried two ASUS motherboards, two Logitech keyboards and two Logitech mice and both mice refused to work. Does anyone have any ideas what this can be?
  9. This is driving me nuts I have set up a web server and it is working fine within our own network. When I try to access the website from home for example, it does not work and I receive the error "cannot display the webpage". I have no idea where to look and what the problem could be and I hope that someone here can be of help, before I throw the web server out of the window The website is running on IIS 6.0 on Windows Server 2003 Web Edition. The website is based on DotNetNuke, a CMS. When I enter the servername or its internal IP address in Internet Explorer, the website shows fine. On our router I have forwarded port 80 to port 80 on our web server, a different time I have added the web server's IP address to the DMZ, I have once added an IP alias on the router especially for the web server, I have combined all of these too, but none of these things solved the problem and I still can't access the web server from outside our network. Funny thing is that when I enter the IP address of our router or the IP alias in Internet Explorer while I'm at the office, it forwards me to the servername automatically and the website shows. It's like there is a kind of loop back thingy going on. I'm going to set up Syslog to see what is going on, but I hope that someone here has an idea on how to solve this issue as it's giving me a headache
  10. I have asked this question elsewhere as well, but thus far no one has been able to answer my question. I hope someone here will be able to though. Windows 7 Ultimate allows you to change the installed language once you have finished installing Windows 7 Ultimate. You can download various language packs from Windows Update to change your language into Dutch, German, Danish, et cetera. My question is not about the languages which you can change your installation of Windows 7 Ultimate into once you have installed it, but about the language which is used during the setup process. For example, if I would purchase a Dutch copy of Windows 7 Ultimate, will the installation procedure be in Dutch, or can I choose any other language from the first screen which you get when you start the installation? I have asked Microsoft and they could not answer this what I believe is a simple question. Microsoft told me to "go and try it", meaning that I would have to purchase a Dutch copy of Windows 7 Ultimate for example to see if I can select any other language, which is simply ridiculous. I have downloaded various illegal copies of Windows 7 Ultimate therefore, only to start the installation in Virtual PC to see if the language selection screen and the possible choices. A 32-bit and a 64-bit English version of Windows 7 Ultimate both showed me only English as an option. Another copy which I downloaded was said to be Dutch and it contained both the 32-bit as well as the 64-bit version of Windows 7 Ultimate and the language selection screen showed various languages, such as Danish, English, Spanish, German, Dutch, et cetera. (Which reminds me of another question, does a retail copy of Windows 7 Ultimate contain both the 32-bit as well as the 64-bit version of the operating system?) But was this really a Dutch retail release or was it a MSDN copy for example? I do not know. So, for anyone out there who has a copy of Windows 7 Ultimate, in whatever language, can you only choose one language (only English, only Dutch, only French, et cetera) or could you choose from a list of languages (English and Dutch and French, et cetera)? I need to have a installation disc which allows me to change the language already at the beginning of the setup process. I know that you can integrate language packs yourself, but it is much easier of course if you could simply purchase a copy where this is possible by default. I hope someone here can answer my question.
  11. What do you mean by "messed up pretty bad"? I don't see anything wrong with the script. I probably can't read documentation at all, or something like it. Nevermind, I have to done everything by hand again. Sigh. SED might not be a great tool, but there aren't many tools around which can do the job. SED does its work.
  12. I'd stick with a single path, and don't play with mirroring ports or vlans or any of the other managed switch features until you know what they're for. Pretend it's an unmanaged switch for now But even if we don't mirror any LAN port, we could still connect the managed switch to 2 LAN ports of the router... Would this be useful?
  13. Wouldn't it be wise to connect the managed 1 Gbit switch to several ports on the router, for example two ports? Is this possible at all, I wonder? And if it's possible, wouldn't this increase the maximum throughput from the managed 1 Gbit switch to the internet? Like below. Internet | | Router | | | | Managed 1 Gbit Switch On the router it's possible to mirror ports. The router has 4 WAN ports and 4 LAN ports. If I would connect the managed switch to the router with two cables, would it be a good idea to mirror port 1 on the router to port 2, so that both cables from the switch are basically connected to the same port? If the above is possible at all, wouldn't it be wise to connect both unmanaged switches with two cables instead of one to the managed switch as well to increase the throughput? Like below. Managed 1 Gbit Switch | | | | | | | | Unm. 1 Gbit Sw. Unm. 100 Mbit Sw. Thanks again!
  14. Will do. Thanks to both of you for the advice, it's much appreciated!
  15. Thank you very much for your reply! It's only a small office. All machines are located in the same single floor building. We have one 19" rack in which we have our router, switches and servers. This 19" rack is really the core of our network. Good thing that I asked then, because we believed that connecting each switch to the other switches would be a good thing... Thank you for clearing that up! But what I'm wondering is, our internet facing router has four 100 Mbit LAN ports, do we connect all switches to the router directly, or should we connect only the managed 1 Gbit switch to the router and connect both the unmanged 1 Gbit switch and the unmanaged 100 Mbit switch to this managed 1 Gbit switch? Let me try to draw it: Internet | | Router | | Managed 1 Gbit Switch | | | | Unm. 1 Gbit Sw. Unm. 100 Mbit Sw. Or... Internet | | Router / | \ / | \ Man. 1 Gbit Sw. | Unm. 100 Mbit Sw. | Unm. 1 Gbit Sw. In the first drawing the unmanaged switches are connected to the managed switch. If I understood you correctly we could best connect the servers to the managed switch and the workstations, printers, et cetera to the unmanaged switches (depending on their link speed of course). No network traffic will go through the router, unless it's meant for the internet. In the second drawing all switches are connected to the router. Connecting the servers, workstations, et cetera will be the same as above, but now all network traffic will go through the router. If a workstation from one switch works on a server on another switch, this network traffic will go through the router, whereas in drawing one this is not the case. The network ports on the router are also only 100 Mbit, which means that all 1 Gbit connections will be reduced to only 100 Mbit as soon as the traffic goes through the router. If the above is correct, that would mean that connecting only one switch to the router is the best way to go. This one switch should be the managed 1 Gbit switch then, as it'll be the backbone. The two other switches, both unmanaged should be connected only to the managed switch and not to each other, as this would create a loop, right? No VLAN's for now then So let me sum it all up: The router is connected to the internet. Of the four 100 Mbit LAN ports on the router, we only use one port, number 1, which will be connected to port 1 on the managed 1 Gbit switch. On this switch on port 2 we need to connect the unmanaged 1 Gbit switch and on port 3 we need to connect the unmanaged 100 Mbit switch. We don't link these unmanaged switches together, as it would create a loop. On the managed 1 Gbit switch we connect all servers. On the unmanaged 1 Gbit switch we connect all workstations. Devices which only require 100 Mbit, such as printers, need to be connected to the unmanaged 100 Mbit switch. Is this all correct? Have I understood it all? Very useful, so thank you very much! Hope you can reply as soon as possible to what I have written above, as we need to set up the above this week to have everything done before the end of the year. Thank you very much again, your advice is very much appreciated!
  16. I'm not much of a hardware person, I know how routers and switches work, but I need urgent help on how all these should be properly linked together? Which ports should be connected to what? Which devices should be connected to which switch? Should I use VLAN's or not? Et cetera. Let me start by listing what we have: - We're connected to the internet via glass, using a professional router. This router has 4 WAN ports and 4 LAN ports, all 100 Mbit. - Behind the router are 3 switches: 1 unmanaged 24-port 100 Mbit switch, 1 unmanaged 24-port 1 Gbit switch and 1 managed 48-port 1 Gbit switch. - We have about 4 wireless access points connected to our network. - We have about 4 security camera's connected to our network, either wired or wireless, both is possible. - We have about 8 to 10 network printers. - We have 6 servers at current, but this is growing still. Each server has 2 NIC's, plus 1 ILO, so 3 network connections in total per server. - There are about 40 workstations connected to our network, most of them wired, some wireless. My idea is as follows: - Connect each of the 3 switches to a LAN port on the router. This leaves us 1 free LAN port on the router. To connect these switches, I need to connect port 1 of each switch with the router, correct? - Connect each of the 3 switches to both other switches, so switch 1 needs to be connected directly to switch 2 and to switch 3, et cetera. By connecting the switches to each other, I avoid stressing the 100 Mbit ports of the router I was told, is this correct? Do I need to connect port 2 on switch 1 to port 2 on switch 2, port 3 on switch 1 to port 2 on switch 3 and last but not least connect port 3 on switch 2 to port 3 on switch 3? - Now that the router and the switches are connected, what do I connect to which switch? If I have 3 network connections per server, I can connect 8 servers in total to the unmanaged 24-port 1 Gbit switch. Since we have 6 servers at current, we'll have 2 ports left for 2 more servers in the future. But is it wise to connect the servers to an unmanaged switch instead of a managed switch? - We can connect all wired workstations to the managed 48-port 1 Gbit switch. Unless it's wise to connect the servers to the managed switch and the workstations to the unmanaged switch? - We were thinking of connecting the wireless access points to the same switch as the workstations, so the managed 48-port 1 Gbit switch, is this wise? - The camera's consume quite a lot of bandwidth we believe, so should we connect those to the managed 48-port 1 Gbit switch as well? - Printers can be connected to the unmanaged 24-port 100 Mbit switch. 100 Mbit is not fast, but enough for printing. So, what we're most worried about is how to connect the 3 switches. Connecting each of them directly to the router is good, but what about connecting them to each other? And if that's a good thing to do, how do we do that? Everything is a mess currently, so we would like to do this good now. Any help and advice would be appreciated very much! Thank you in advance!
  17. Not quite sure that I understand your problem Peter... The subject of this post is and what you wrote makes it all confusing I'm afraid... First of all you don't mention the version of the software which you're using, so I'll just assume that you're working with Windows Server 2003 Small Business Edition and Windows XP Professional. If I understand correctly, you can reach the server and all workstations internally via RDP without any problems, but when you want to reach them from the outside, for example from home, it fails. If this is the case, then your router is indeed the problem. Make sure that the workstations have fixed IP addresses. Your server should already have a fixed IP address. In your router, forward a port, for example 666, to the IP address of your server and as a port choose 4489. Now connect to your internet facing IP address using RDP, followed by the portnumber, for example: 123.123.123.123:666. It should work like this. Do this for every workstation as well. Make sure to use different ports on your router, so for example 667, 668, 669, 700, et cetera.
  18. 1. Grab a copy of HFSLIP. 2. Install Office 2003 via RunOnceEx.
  19. This has been posted various times before, just have a look at any of the tweaking threads. No need to make a new thread for every possible tweak IMHO.
  20. You can simply install XP as you would normally, but simply booting from CD, that is, if you have made your CD bootable. Simply rip the bootsector of your original CD and burn it as the bootsector on your new disc.
  21. Just place your shortcuts in the SendTo folder for the Default User.
  22. I've been using Windows Vista Ultimate since it's corporate launch and how much I like certain new features, I'm going to reinstall Windows XP Professional in the nearby future. I have good contacts with Microsoft. There are still several bugs in Windows Vista which annoy me and which Microsoft have admitted that they are indeed bugs, but which have not been solved with SP1. Certain software is not compatible with Windows Vista and although this is not a problem with Windows Vista, but actually with the software vendors, it also makes me want to get rid off Windows Vista. The latest problem in a new update, which resulted in my mouse behaving silly at times when selecting text for example. Again Microsoft have admitted the bug, but when it will be fixed, no one can tell me. Windows Vista also does too much thinking for me. When I want to create a new folder for example in the Start Menu, when I want to copy files into the Program Files folder, et cetera. Windows Vista annoys me, but I'll have to deal with it until I have moved houses, since I don't have time to get rid off it at the moment. Windows XP all the way for now and waiting impatiently for the follow up to Windows Vista, codenamed Windows 7.


×
×
  • Create New...