 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Small Business Server / SBS 2000 / March 2008Configuring SBS 2000 for NAT.
I have a client who is presently using SBS 2000, and is having constant problems with network connections. Here's what is happening. First, from time to time he loses connections and has to restart all of his workstations, and even the server to get he connections back. (History) Now, it was setup by somebody else over 5 years ago. Recently, I rebulit him a new server and loaded back his operating system into it, to get him running. Except, his network is static IP's with internet through the same LAN adapter. What I like to do for him, to solve his problem, is to attach his second LAN adapter with a router, for the internet, either DHCP or static using NAT. Then, using a HUB attach all of his computers to the second LAN adater and configure it to log in each workstation statically. This way, he will not have these issues again! Is this a better choice, or is there something else as to why he is having all of these problems. What he has, is a DSL modem attached to a wired router, along with all his clients, and they are seeing the server and logging in and seeing the internet too. Please advise if NAT is a good suggestion, I believe he is logging into a Domain controller... not sure, but can find out. I appreciate any feedback on this topic! I'd probably try to get the current setup reliably working before implementing any change. 1) Post the current output from 'IPConfig /all' for both the server and one workstation. 2) If the router has any DHCP ability (they normally do), disable it. Enable DHCP on the SBS. Set all workstations to get IP's via DHCP from SBS. Sounds like we can forget everything that happened 5 years ago because you have re-installed the server. When this was done, did you 'restore' AD from the old box? migrate it? or simply throw away the old and fresh install? If it's a fresh installation have the client machines been properly introduced to the new domain? >I have a client who is presently using SBS 2000, and is having constant > problems with network connections. Here's what is happening. First, from [quoted text clipped - 27 lines] > > I appreciate any feedback on this topic! Hi SuperGumby, Thank you for jogging my memory. Actually, no miragation was performed. All that was done, was a installation and I believe there is an AD. I have to look at it of course. But, what I do know, everything is setup statically. No DHCP! I believe the scheme of IP addresses its behind is 192.168.16.xxx. However, the DSL modem is plugged into the LINKSys router, and they are sharing the internet through it. When you say: "Enable DHCP on the SBS. Set all workstations to get IP's via DHCP from SBS", I was wondering... would it be best to attach the workstations unto a wired HUB and attach it to the server, being that their router is failing at times, and program the workstations that way? And configuring the workstations to log in dynamically might confused their printers they have. Which I believe is static. Although, they are HP laser printer, and inkjet. I feel that their network connections is failing at times, where they lose the communication between the workstation and server application. Which is DENTRIX. A medical software application. Would enabling SBS to DHCP really solve their problem? > I'd probably try to get the current setup reliably working before > implementing any change. [quoted text clipped - 41 lines] > > > > I appreciate any feedback on this topic! Without the current IPConfig from the server and a workstation it is hard to pass comment. However, _most_ network related problems occur because things do not happen in the manner SBS requires. The simplest way of fixing this is to allow SBS to be boss. The users are not going to be confused by a change from static to dynamic IP addressing, they don't even see this process. (NOTE: I was wondering what you meant by 'static logon'.) > Hi SuperGumby, > [quoted text clipped - 88 lines] >> > >> > I appreciate any feedback on this topic! Sorry, I should have been more clear. They all have been logging on with a static IP, instead of dynamic. (Fixed IP instead of DHCP). I know very little about SBS 2000, compared to 2003, etc. I remembered that NAT had be set in order for Windows Server 2000 to route the "name address translation" for both the internet and the workstations to exist together. But, you are telling me that I have to tell SBS 2000 to confire itself as DHCP and the problems will go away?! They are still freezing up with connection issues, and have to constantly reboot their workstations, and even the server in order for the software to work again, temporarily of course. I figured, if I get them a new router and HUB switch, and plug the router into one LAN adapter, and the HUB into another, and tell SBS 2000 to work it's NAT that it would operate without the system crashing. Tell me is it the server causing the problem by not being DHCP? > Without the current IPConfig from the server and a workstation it is hard to > pass comment. However, _most_ network related problems occur because things [quoted text clipped - 97 lines] > >> > > >> > I appreciate any feedback on this topic! The problem is not specifically due to whether or not SBS is doing DHCP. It is all about the proper configuration of networking. It is possible to manually configure properly. It is easier to let SBS do it for you. Throwing devices at the mix willy-nilly won't fix anything. > Sorry, I should have been more clear. They all have been logging on with a > static IP, instead of dynamic. (Fixed IP instead of DHCP). I know very [quoted text clipped - 138 lines] >> >> > >> >> > I appreciate any feedback on this topic! When you say, let SBS do it for me... are you referring about Active Directory? I'm sorry, it's just that I am confused on what exactly you are trying to get at... I mean setting up the LAN adpater on the server to DHCP is easy, but will it actually solve the problem that the customer is having? > The problem is not specifically due to whether or not SBS is doing DHCP. It > is all about the proper configuration of networking. [quoted text clipped - 146 lines] > >> >> > > >> >> > I appreciate any feedback on this topic! NO, I am not talking about AD, I am talking about DHCP, I thought you were too. I cannot put it more plainly. Configure SBS's NIC for operation on a static IP. Install and configure (using SBS wizards) the DHCP Server service on SBS. Ensure no other DHCP source exists on the SBS network segment. Configure all client PC's to get IP via DHCP. > When you say, let SBS do it for me... are you referring about Active > Directory? I'm sorry, it's just that I am confused on what exactly you are [quoted text clipped - 189 lines] >> >> >> > >> >> >> > I appreciate any feedback on this topic! DHCP... there is a wizard in SBS 2000? Interesting... okay. So, I configue the NIC's for operation on a STATIC IP? Like 192.168.16.xxx? Because what you said below is to configure the NIC card that way, which it is already. Then you said to Install & configure DHCP Server on SBS. And no, there isn't any existing DHCP on it! But why is the application still crashing when trying to access it? In other words, what is it that STATIC IP is doing that DHCP would not do? How does changing it really resolve the crashing issue?! Can you explain? > NO, I am not talking about AD, I am talking about DHCP, I thought you were > too. [quoted text clipped - 197 lines] > >> >> >> > > >> >> >> > I appreciate any feedback on this topic! SBS 2000, 2 NICs, STATIC IP, ISA [PROXY SERVER], with ROUTER http://www.sbslinks.com/sbs2000router.htm Andy Goodman's articles on setting up SBS 2000 (SBS 2000 Walkthrough) http://www.sbs-rocks.com/articles.htm#SBS 2000 Articles Once you've got SBS 2000 set up correctly, if the apps continue to crash, then you can start looking at hardware (maybe a NIC problem) or software issues. As a side note: If you only have a single NIC in the SBS 2000 server, then ISA will be running in Cache mode and not Firewall mode.  SignatureMerv Porter [SBS-MVP] ============================ > DHCP... there is a wizard in SBS 2000? Interesting... okay. So, I configue > the NIC's for operation on a STATIC IP? Like 192.168.16.xxx? Because what [quoted text clipped - 252 lines] >> >> >> >> > >> >> >> >> > I appreciate any feedback on this topic! Hi Merv Porter- Okay, the server is a Xeon Core 2 Duo processor, two of them with a Xeon motherboard that has two NIC's on it. So, the hardware is current technology as of less than one year ago. So, if I do this, and their software still crashes, is it possible that the HUB or router is the problem? Or, is it that he is using 7 PC's to log on to the server and licensing is the issuse? He's using a medical application for dental, and he has exam rooms each with a desktop computer, and from time to time it also crashes unexpectively. So, I run MMC and install DHCP onto the server, and should I replace his router(s). He has one 8 port wired router, and another 5 port... I think?!? I'm not there to confirm his hardware at the moment. But, I like to propose a solution for him up front going in on this, (I'm not as familiar with SBS 2000 as I have been working with 2003 R2 and now the new 2008 which I will be testing) - will he need to replace the router and use a HUB instead? For he has presently, two (2) NIC cards, as I said, and if the application still crashes, we must assume hardware. I've alredy spoken to DENTRIX, their software application support team, they claim it's a communication or hardware issue that is having the problem. That's why I did this post about NAT. That's is all. > SBS 2000, 2 NICs, STATIC IP, ISA [PROXY SERVER], with ROUTER > http://www.sbslinks.com/sbs2000router.htm [quoted text clipped - 266 lines] > >> >> >> >> > > >> >> >> >> > I appreciate any feedback on this topic! Crashes... SBS 2000 was designed to be setup and used with 2 NICs in the server (so that ISA 2000 could be used in Firewall Mode). Have you checked the event logs on the SBS server and on the workstations for clues as to why he's having crashes? And what is actually crashing... is it the Dentrix App or the workstation OS? If memory serves, SBS 2000 was fairly forgiving as far as CALs were concerned. It wouldn;t just crash. It would give a CAL error in the event logs and maybe in the workstation logs. While it could be his router (a comm problem with the server), I suspect it may have more to do with the SBS server (hardware or software problem). I also wouldn't think that Static vs Dynamic IP addresses would be the cause of crashes. However, installing a switch (not a hub) and putting all workstation plus the server on it would take the router out of the equation as far as accessing the Dentrix program on the server (assuming it a local app and doesn't need to access the Internet). May be a cheap thing to try and would be needed if you intend to set up SBS 2000 in the future to use ISA as a firewall. If the hub doesn;t fix the problem, I'd say you're looking at either a NIC hardware problem (or setting) or a Windows 2000 software issue. Another thing you might look at is turning off "autodisonnect" on the server: How Autodisconnect Works in Windows NT and Windows 2000 http://support.microsoft.com/kb/138365 Turn off Autodisconnect... net config server /autodisconnect:-1 I assume you installed SBS 2000 SP1a (the last update for SBS 2000) to the server along with the latest MS security patches for the underlying Windows 2000 OS. Small Business Server 2000 Service Pack 1a http://www.microsoft.com/downloads/details.aspx?FamilyID=f4fc58d0-1fac-4927-84d7 -189fa1b690be&displaylang=en SignatureMerv Porter [SBS-MVP] ============================ > Hi Merv Porter- > [quoted text clipped - 338 lines] >> >> >> >> >> > >> >> >> >> >> > I appreciate any feedback on this topic! |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.