Ghost 9 Network hassles...

[Kenneth]

Kenneth, you are getting good advice from Peter. I've read all the
threads here and in backup.

If your two PC's (A & B) are both ONLY using TCPIP, and if the
router/switch is configured for DHCP, you should be able to ping
between the two. If you can't that MUST be fixed first. Don't just
disable NETBEUI by unchecking it, make sure it's not in the network
properties list.

I would disconnect all other cables from the router/switch except A &
B and concentrate on getting those two to communicate properly with
each other.

Make sure A and B can browse the other's network neighborhood shares.
Then see if those two can access the Internet via the router.

Once all that is working, then reboot one of them with Ghost 9, and
see if you can access the other one. In the Windows 2000 Pro PC with
the images on its hard drive, you wilt need have a valid logon
id/password defined for the Ghost user.

john

Hi John,

Thanks for your comments...

I did not merely un-check NetBEUI, I "removed" it. But with TCP/IP, I
could not ping either box from the other.

I have not tried the un-plugging approach as yet, but certainly will.

One other question:

I assume that to ping successfully, there is no logon issue. Is that
correct?

When I have more info, I will post here.

Sincere thanks, once again,

 

[Michael Kimmer]

Howdy,

I cannot seem to find my network to restore with Ghost 9 (or Drive
Image 7, or V2i Protector.)

If in Ghost 9 if I boot from the recovery CD and attempt to configure
the network, here's what I get:

The Network configuration dialog shows -

"No network configuration was detected."

The netcard name is displayed correctly, but is grayed out.

IP #1 displays correctly
Subnet #1 displays correctly

IP #2 displays 0.0.0.0.
Subnet #2 displays 0.0.0.0.

How should I proceed to get this thing to see the network properly?

Thanks for any assistance,

I haerd that you could contact Technical Support, they may ask you to send
them:
-the network card details
-a System Information file
-the Windows XP NIC drivers (as the PE environment is a Windows PE one)

Maybe they are willing to build an customer made ISO for you that natively
will support your NIC?

--
M.f.G.
Michael Kimmer

"Ein Tag an dem Du nicht lächelst ist ein verlorener Tag"
"Eine Nacht in der Du nicht schläfst ist eine verschlafene Nacht"

 

[Kenneth]

I haerd that you could contact Technical Support, they may ask you to send
them:
-the network card details
-a System Information file
-the Windows XP NIC drivers (as the PE environment is a Windows PE one)

Maybe they are willing to build an customer made ISO for you that natively
will support your NIC?

Hello Michael,

I have tried on at least five occasions in the last few days to get
technical support from Symantec.

The "support" is of amazingly poor quality. It is not an exaggeration
to say that the people trying to assist me know less about the product
than I.

On one occasion, the gentleman assisting me asked "What version of
Ghost are you using?" That is, of course, a perfectly reasonable
question. I answered, he said "Please hold for a few moments while I
research your problem." He returned perhaps five minutes later and
asked "What version of Ghost are you using."

I give you my word that precisely the same thing happened a third time
before I gave up on that particular call.

Later I called again, waited more than 30 minutes, and eventually
reached someone who was about to "assist" me. I asked to speak with a
"supervisor" and was told that I could make an appointment to receive
a return phone call.

I was to receive that call eleven hours ago, but, of course, have
received nothing.

All this is to say that the "support" provided by Symantec on Ghost is
something less than useful.

All the best,

 

[John .]

Hi John,

Thanks for your comments...

I did not merely un-check NetBEUI, I "removed" it. But with TCP/IP, I
could not ping either box from the other.

I have not tried the un-plugging approach as yet, but certainly will.

One other question:

I assume that to ping successfully, there is no logon issue. Is that
correct?

When I have more info, I will post here.

Sincere thanks, once again,

There is no logon with ping. The only thing that could stop it would
be router blocking pings, but I doubt it.

If you can't ping between two PC's and get a response, then your
network is not setup correctly.

If the PC's are physically close to each other you could further
isolate it by connecting an Ethernet cross-over cable between the two.

Before pinging though, check both PC's with ipconfig /all and compare
results. They should both have similar ip addresses except last such
as 192.168.1.100 and 192.168.1.101. Both should have 255.255.255.0
and both should have gateway address of your router (probably
192.168.1.1)

