RE: Domain vs Wkgrp changed VB app launch
From: Gary Fose [MSFT] (garyfose_at_online.microsoft.com)
Date: 02/22/04
- Next message: Dan: "Win2K/XP connectivity problem"
- Previous message: Gary Fose [MSFT]: "RE: AppleTalk issues"
- In reply to: Jim: "Domain vs Wkgrp changed VB app launch"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 22 Feb 2004 01:46:13 GMT
Hi Jim
Ater reading your book, here are some comments..:)
1. You had a problem with the VB app at home because apparently it needs something from
your network at work to run (so it would appeard from your message). My guess is that Office
was installed on the laptop from and netowkr share at work and the VB app needs something
from that share everytime it runs because that whatever it needs was not donwloaded and
installed on the laptop but rather accessed over the workplace network.
2. If the MIS folks are correct about not being able to rejoin the domain with the same name,
then they could have told you about creating a separate hardware profile on the laptop, one
for work and one for home. This way you will not have to make any changes betwene home
and work other than selecting which profile to use when booting up.
Hope this answers all your questions.
Thanks,
Gary
--------------------
'--'Content-Class: urn:content-classes:message
'--'From: "Jim" <anonymous@discussions.microsoft.com>
'--'Sender: "Jim" <anonymous@discussions.microsoft.com>
'--'Subject: Domain vs Wkgrp changed VB app launch
'--'Date: Thu, 19 Feb 2004 16:56:38 -0800
'--'Lines: 82
'--'Message-ID: <1354b01c3f74c$654df990$a401280a@phx.gbl>
'--'MIME-Version: 1.0
'--'Content-Type: text/plain;
'--' charset="iso-8859-1"
'--'Content-Transfer-Encoding: 7bit
'--'X-Newsreader: Microsoft CDO for Windows 2000
'--'Thread-Index: AcP3TGVNKLph0AQQQU2FaWV4liH7HQ==
'--'X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
'--'Newsgroups: microsoft.public.win2000.networking
'--'Path: cpmsftngxa07.phx.gbl
'--'Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.networking:55421
'--'NNTP-Posting-Host: tk2msftngxa12.phx.gbl 10.40.1.164
'--'X-Tomcat-NG: microsoft.public.win2000.networking
'--'
'--'Background (questions are at the bottom):
'--'=========================================
'--'I have a company laptop running Window 2000 Pro. While not
'--'really a Visual Basic programmer, I inherited support and
'--'maintenance for a small application. I was making changes
'--'and testing on the laptop at work normally. The laptop is
'--'configured for a domain here at work although I did not
'--'have the network cable connected. The actual VB
'--'development is done on a desktop machine, then the program
'--'is copied to a memory stick and installed on the laptop.
'--'
'--'I took the laptop home to continue development on my
'--'desktop PC there. Since I have a 10bT network at home, I
'--'thought I would make my life easier by connecting it, then
'--'I could transfer the install package without using a
'--'memory stick or CD. My home network is setup for a
'--'workgroup not a domain as there is no central server. I
'--'configured the laptop for workgroup instead of domain. I
'--'set the workgroup name to match the home network. When I
'--'restarted the laptop, the user name and password that I
'--'was using was no longer valid. I somewhat vaguely
'--'understand this as the user name was part of the domain
'--'not the local machine. I haven't quite figured out the
'--'details but that suffices for now.
'--'
'--'I was lucky that the Administrator (local machine I guess)
'--'had a default password. I was able to create new user
'--'accounts, etc.
'--'
'--'Now I attempted to run the VB application that had been
'--'installed before. I was not re-installing it, just running
'--'the previously installed application that had been
'--'working. When I did, it started the Microsoft Office 2000
'--'Installer. The installer prompted that I was attempting to
'--'use a component of Office that was not installed and asked
'--'for the CD. I tried again logged in as Administrator and
'--'got the same results. I did not have the CD so I had to
'--'cancel and give up for the night.
'--'
'--'When I took the laptop back to work, I could not get it to
'--'connect back to the domain, even though I used the proper
'--'domain name, user name and password. I got the message
'--'user name or password is invalid. I had our MIS department
'--'get it reconnected to the domain. MIS renamed the
'--'computer. They said they had to rename it because the
'--'server already knows about the old name and will not allow
'--'rejoining the network with an identical name. This did not
'--'make sense to me and I had heard of someone else I know
'--'that was able to get re-joined to domain without changing
'--'the laptop name.
'--'
'--'Anyway, the domain connection was working again and so was
'--'the original user name and password. Interestingly enough,
'--'now when I ran the VB application it was able to find the
'--'Office component it was looking for and did NOT start the
'--'Office 2000 Installer.
'--'
'--'Questions:
'--'=========================================
'--'Why did the VB application cause the Office Installer to
'--'run?
'--'
'--'I realize it wanted to use some component, but why
'--'couldn't it be found in a workgroup configuration?
'--'
'--'When an application like Office is installed in a domain
'--'configuration, is the machine essentially split into
'--'virtual machines such as local machine and domain machine?
'--'
'--'Why couldn't I reconnect to the domain at work after
'--'reconfiguring correctly?
'--'
'--'Why did MIS have to change the computer name to re-join
'--'the domain?
'--'
'--'=========================================
'--'Apologize for the length of this post, but without the
'--'whole story, the questions are not as clear.
'--'
'--'Any help is appreciated,
'--'
'--'Jim
'--'
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included
script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best
directed to the newsgroup/thread from which they originated.
- Next message: Dan: "Win2K/XP connectivity problem"
- Previous message: Gary Fose [MSFT]: "RE: AppleTalk issues"
- In reply to: Jim: "Domain vs Wkgrp changed VB app launch"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
