clutch

NP, I try to post links if it's something of possible interest. ------------------ Regards, clutch

Well, the issue was resolved once he adjusted his naming convention. In addition, the excessive activity of the NIC is a giveaway as well. ------------------ Regards, clutch

Oh well, and to think we went 3 whole days without a major flame... /edit Scratch that, I see this JJ32 person seems to have issues with Brian Frank. I just don't go into the Win9X forum enough to notice, I guess... /end edit ------------------ Regards, clutch [This message has been edited by clutch (edited 27 March 2001).]

It's cool dude. Here's something to try out. First, go to this link and read up on the ARC naming conventions (towards the bottom). http://cramsession.brainbuzz.com/cramsession/microsoft/ntworkstation/guide.asp Next, I *think* the new path that you will enter will look something like this; multi(0)disk(0)rdisk(1)partition(1)\Windows="My POS WinDOS Install" The changes are to "rdisk" which is now "1" since it is on IDE channel "1" and "My POS WinDOS Install" will show up as a menu option. In addition, make sure that the "boot loader" entry has more than "2" for an entry to give you a chance to select the new path. If you are really concerned with messing up your boot.ini, you can make a NT boot floppy and try this new path in the boot.ini on it. Then, boot your PC off of it and see if it works. Here's how to do that; http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14716 Hope this helps. ------------------ Regards, clutch

His problems were based more around name resolution, rather than rogue DHCP servers or hardware settings. With all the defaults of the hardware, he should not have to wait more than 10 seconds for credential authentication. In addition, I am more of a fan of DHCP use than static IPs, as you can change settings for an entire subnet from one server, rather than walking to each client and having to adjust then manually (or from batch-driven processes). Also, relying on the broadcast nature of NetBIOS over TCP/IP provides for sloppy results in any of the Windows OSs and in Samba on *nix (I can only say this for Linux, as I am not a true Unix person; but the implementation should be quite similar for them all). You tend to have more issues with ghost machines (machines that *seem* to be on the network, but only the name of the PC is in the master browser listing) that keep the valid PC from getting online due name conflicts. The odds of timeouts increases as well, along with flaky credential verification. While a good deal of people use Win9X in peer to peer mode, the vast majority of them do not stress their systems/network like the users do here. Therefore, they will not see (or notice) a lot of the problems that we would. If you can't use some sort of name resolution system (hard to believe since a lot of people have "accquired" copies of various Windows server OSs ), then consider going with a LMHOSTS file and static IPs. Bear in mind that when playing with more modern networks, there are 3 major players to be concerned with; 1. Name resolution 2. Permissions 3. Time synchronization (more of an issue with AD security services; you know, that funny little w32time issue you probably have in your log). Sorry for the long post, but I have seen quite a few networks have similar issues that were all solved by a proper name resolution scheme /end soapbox ------------------ Regards, clutch

You have to connect your modem to a router/proxy BEFORE you can connect it to your network (switch or hub). So, it goes wall>modem>router>switch>PCs and Mac if you want network support from your cable modem. If you just want to throw another NIC into a PC, and set it up as a router (or proxy), then you can forgo buying the seperate router. ------------------ Regards, clutch

I am surprised that you have to enter a key for your MSDN Office2K set. I have the Office 2K Premium Developer's Edition, and I did not have a key with it. It was in a handy-dandy 5 CD set as well. Actually, I think the only thing that I have seen in the MSDN sets (haven't been a recent subscriber in a while) was a copy of Win2K AS. Are all the apps coming this way from MSDN now? ------------------ Regards, clutch

Switch is DLL, but I think the reason for the confusion is that the network layer is listed as "dealing with packet switching" in some texts that you will see. Kinda confusing terminology if you get stuck having to wade through it. ------------------ Regards, clutch

Score 1 for the good guys! ------------------ Regards, clutch

To me, it sounds like a name resolution issue. Try HarU's recommendation, and make sure that you state your server's name as a domain controller, like so: 200.200.200.50 titanic #PRE #DOM:SAVILLTECH Check out this link for some more info on LMHOSTS. It shows using mulitple domain controller entries, but one will suffice. http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=13539 ------------------ Regards, clutch