(above rule applies to all PC's on your network.)

You should not have to release or renew ip's to get it to work. They
must both have same workgroup name also.

I think there is a "Setup home network" wizard in Windows 2000. If so
run this, then reboot.

 

[Kenneth]

There is no logon with ping. The only thing that could stop it would
be router blocking pings, but I doubt it.

If you can't ping between two PC's and get a response, then your
network is not setup correctly.

If the PC's are physically close to each other you could further
isolate it by connecting an Ethernet cross-over cable between the two.

Before pinging though, check both PC's with ipconfig /all and compare
results. They should both have similar ip addresses except last such
as 192.168.1.100 and 192.168.1.101. Both should have 255.255.255.0
and both should have gateway address of your router (probably
192.168.1.1)

(above rule applies to all PC's on your network.)

You should not have to release or renew ip's to get it to work. They
must both have same workgroup name also.

I think there is a "Setup home network" wizard in Windows 2000. If so
run this, then reboot.

Hi John,

You may have pointed me in an important direction...

With the remote box running Windows, and the local box running off the
Ghost CD, I unplugged all but those two systems from the switch.

Then, as you suggested, I ran IPCONFIG /all on both.

They both show DHCP: yes

They both show Autoconfig: yes

The IP address are just as you suggest, that is differing by one in
the last field.

The subnet for both is 255.255.255.0

But, the remote (Windows) box displays the Default Gateway as
192.168.1.1 while the local (CD booted) box shows nothing in that
field.

So, that would seem to be telling us that the CD booted local box is
not seeing the router, and thus, not seeing anything else.

What should be my next step?

Sincere thanks,

 

[Peter]

Just curious, how did you run IPCONFIG /ALL on PC booted with Ghost9 CD? As
far as I know, Symantec does not allow to run command shell so there is no
way to execute that command.
Maybe you meant "Run IP Config Utilityl" ->View Info
The fact you do not see Default Gateway set up, might indicate DHCP server
setup problem (on your router)
But, if both PCs are connected to the same switch, there is no need for the
default gateway. They should be able to ping each other regardless of the
gateway setup.

 

[John .]

Just curious, how did you run IPCONFIG /ALL on PC booted with Ghost9 CD? As
far as I know, Symantec does not allow to run command shell so there is no
way to execute that command.
Maybe you meant "Run IP Config Utilityl" ->View Info
The fact you do not see Default Gateway set up, might indicate DHCP server
setup problem (on your router)
But, if both PCs are connected to the same switch, there is no need for the
default gateway. They should be able to ping each other regardless of the
gateway setup.

I agree. The important test is that with just 2 PC's connected to the
switch, and both booted to Windows 2000, can you
1. From windows 2000, ping and get response from each PC to the other
PC's ip address
2. From windows 2000 network neighborhood, can you browse (see) shared
resources on the other PC.

1 and 2 will verify a proper tcpip and sharing setup.

 

[Kenneth]

Just curious, how did you run IPCONFIG /ALL on PC booted with Ghost9 CD? As
far as I know, Symantec does not allow to run command shell so there is no
way to execute that command.
Maybe you meant "Run IP Config Utilityl" ->View Info
The fact you do not see Default Gateway set up, might indicate DHCP server
setup problem (on your router)
But, if both PCs are connected to the same switch, there is no need for the
default gateway. They should be able to ping each other regardless of the
gateway setup.

Hi John,

You may have pointed me in an important direction...

With the remote box running Windows, and the local box running off the
Ghost CD, I unplugged all but those two systems from the switch.

Then, as you suggested, I ran IPCONFIG /all on both.

They both show DHCP: yes

They both show Autoconfig: yes

The IP address are just as you suggest, that is differing by one in
the last field.

The subnet for both is 255.255.255.0

But, the remote (Windows) box displays the Default Gateway as
192.168.1.1 while the local (CD booted) box shows nothing in that
field.

So, that would seem to be telling us that the CD booted local box is
not seeing the router, and thus, not seeing anything else.

What should be my next step?

Sincere thanks,

Hi Peter,

Yes: "Run IP Config Utilityl" ->View Info" is what I did...

Thanks,

 

[Kenneth]

I agree. The important test is that with just 2 PC's connected to the
switch, and both booted to Windows 2000, can you
1. From windows 2000, ping and get response from each PC to the other
PC's ip address
2. From windows 2000 network neighborhood, can you browse (see) shared
resources on the other PC.

1 and 2 will verify a proper tcpip and sharing setup.

Hi John,

#2 is fine, we can see and modify shared resources in both directions
between any two machines. But #1 fails every time, and between any
combination of systems on our 5 node net.

Thanks,

 

[Kenneth]

Just curious, how did you run IPCONFIG /ALL on PC booted with Ghost9 CD? As
far as I know, Symantec does not allow to run command shell so there is no
way to execute that command.
Maybe you meant "Run IP Config Utilityl" ->View Info
The fact you do not see Default Gateway set up, might indicate DHCP server
setup problem (on your router)
But, if both PCs are connected to the same switch, there is no need for the
default gateway. They should be able to ping each other regardless of the
gateway setup.


Hi Peter,

Yes: "Run IP Config Utilityl" ->View Info" is what I did...

Thanks,

Hi,

I have no idea if this is useful information, but...

I just tried running Net View on the remote Windows machine from the
local Windows machine. To my surprise, it succeeded, but a ping
attempt fails.

Thanks for any further help on this,

 

[Peter]

Hi,

I have no idea if this is useful information, but...

I just tried running Net View on the remote Windows machine from the
local Windows machine. To my surprise, it succeeded, but a ping
attempt fails.

Did you disable NETBEUI and enabled TCPIP before doing that?

 

[John .]

Hi John,

#2 is fine, we can see and modify shared resources in both directions
between any two machines. But #1 fails every time, and between any
combination of systems on our 5 node net.

Thanks,

Then you must have some firewall (in router/switch or in Windows 2000)
that is blocking ping requests and responses. What brand/model
router/switch? Have you looked at the security settings in that
router?

When you look at the Windows 2000 Network properties, do you see only
one LAN network defined? No bridges or anything else? You might see
the dial up, but that should be the only extra one.

As you've found, if you can't get ping responses, Ghost (or anything
else) is not going to get through.

 

[Kenneth]

Did you disable NETBEUI and enabled TCPIP before doing that?

Hi Peter, and All,

Well, my saga has a very happy end.

In brief summary:

I had tried unsuccessfully (for many months) to see my network after
booting from the Drive Image, V2i Protector, or Ghost 9 CDs.

I spent hours with Tech Support folks from Powerquest looking at every
aspect of the problem all to no avail. I attempted to work with
support folks from Symantec, but found that to be a complete waste of
time.

Eventually, in an email, Peter suggested a variety of things that I
should check. For some reason, my eye was drawn to the bottom of his
list:

He said "Be sure that you don't have some sort of software firewall
running." (or words to that effect...)

Well, you can guess the rest.

Indeed, that was my months long problem, and all is now well.

My thanks to Peter, and to the other good folks who tried to assist!

All the best,