Starband is a wireless service, correct? If so, I would imagine that you would need to hook the modem up to a PC running some sort of proxy (MS Proxy, Wingate, Sygate, etc) and connect a NIC from the PC to your network. I go to New Horizons for some classes occasionally, and they have that system (in WI). It is just about the worst broadband system that I have ever seen. It could probably be only local issues, but it's pretty bad. Sorry I don't have any more/good info to give you. ------------------ Regards, clutch

Are you going to be there, Inferno? I think I might be able to make that one. ------------------ Regards, clutch

¡Ç ------------------ Regards, clutch [This message has been edited by clutch (edited 26 March 2001).]

Are the profiles set to be local or roaming? If they are local (default), then is little being done aside from loading security policies. ------------------ Regards, clutch

Modem: Device that initiates comunication from one network to another. Hub: Device that lets multiple PCs converse with each other when connected. Device permits broadcasting of packets across all ports. Rated speed is divided amongst all ports. Switch: Similar in function as hub, except it does not permit broadcasting across all ports, hence less traffic. Rated speed is available to each port, not just across the entire unit. No broadcasting combined with great per-port bandwidth equals faster transfer speeds. Router: Device for connecting 2 networks. In the case of TCP/IP routers, they are used for connecting different subnets. Most of the devices that you see for sale, like the Linksys BEFSR41, are routers with built-in switches. On one "end" (node) of the unit, you connect the modem. On the other end, you connect the PCs/hubs/switches that you need for your local network. Some of the units can be purchased with no internal hub or switch, which would make the unit cheaper to purchase, but would need an external hub/switch to connect more than one PC to it. ------------------ Regards, clutch [This message has been edited by clutch (edited 26 March 2001).]

I have a 20GB and 25GB at home, and a few old SCSI units at work. They have been running fine (ranging from 1 to 5 years old). ------------------ Regards, clutch

Firewalls are a must at the gateway (being a single PC, then it would be the gateway itself) between local and public networks. That's it as far as that part is concerned. The thing I don't do (or understand a need for) is install firewall software on ALL of the PCs on a LAN when there is a firewall mechanism already in place at the gateway. ------------------ Regards, clutch

Quote: <font face="Verdana, Arial" size="2">Originally posted by DosFreak: If you use NTFSDOS or ERD Commander you can easily access the DOS prompt.</font> What do you think of ERD Commander? I have it budgeted for work, but I haven't decided if I should get it or not yet. Is NTFSDOS just as functional? Where can I get it at? edit Never mind, I found it with ERD Commander at www.winternals.com. /edit ------------------ Regards, clutch [This message has been edited by clutch (edited 24 March 2001).]

I think this is the link he was talking about for those who don't know: http://www.microsoft.com/downloads/release.asp?releaseid=28792 ------------------ Regards, clutch

You don't by chance have any mapped drives to the AD controllers from the joining servers do you? A good friend of mine just told me that's why he couldn't get his member server to join his newly created AD. ------------------ Regards, clutch

Hit me baby! I NEEEEEDDDD that! ------------------ Regards, clutch

Any better? Any worse? ------------------ Regards, clutch

I had a situation once where I could not get a member server to join a domain due to "conflicting credentials". I wound up renaming the server (server name wasn't important as it was just going to be a file server) and sure enough, it was able to join. Just a thought. ------------------ Regards, clutch

I haven't had any issues with dcpromo. Now, the member server is an active member of AD prior to running dcpromo, correct? Sounds like a dumb question, but I am just making sure that your server is in the domain. I have not tried to join a workgroup level server into a foreign domain, as I have always had the domain ready for the new server during installation. As far as credentials go, you might want to try entering the admin user account name as either: DOMAIN_NAME\Administrator, or administrator@DOMAIN_NAME It could be an issue of not having the proper domain reference when making the request of network resources (such as joining a domain). The pop-ups *usually* have a DOMAIN entry to fill out, but try this method anyway in the username field even if you do see a DOMAIN option. ------------------ Regards, clutch

This may not be helpful, and I am still learning this as well, but I had a ton of problems with AD/DDNS until I setup a secondary DDNS box on my test LAN. Now they update each just fine, and they don't generate a ton of errors in the event logs. I am in the process of reading a couple of books on AD, but at the moment this is all I can offer. Sorry. ------------------ Regards, clutch